Capability 5 · Company System
Make Ownership Stick
"Nothing gets done unless I personally make sure it gets done" — until results got single visible owners, explicit decision rights and a weekly review, and the founder stopped being the company's follow-up system.
Founders say
“Nothing gets done unless I personally make sure it gets done.”
Where you are today
- Every commitment lives in your head, and things move only when you chase them.
- A launch slips because three teams each assumed another one owned the integration piece.
- Decision rights are fuzzy, so everything escalates up — your calendar is mostly tie-breaking.
Where you’re headed
- Every important result has one visible owner on the ownership map.
- The weekly ownership review runs the follow-up — a two-week holiday doesn't stall the quarter.
- Owners know what they decide alone and what needs alignment, and anything not green arrives with a plan.
The hook above is a real founder line, word for word — and the instinct it produces is exactly wrong. The founder who believes nothing happens without them responds by chasing harder, which makes it truer: follow-up now means you asking, so the moment you stop asking, everything reverts. Tasks were transferred; ownership never was. Ownership isn't a personality trait you hire for — it's a system you build. Patrick Lencioni's Five Dysfunctions pyramid names the failure chain underneath it: teams that don't commit avoid accountability, and teams that avoid accountability stop attending to collective results.
The three layers of the system
First, visible owners for results — results, not tasks. One name per important result, on an ownership map anyone in the company can read. Two names on one result, "the team" owning it, or an owner who routes every call back up to you — none of those is ownership; they're the appearance of it. Second, explicit decision rights: what an owner decides alone, what needs alignment first, where escalation is expected. Most escalation culture is just this list not existing. Third, a rhythm where accountability is normal: owners traffic-light their results in the weekly review, and the only thing that's not okay is a plan-less red. Watch out for the counterfeit version — meetings full of updates and zero commitments, where progress gets reported but never owned, and nothing is ever red because nothing was ever promised.
The first team
Ownership's top floor is your leadership team — and most leadership teams aren't teams. They're department heads reporting in parallel, each loyal to their function first. The test: when their function's interest and the company's interest split, which do they choose? The strongest leadership teams craft their own distinctive culture — a handful of explicit agreements about how they disagree, decide and defend decisions — and the first agreement is one voice outside the room. A decision defended with "well, I disagreed" undoes ownership on every floor below it.
80% commitment, 100% alignment. You might be only 80% sold on a decision after the fight — outside the room you're 100% aligned, defending it as if it were your own idea. Kin to Andy Grove's "disagree and commit", and the behavioural core of putting the company above the function.
This page is the org level: systems and culture that make ownership stick without you. The individual level — co-creating goals and accountability with one person, delegation that doesn't snap back — lives in Build Leaders, Not Dependencies. Same principle, two altitudes.
What you can do right now
- Map the results, not the tasks. List the results that matter this quarter and put exactly one name on each. Publish it where everyone can see it. Ownership Map →
- Write the decision rights. For each owner: what they decide alone, what needs alignment first, and where escalation is expected. Most escalation culture is just this list not existing. Alignment vs. Autonomy →
- Install the weekly ownership review. Owners bring their own traffic lights, the meeting opens with last week's commitments and closes with new hard ones — measurable, time-bound. Run it two weeks in a row and watch the chasing stop. Commitment Loop →
- Run the pyramid check. If accountability is missing, look one layer down: is it really a commitment problem, a conflict problem, or a trust problem? Five Dysfunctions of a Team →
The toolkit
Work with Ben
Want help installing this?
Outstride OS is the system behind Ben's founder coaching — pre-seed to Series C. If this page names something you are living right now, start a conversation.