Direction, Measures, and Autonomy Leadership
Set direction and measurable success, then let capable people execute
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 90%
This leadership method separates what the leader must own from what the team should own. The leader selects a direction, establishes a small set of guidelines, and defines measurable evidence of success. Team members then determine how to accomplish the work within those boundaries. This allows the leader to support multiple demanding responsibilities while preserving the judgment and motivation of skilled specialists. The method depends on hiring or developing capable people, because delegation without competence becomes neglect. It also depends on measurable outcomes, because autonomy without a shared definition of success creates drift. Reviews should therefore focus on results, constraints, and learning rather than controlling every intermediate action. The output is a team that remains aligned while operating with substantial execution independence.
Origin
Anderson described this as his general philosophy while leading Wired, writing books, pursuing public work, and developing side projects.
Core principles
- 01Leaders provide direction rather than constant instructions
- 02Success needs explicit and measurable definitions
- 03Capable people should control execution
- 04Strong staffing makes autonomy possible
How to run it
- 1
Set the direction
Define the destination and why it matters. Keep the direction specific enough to guide decisions without prescribing every action.
Pro tip Express the direction in language the team can use to resolve trade-offs.
Watch out A slogan without operational meaning does not provide direction.
- 2
Define measurable success
Choose observable outcomes that will show whether the work succeeded. Include quality, timing, impact, or business measures as appropriate.
Pro tip Use a small number of measures that the team can influence.
Watch out Activity metrics can reward motion without progress.
- 3
Establish constraints
Communicate the essential standards, boundaries, resources, and risks. Leave everything else open to team judgment.
Pro tip Explain why each constraint exists.
Watch out Too many guidelines recreate micromanagement.
- 4
Delegate execution
Give capable people clear ownership and authority to choose methods. Avoid pulling decisions back upward merely because their approach differs from yours.
Pro tip Delegate outcomes and decision rights together.
Watch out Responsibility without authority is not genuine delegation.
- 5
Review and learn
Compare results with the agreed measures and discuss what should change. Intervene when evidence shows drift, not simply to remain involved.
Pro tip Use review cycles appropriate to the cost of being wrong.
Watch out Waiting until final delivery can make correction unnecessarily expensive.
In the wild
An editor establishes the publication's technological worldview, audience standards, and measurable goals, then lets strong writers, designers, and editors determine how individual stories are reported and presented.
→ The publication remains coherent without requiring the editor in chief to control every assignment.
Common mistakes
Delegating without a destination
People cannot exercise aligned judgment if the leader has not established what the team is trying to achieve.
Measuring the wrong activity
Easy-to-count output can displace the quality or impact that actually defines success.
Calling neglect autonomy
Teams still need capable staffing, usable constraints, resources, and outcome reviews.
Is it for you?
Best for
It is best for experienced creative, editorial, technical, or cross-functional teams capable of independent judgment.
Not ideal for
It is not ideal for untrained teams, emergencies, or tightly regulated work requiring prescriptive supervision.
From the transcript
“my general philosophy on on on, you know, leading teams is to kind of point them in a direction, set some some you know, some…”
From the episode
Chris Anderson: Don’t Confuse Valuation With Tech Adaptation
Chris Anderson