Single-Threaded Leadership

Assigning one person, supported by a dedicated and largely autonomous team, to own a single initiative and nothing else. The "single thread" is that the owner's attention is not divided across competing priorities, and the team has the people and authority it needs so progress does not wait on other teams.

Why it Matters

Important initiatives stall when they are one of many responsibilities competing for a leader's attention, or when they depend on teams with their own priorities. A single-threaded owner removes both drags: undivided focus and minimized cross-team dependencies let the initiative move at its own pace. The book's lesson is that small teams alone (two-pizza teams) were necessary but not sufficient; what mattered was separable, single-threaded ownership.

Signals

• A key initiative shared among leaders who each own it part-time.
• Progress repeatedly blocked waiting on another team's roadmap.
• "Everyone is responsible, so no one is."

Benefits

Focus, clear accountability, and speed from autonomy and few dependencies.

Risks

Duplicated effort across autonomous teams; under-resourcing the owner so the autonomy is nominal; fragmenting work that genuinely needs to stay together.

Tensions

Autonomy and minimized dependencies speed a single initiative but can duplicate work and fragment shared concerns that centralization would handle more efficiently; independence trades coordination cost for speed.

Examples

Giving a new product a dedicated owner and team rather than adding it to an existing team's backlog; restructuring so an initiative no longer depends on three other teams' priorities.