📖 Business
Missionaries vs Mercenaries
John Doerr's distinction between missionary and mercenary organizations, applied by Cagan to product teams. **Mercenaries** build what they are told. They hit deadlines, complete tickets, and ship features — but they do not deeply care about the user or the outcome. **Missionaries** believe in the vision. They are obsessed with the customer problem, will push back on bad ideas, propose better alternatives, and work through hard problems because they genuinely care about the result. Cagan's core insight is that the difference between these two modes is not about hiring or motivation — it is about organizational structure. The same talented engineer becomes a mercenary on a feature team and a missionary on an empowered team.
2
Minutes
2
Concepts
+45
XP
1
How It Works
- Mercenary behaviors: builds exactly what the spec says, does not question requirements, measures success by on-time delivery, disengages after handoff, treats the product as "someone else's problem"
- Missionary behaviors: asks "why are we building this?", talks to customers, proposes alternative solutions, measures success by business impact, feels ownership of the outcome even after launch
- The organizational lever is empowerment. When teams are given problems and trusted to find solutions, they develop missionary mindsets. When teams are given feature specs and deadlines, they default to mercenary mode
- Missionary teams produce better outcomes because they bring diverse perspectives (engineering, design, product) to the problem. Mercenary teams produce exactly what was specified — which is usually wrong
- Leadership creates missionaries by: sharing compelling vision, providing strategic context, trusting teams with problems, celebrating outcomes over outputs, and tolerating experimentation and failure
- Leadership creates mercenaries by: dictating features, measuring velocity, punishing missed deadlines, ignoring team input, and treating engineers as interchangeable resources