Concept
One Responsibility Each
One responsibility each is a startup management rule described by Peter Thiel in Zero to One: every early team member owns exactly one clearly defined area that no one else shares, so they are judged on one thing and never compete with a colleague for the same job.
In a young company, roles are vague and everything is urgent, so two capable people often drift into the same territory. That is where most early conflict comes from. The cause is usually overlapping ownership, not bad character. Thiel describes how PayPal reduced this conflict by evaluating each person on a single responsibility. They also made sure no two people's responsibilities collided. The point is not narrow job descriptions or rigid silos, because people still help each other. The point is that every important outcome has one name next to it, and every person has one thing they are clearly measured on. That clarity ends the daily turf negotiation and makes accountability obvious. The mission is what brings early hires in. Clear ownership is what keeps them pulling in the same direction instead of quietly competing.
A real-life example
A six-person fintech startup has two engineers who both "own the app." Each rewrites the other's code, and stand-ups turn tense. The founder splits the territory. Maya owns payment reliability, measured by failed transactions. Tom owns onboarding, measured by sign-up completion. They still review each other's work. Within two weeks, the arguments over whose call it is disappear, and both can say exactly what they are judged on.
How to use it
- 1List every outcome that matters this quarter and write one owner's name next to each. Any outcome with two names or none is your first problem.
- 2Give each person a single primary measure they are judged on, and check that no two people's measures overlap.
- 3Revisit the map whenever someone joins or the company pivots, because responsibilities that were clean at five people blur at fifteen.