Principle

Delegate context, not only instructions

Context lets people make local choices that preserve the larger objective.

About 1 min read

Before you use it

Use when
  • When delegated work is technically completed but optimized for the wrong priority.

Keep this limit in mind

  • Autonomy must be bounded by competence, risk, compliance and recoverability. High-consequence decisions may need explicit approval gates.

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

Explain why the outcome matters, what downstream systems or people depend on it, and which trade-offs are acceptable. Context is part of the work product.

An example

A developer learns that audit traceability outranks UI elegance for a specific workflow, so edge-case choices remain aligned.

Check your result

Local decisions remain coherent when the original instructions no longer fit exactly.

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 readingDelegate context, not only instructions

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