Skip to main content

Documentation Index

Fetch the complete documentation index at: https://userstory.zeroemdashes.com/llms.txt

Use this file to discover all available pages before exploring further.

Leading with context is the practice of sharing the reasoning, constraints, and goals behind decisions - not just the decisions themselves. It’s the alternative to leading with control, where the leader makes the calls and the team executes without needing to understand why 🧭 Netflix popularised the phrase, but the idea predates them. The military calls it commander’s intent - telling people what you’re trying to achieve so that when the plan changes on contact with reality, they can adapt intelligently rather than waiting for new orders.

​
Why it matters

When people understand the context behind a decision, three things happen: Better autonomous decisions - a team that knows the strategy, the constraints, and the priorities can make good calls without escalating everything. Context is what enables genuine delegation rather than just task assignment. Better pushback - when people understand the reasoning, they can identify when it’s flawed. A team that just receives directives can’t challenge bad decisions; a team with full context can and will 💡 Better alignment - context travels. When your PM understands why something is a priority, they can explain it to their team, who can explain it to engineering, who can make better technical trade-offs as a result. Without context, each layer of the organisation is guessing.

​
What context to share

The context that matters most:
  • The goal - what outcome are we trying to achieve, and why does it matter right now?
  • The constraints - what are we working within? Timeline, budget, regulatory requirements, strategic dependencies.
  • The trade-offs - what did we consider and decide against, and why?
  • What could change - if conditions shift, which decisions are revisable and which aren’t?
The common objection is “we can’t share everything.” That’s sometimes true - there are genuinely sensitive things that can’t be shared broadly. But most leaders vastly underestimate how much context is safe to share and overestimate how much their team already has 🙌

​
Context and empowerment

Marty Cagan’s Empowered is essentially a book about this - product teams that are given outcomes and context, rather than features and instructions, consistently outperform those that aren’t. The context is what converts a team of mercenaries into a team of missionaries. Lesson learned: every time I’ve shared more context than felt strictly necessary, the team made better decisions than I would have made for them. The information asymmetry that leaders protect is usually the thing limiting their team’s performance.