The Setup
A familiar scene — big team, big budget, big delays.
Picture a cross-border project with a dream team assembled across multiple regions. The brief is ambitious. The budget is generous. The roster reads like a highlight reel — creative directors, regional coordinators, technical leads, content specialists, logistics managers. Everyone is an expert. Everyone is busy.
Yet nothing moves.
Weeks pass. Deliverables slip. Meetings multiply. The project has all the resources it needs — the talent, the tools, the budget. But it lacks the one thing that actually propels progress: someone who can close the loop.
The Common Misconception
"Complex work needs more hands." — The assumption we need to challenge.
When things get hard, leaders instinctively add headcount. The logic seems sound: more complexity demands more capacity. More capacity means more people. More people means more output.
But this logic is built on a flawed premise.
More people mean more coordination. More coordination means more communication. More communication means more friction. More friction means slower progress. The equation doesn't scale as we expect — and yet we keep running the same calculation, expecting different results.1
Where It Actually Breaks
The real cost of "too many cooks."
The mechanics of why large teams stall are predictable once you know what to look for:2
Fragmented ownership
When responsibility is distributed across too many people, no one owns the full outcome. Everyone owns a piece. No one owns the result.3
Long communication chains
Information degrades with every handoff. By the time a decision reaches the person who needs to act on it, it has been filtered, reinterpreted, and diluted.4
Decision paralysis
Too many stakeholders means too many opinions, too many approval layers, and too much time spent aligning before anything can move.5
Coordination burden
Meetings about meetings. Status updates about status updates. The infrastructure of coordination consumes the capacity it was meant to enable.6
Blame culture
When things fail, everyone points elsewhere. Accountability dissolves into the complexity of the org chart.7
The Alternative Model
One person who can "close the loop."
The antidote to splintered teams isn't a better project management tool or a more detailed RACI matrix. It's a different kind of person.
A cross-functional lead who can operate across silos — someone who doesn't just coordinate between functions, but who can actually execute within them. Three capabilities define this person:
Understand the "what"
Vision and direction. They can hold the strategic intent without losing it in the operational noise.
Understand the "how"
Technical and implementation feasibility. They know what's actually possible, not just what looks good on a slide.
Understand the "now"
What needs to happen today to move forward. Not next quarter. Not after the next alignment meeting. Today.
This is the loop-closer. The person who can take an idea from concept to execution without losing it in the handoffs.
Before and After
What changes when you shift from "more people" to "the right person."
The difference in velocity is not incremental. It's structural.
Fragmented Model: Idea → Creative → Coordination → Tech → Content → Coordination → Creative → Approval → Execution Time lost: Days or weeks per cycle. Each handoff introduces delay, misinterpretation, and the risk of the original meaning getting lost entirely.
Closed-Loop Model: Idea → Lead → Execution Time lost: Minimal. The person who understands the idea is the same person who can execute it. No translation required.
The shift isn't about working harder. It's about eliminating the structural friction that makes hard work feel like it's going nowhere.
Three Questions for Leaders
Ask yourself these questions about your current team.
Before you add another person to a struggling project, sit with these three questions:
Is there someone on this project who can independently drive from concept to completion?
If not, you have a dependency problem. Adding more people won't solve it — it will deepen it.
How many people does a decision need to pass through before it becomes action?
If more than two, you have a friction problem. The solution isn't more coordination — it's fewer handoffs.
Is my project manager coordinating — or actually executing?
If they're only coordinating, they're not moving the needle. Coordination is necessary but not sufficient. Execution is what creates progress.
These questions don't have comfortable answers. But they're the right questions.
A Wider Observation
What I've learned across multiple complex projects.
The projects that move fastest aren't the ones with the most people. They're the ones where someone can "horizontally traverse" every function — understand creative intent, technical restrictions, operational reality, and human dynamics — and keep everything synchronized without losing momentum.8
This is a rare capability. It doesn't show up on a standard job description. It doesn't fit neatly into an org chart. But it's the difference between a project that delivers and one that produces beautiful documentation of why it didn't.
The underrated skill isn't strategic vision or creative talent. It's knowing how to make things happen — not just how to make things look good on paper.
Closing Reflection
Before you ask for more headcount, ask a different question.
The next time a project stalls, resist the instinct to add more people. Instead, ask a different question:
Who do we already have that can do more?
Is there someone on this team who can hold the full picture — the strategic intent, the operational constraints, the human dynamics — and drive from concept to completion without losing the thread?
If the answer is yes, give them the authority to close the loop. If the answer is no, that's the real gap you need to fill.
The biggest teams aren't always the most effective. The most effective teams are the ones where someone can close the loop.
"More people don't solve complexity.
People who can connect the dots do."
Professional Opinion & IP Notice
This article is original intellectual property drawn from direct professional experience, independent field observation, and proprietary analysis. The views expressed are solely my own and do not represent any employer, client, or affiliated organisation. No part of this work — including its frameworks, arguments, or structure — may be reproduced, forwarded, quoted at length, or used in any form without explicit written authorisation. If you are interested in referencing or republishing this content, please get in touch.