Mission-Above-Product Prioritization
Route every cross-org tradeoff through a single shared mission so decisions are fast and everyone stands behind them
- Difficulty
- Advanced
- Time to result
- ~ongoing to results
- Steps
- 3
- Confidence
- 88%
Anthropic makes fast org-wide decisions by placing a unifying mission above any individual product line or team's KRs. When two priorities compete, the team debates which better serves the mission, decides, and everyone commits — even the losing team. This is distinct from focus: mission means teams willingly sacrifice their own goals in service of the company's, which is what lets decisions cut cleanly across the whole org.
Origin
Cat Wu describing Anthropic's decision-making culture; she explicitly distinguishes 'mission' from 'focus' as separate ingredients.
Core principles
- 01A shared mission is a tiebreaker that resolves competing priorities quickly
- 02Mission is about willing self-sacrifice of team KRs, not just staying focused
- 03When the call is made, even the deprioritized team stands behind it
- 04Referencing the mission frequently in real decisions keeps it load-bearing, not decorative
How to run it
- 1
Establish one mission that outranks any product
Hire for and repeatedly reference a mission that sits above every individual product line, so it can legitimately override local team goals.
- 2
When priorities compete, debate which serves the mission more
Frame the tradeoff explicitly as 'which of these matters more for the mission?' rather than which team shouts loudest or has more revenue at stake.
- 3
Decide, then have everyone commit — including the losers
Once decided, the whole org stands behind the choice; a team may deprioritize its own shipment and wait, accepting the hit to its own KRs.
Pro tip The willingness of a team to be happy even if its product fails but the company succeeds is the cultural marker that the mission is real.
Watch out This only works if people genuinely internalize the mission over local incentives — otherwise it becomes lip service and slows decisions.
In the wild
Cat notes that sometimes the team wants to ship something on Claude Code, but another initiative is more important for the mission, so they deprioritize the Claude Code work and wait until later — without internal conflict.
→ Fast cross-cutting decisions that the whole org executes in a unified way, at a scale Cat says she's never seen elsewhere.
Facing demand and capacity limits, Anthropic chose to prioritize its first-party products and API over third-party 'open claw' usage, framing it as growing the number of users it can reach — a mission-aligned tradeoff even though it hurt some third-party users.
→ A hard but decisive call that the team aligned behind rather than relitigating.
Common mistakes
Confusing mission with focus
Focus is doing fewer things; mission is willingly sacrificing your own goals for the company's. Treating them as the same misses the self-sacrifice dynamic that actually resolves cross-team conflict.
Keeping the mission decorative
If the mission is never invoked in concrete tradeoff decisions, it can't function as a tiebreaker and teams default to local incentives.
Is it for you?
Best for
Multi-team product orgs where cross-cutting decisions stall because each team optimizes its own KRs
Not ideal for
Small single-product teams with no competing product lines, or orgs whose mission is too vague to adjudicate real tradeoffs
From the transcript
“If there's two competing priorities, we'll talk about which one is more important for Anthropic's mission.”
“Mission means that teams are willing to make sacrifices that hurt their own goals and their own KRs in service of Anthropic's goals and Anthropic's…”
“if Claude Code failed, but Anthropic succeeded, I would be extremely happy.”
From the episode
How Anthropic’s product team moves faster than anyone else
Cat Wu (Head of Product, Claude Code)