Protocol

Set a decision date and evidence threshold

A decision needs a stopping rule as well as a question.

About 1 min read

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.

Keep reading

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

  1. Set the date after which delay has a real cost.
  2. List must-have evidence.
  3. List uncertainty that can remain.
  4. 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.

Use email
Keep exploring

Connected ideas

You are readingSet a decision date and evidence threshold

Evidence and sources
Supports

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

All sources (1)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details