Companies stop shipping the moment ownership goes soft. A goal everyone is responsible for is a goal nobody is responsible for, because responsibility without singular ownership is just a feeling. The single-thread principle is the discipline of assigning exactly one person to every outcome that matters, then giving them the room and rope to deliver it.
The idea has pedigree: Amazon institutionalised it as the single-threaded leader, one person whose only job is the initiative, on the observation that the best way to fail at something new is to make it somebody's part-time job. The principle scales down perfectly. A five-person startup does not need the org machinery, but it needs the same sentence answered for every outcome that matters: whose name is on this?
Why the rule keeps breaking
The trap is collaboration. It feels generous to say "we will own this together," but committees do not own things, they coordinate them. Coordination is overhead, not progress. The instant an outcome is collective, decisions migrate to the slowest reviewer in the room and the work stalls in inboxes.
Watch for the moment the rule breaks most predictably: when the work starts struggling. A launch slips, and leadership's instinct is to "put more senior eyes on it," which quietly converts one owner into a working group. Now every decision needs alignment, the original owner reads the reinforcement as a demotion, and velocity drops exactly when it most needed to rise. The correct move under pressure is the opposite: keep one name, and add support (hands, budget, unblocking) that reports to that name. Help flows through the owner, never around them.
What single-threading actually looks like
The owner is named, in writing, with the outcome they are responsible for and the date it is due. They have the authority to make the trade-offs the work demands, and they are the one accountable when it lands or does not. Other people contribute, but only one name sits next to the outcome.
The authority clause is the half everyone skips, and without it the principle curdles into scapegoating: accountability for an outcome whose key decisions are made elsewhere is just pre-assigned blame. A real single-threaded owner can reprioritise their own time, make the reversible calls without asking (see the 70% rule), spend within an agreed envelope, and escalate a blocker to anyone in the company. If any of those requires a committee, the outcome has a coordinator, not an owner. The written form is one line, and the whole company should be able to read it: outcome, name, date, decision rights.
Where it earns its keep
Cross-team initiatives, anything spanning product and operations, new market launches, and any change that requires a sequence of small decisions. The faster the cadence of decisions, the more dangerous shared ownership becomes.
Run the audit that makes the gaps visible: list your company's ten most important outcomes for the quarter and try to write one name next to each. The outcomes where you hesitate, or where the honest answer is a function ("marketing owns it") rather than a person, are precisely the ones drifting. A function cannot be accountable; a name can. And include the founder's own list in the audit: the outcomes the founder vaguely holds are usually the softest-owned in the whole company, because nobody else will claim what the founder has not visibly released.