TL;DR: Amazon’s principle: for each major initiative, one leader whose sole job is that project. “The best way to fail at inventing something is by making it somebody’s part-time job.” Kills intra-organizational dependencies.
A leader who owns something part-time owns nothing. They optimize for their day job. The initiative gets what’s left over. Single-threaded leadership inverts this: the initiative is the day job. The leader is measured, funded, and politically protected around that one mission.
This matters because most corporate lethargy comes from diffused ownership. Nobody has full accountability. Project timelines slip because the owner is in a meeting defending something else. Teams can’t commit because their leader is split across five initiatives. Single-threading breaks the knot: one leader, one team, one mission. Dependencies between initiatives get escalated to the S-Team, not negotiated sideways (working-backwards-method, working-backwards).
The constraint is obvious: you can only have a few truly single-threaded leaders. That’s a feature, not a bug—it forces prioritization.