Two people in one job is an idea that returns every few years and leaves again. It is back, and the reasons are mostly sound ones: a company that cannot find a single candidate with the full range, a succession that needs a bridge, a strong internal who will leave if passed over, a business that genuinely spans two disciplines nobody holds at once.
Where it works, it works well and quietly. Where it fails, it fails in a recognisable way, and the failure is usually visible in the announcement.
The split has to be about the work, not about the people
The arrangements that hold up divide something real. One runs the commercial side and one runs delivery. One owns the existing business and one owns the new market. One holds the region and one holds the function. In each case a stranger could look at a decision and say which of the two owns it, and the pair could too.
The ones that fail divide nothing. Co-leads are announced as jointly responsible for everything, described as complementary, and asked to operate by consensus. What happens next is predictable. Decisions requiring a trade-off between their two priorities have no owner, so they get deferred. The organisation learns which one to ask for what, and an informal hierarchy forms that nobody will confirm. The pair spend an increasing share of their time aligning with each other rather than running anything.
The tell is usually in why the structure exists. A co-lead arrangement created because two candidates were both strong and the company did not want to lose either is not an org design; it is a retention package with a reporting line attached, and it postpones the choice rather than making it. That is a reorganisation used to avoid a decision, scoped to one seat.
The version with the best record is explicitly temporary and says so. A founder and an operator running together through a transition works when everyone knows it is a transition and roughly how long it lasts, which is why hiring an operator alongside the founder has become the standard move rather than an unusual one. The damage comes from the indefinite version, where the ambiguity is the point.
There is a cost the announcement never mentions. Two people in one job means the layer below has two managers to satisfy, two sets of priorities to reconcile, and no clean escalation path when those conflict — which lands hardest on the middle tier that companies cut and are now rebuilding, and which is precisely the group with the least authority to force a resolution.
And it does not solve the problem it is usually reached for. A company using co-leadership because it has no obvious successor still has no successor; it has two people doing half a job each, neither of whom is being tested on the whole of it. That is the bench depth problem with an org chart drawn over the top of it.
