How do I practice delegate outcomes not methods?

The most direct way to practice delegate outcomes not methods is through a focused exercise: Choose one task you currently delegate — to a person, a tool, or an AI agent. Write down how you currently specify that delegation. Separate your specification into two columns: outcome statements (what the result must achieve) and method statements (how to achieve it). Now rewrite the delegation using only the outcome column. Add constraints only where they are genuinely necessary — budget limits, legal requirements, format compatibility, deadlines. Remove every method statement that is actually a preference rather than a requirement. Test the rewritten delegation this week and observe whether the result meets your needs. If it does, the method statements were unnecessary overhead. If it does not, identify which missing constraint caused the failure and add that specific constraint back — as an outcome constraint, not a method prescription.

Common pitfall: Specifying outcomes so vaguely that the delegate has no useful guidance. 'Make the report good' is not outcome delegation — it is abdication. Outcome delegation requires precision about the result: what the deliverable contains, who it serves, when it is due, what quality threshold it must meet, and what constraints are non-negotiable. The failure is not in giving too much freedom about method. The failure is in giving too little clarity about the destination. Vague outcomes produce worse results than detailed methods, because at least detailed methods produce predictable outputs. The goal is precise outcomes with open methods — not vague outcomes with no methods.

This practice connects to Phase 27 (Delegation Patterns) — building it as a repeatable habit compounds over time.