Protocol
Set a decision date and evidence threshold
A decision needs a stopping rule as well as a question.
Before you use it
- Use when
- When analysis keeps expanding because nobody knows when enough evidence is enough.
Keep this limit in mind
- Formal governance and accountability still apply. Stakeholder analysis should expose constraints and decision rights, not justify bypassing them.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
Define the latest useful decision date, the evidence that must be present, and what uncertainty can remain. This prevents endless consultation while preserving material unknowns.
Steps
- Set the date after which delay has a real cost.
- List must-have evidence.
- List uncertainty that can remain.
- Name the fallback if evidence is still missing.
An example
A rollout choice must be made Friday; error-rate data and support capacity are mandatory, while exact month-three volume can remain uncertain.
Check your result
The team can say what evidence closes analysis and what happens if it does not arrive.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingSet a decision date and evidence threshold
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaFind the missing stakeholder before late review
Evidence and sources
A meta-analysis of 65 independent studies found team cognition positively related to team behavioral process, motivational states and performance, with moderation by task and team characteristics.
Shared cognition is not identical to unanimous opinion; teams may need differentiated expertise as well as common understanding.
The Cognitive Underpinnings of Effective Teamwork: A Meta-Analysis · Abstract
Edition and review
Version 0.1.0
No review details are supplied for this edition.