Single-Threaded Leadership Model

"The best way to fail at inventing something is to make it somebody's part-time job." — Bill Carr

What It Is

An organizational model where a single leader is fully accountable for a specific business goal and controls the cross-functional resources (engineering, product, marketing) needed to achieve it, minimizing external dependencies.

When To Use

Company becomes complex and innovation slows
Cross-team dependencies cause bottlenecks
Bureaucratic resource fighting between departments
Need to move with startup speed within a large org

Before vs. After

PROJECT ORIENTATION (Matrixed)    SINGLE-THREADED (Program)
┌────────────────────────────┐    ┌────────────────────────────┐
│ Resources swarmed to       │    │ Dedicated cross-functional │
│ temporary projects         │    │ teams                      │
├────────────────────────────┤    ├────────────────────────────┤
│ High dependency on         │    │ Control of own resources   │
│ central teams              │    │ and roadmap                │
├────────────────────────────┤    ├────────────────────────────┤
│ Leaders referee every      │    │ Leaders referee resource   │
│ roadmap item               │    │ allocation only            │
├────────────────────────────┤    ├────────────────────────────┤
│ Diluted ownership          │    │ Clear single-owner         │
│                            │    │ accountability             │
└────────────────────────────┘    └────────────────────────────┘

Core Principles

1. Program Over Project Orientation

Long-term ownership beats temporary task forces.

2. Autonomy Creates Speed

Teams that own their resources move faster.

3. Remove Dependencies

Reduce "coordination tax" by decoupling architectures.

4. Leader Owns Everything

Roadmap, resources, and results under one person.

How To Apply

STEP 1: Identify Strategic Goal
└── What outcome needs dedicated ownership?
└── What's currently "everyone's job" (nobody's job)?

STEP 2: Appoint Single-Threaded Leader
└── One person, fully dedicated
└── Cannot be their "part-time job"

STEP 3: Assign Cross-Functional Resources
└── Give them their own engineers
└── Give them their own designers/PMs

STEP 4: Decouple Architecture
└── APIs instead of shared code
└── Minimize dependencies on central teams

STEP 5: Implement Countermeasures
└── Bar Raisers to maintain quality
└── Functional guilds for skill development

Common Mistakes

❌ Creating single-threaded teams without decoupling architecture first

❌ Failing to implement countermeasures (like Bar Raisers)

❌ Making it someone's part-time job

Real-World Example

Prime Video organized into separate single-threaded teams for TV apps, game consoles, and mobile phones, each with their own resources and roadmaps.

Source: Bill Carr, Co-author of "Working Backwards", Lenny's Podcast