Principle

Match detail depth to the receiver's decision

Useful detail is relative to the decision being made.

About 1 min read

Before you use it

Use when
  • When the same explanation is being reused for engineers, executives and process owners.

Keep this limit in mind

  • Influence should remain evidence-based and transparent. Do not hide material risks, manufacture urgency or manipulate stakeholders into consent.

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

Keep the evidence chain intact but change resolution: implementation detail for builders, control and impact for owners, trade-offs and exposure for executives. Do not confuse simplification with omission of material risk.

An example

A developer gets field mappings and error traces; the sponsor gets affected volume, operational impact, options and residual risk.

Check your result

The receiver can decide without asking for basic relevance, while deeper evidence remains traceable.

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 readingMatch detail depth to the receiver's decision

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)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details