Principle

Write the unresolved disagreement explicitly

Hidden disagreement is more dangerous than visible disagreement.

About 1 min read

Before you use it

Use when
  • When a meeting ends with polite language but different stakeholders leave believing different things.

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

Record the exact proposition still disputed, the competing evidence or values, the owner of the next step and the condition for closure. Avoid vague labels such as 'alignment needed.'

An example

The record says 'Finance accepts option B only if reconciliation stays under two hours; integration cannot yet demonstrate that threshold.'

Check your result

A reader can identify the unresolved proposition without attending the meeting.

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 readingWrite the unresolved disagreement explicitly

Evidence and sources
Limits

A meta-analysis found both relationship conflict and task conflict negatively related to team performance and satisfaction on average, with task and task-complexity moderators.

The result cautions against treating conflict itself as beneficial; constructive disagreement still requires process design and cannot be reduced to one correlation.

Task Versus Relationship Conflict, Team Performance, and Team Member Satisfaction: 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