Principle
Delegate context, not only instructions
Context lets people make local choices that preserve the larger objective.
When it fits
- When delegated work is technically completed but optimized for the wrong priority.
When to avoid it
- Autonomy must be bounded by competence, risk, compliance and recoverability. High-consequence decisions may need explicit approval gates.
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.
Keep this limit in mind
- Autonomy must be bounded by competence, risk, compliance and recoverability. High-consequence decisions may need explicit approval gates.
Connected ideas
Useful withKeep one review point that does not become micromanagement
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