Divide and conquer is one of the most celebrated principles in project management. Break complex problems into smaller parts, assign ownership, deliver in parallel, integrate at the end. The statistics look good — projects run this way show higher success rates than traditional waterfall approaches. The logic is sound. The method is widely taught.
And yet. Something happens when you watch it run in practice, up close, across multiple programmes and organisations. The parts get delivered. The integration struggles. The people who owned their piece move on to the next thing. And somewhere in the gap between the pieces, the actual problem — the one the project was supposed to solve — didn't quite get addressed.
When you divide a project into clear, bounded deliverables and assign each one to a person or team, you create something useful: accountability. You also create something dangerous: a structure where the rational move is to make your piece look good, regardless of what's happening to the whole.
A good manager in this structure might deliver 90% of what the project needs. A career-oriented one delivers the 30% that makes them look good and moves on. Both are behaving rationally within the system. The system rewards completion of the assigned piece. It does not reward — and often can't even measure — contribution to the overall outcome.
This isn't a character flaw. It's a design flaw. The method has it built in.
Most complex programmes don't fail completely. They deliver 80% — enough to declare success, close the budget, and write the case study. The remaining 20% becomes someone else's problem: the legacy system that never got switched off, the workaround that calcified into permanent process, the integration point that was "handled" but never quite worked.
This 80% outcome isn't a coincidence or a failure of execution. It's the natural result of a method where individual deliverables are clear and the integration is nobody's job. Or rather — it's everyone's job in theory and nobody's job in practice.
The people who delivered their piece are done. The people who should integrate don't own anything specific enough to be accountable for. And the gap in between is where 20% of the value permanently lives.
The answer isn't to stop dividing work — that would be a different kind of failure. Diffuse responsibility where everyone owns everything means nobody owns anything. Programmes stall that way too, just more slowly and with better meeting attendance.
The answer is to separate two things that divide and conquer conflates: dividing the work and dividing the picture.
You can give people clear ownership of specific outcomes while making sure they understand the full context — why this piece matters, how it connects to the others, what the project is actually trying to achieve at the level that no single deliverable captures. That's not the same as giving everyone everything and hoping they self-organise. It's setting direction clearly, sharing the picture fully, and then trusting people to make good decisions within that frame.
What changes when you do this: people stop optimising for their piece and start optimising for the outcome. Not because they're better people — because they can see the outcome clearly enough to aim at it.
Before dividing a project, it's worth asking: am I dividing this to make the work manageable, or am I dividing it to make success attributable?
If the answer is the second one — and it often is, even when nobody admits it — the structure will optimise for individual wins. Some of those wins will align with project success. Some won't. And the ones that don't will be very hard to see until it's too late to do anything about them.
The projects that deliver 100% are the ones where someone held the full picture — not as a control mechanism, but as a shared reference point that everyone could navigate by. That's a different kind of leadership than dividing and conquering. It's harder to measure. It's also harder to fake.
This is part one of a two-part series on project leadership. Part two — Direction over Division — looks at what the alternative actually looks like in practice.