Protocol

Pre-wire the decision before the formal meeting

The formal meeting should not be the first time critical evidence is processed.

When it fits

  • When a high-stakes meeting is expected to produce a decision but key objections are predictable and complex.

When to avoid it

  • Formal governance and accountability still apply. Stakeholder analysis should expose constraints and decision rights, not justify bypassing them.

Why it matters

Brief the decision owner and material dissenters beforehand on the decision, evidence, trade-offs and unresolved risks. Use the meeting for closure, not surprise discovery.

Steps

  1. Share the decision question in advance.
  2. Test the recommendation with material dissenters.
  3. Repair missing evidence or expose unresolved disagreement.
  4. Keep the formal forum as the actual decision point.

An example

Before a steering committee, the consultant validates the risk model with security and finance so the meeting debates the remaining trade-off rather than basic facts.

Check your result

Known material objections have been surfaced before the meeting without privately deciding the outcome.

Keep this limit in mind

  • Formal governance and accountability still apply. Stakeholder analysis should expose constraints and decision rights, not justify bypassing them.

Connected ideas

Use before
Write the unresolved disagreement explicitly

Evidence and sources

Supports

A meta-analysis of 72 independent studies found team information sharing positively related to performance, cohesion, decision satisfaction and knowledge integration, with meaningful moderators.

The useful form and amount of sharing depend on task, discussion structure and how information is distributed.

Information Sharing and Team Performance: A Meta-Analysis · Abstract

All sources (1)