When One Person Becomes the Project Plan
Every project has that moment.
A decision stalls. A requirement feels unclear. A blocker appears.
And someone says, “Let’s just check with David.”
At first, it feels efficient. Reassuring, even. There’s someone who knows. Someone who can fix it.
But over time, that sentence starts showing up everywhere in design discussions, testing delays, and stakeholder escalations. Slowly, without anyone formally deciding it, one person becomes the system holding everything together.
Here’s the uncomfortable truth:
That person isn’t your solution. They’re your workaround.
And more often than not, this isn’t a people problem. It’s a clarity problem, one that quietly builds through unclear expectations, reactive hiring, and gaps in how the team was formed in the first place.
The Star Performer Isn’t the Issue
Let’s be clear, your strongest resource isn’t the problem.
They’re the ones stepping in when things aren’t defined, when decisions aren’t owned, and when the team doesn’t fully align. They hold context that others don’t have. They bridge conversations that were never properly structured. They compensate for gaps no one formally acknowledged.
In many Workday projects, this person ends up doing three jobs:
- Translating unclear requirements
- Making decisions no one owns
- Connecting workstreams that were never aligned
That’s not excellence. That’s compensation.
Your star performer is doing the job that your process didn’t define.
Where It Actually Breaks: The 6 Gaps That Build Dependency
Dependency doesn’t happen overnight. It builds quietly through interconnected gaps.
Expectation Gap: No One’s Fully Clear
When outcomes, ownership, and decision rights aren’t defined, teams default to validation.
You’ll see:
- Constant “check with X” moments
- Rework due to misalignment
- Slower decisions masked as collaboration
What it creates: A confidence gap
No one moves unless someone else confirms it.
Formation Gap: Roles Don’t Match Reality
This is where things start compounding.
Hiring often happens under pressure and is based on availability, titles, or urgency but it also requires to consider capability needs.
The result?
- Critical skill gaps go unnoticed
- Teams look complete on paper but struggle in execution
- One or two strong profiles carry disproportionate weight
And here’s the risk most teams underestimate:
When hiring is delayed or rushed, capability gaps reshape it.
Work gets rerouted. Responsibilities blur. The “go-to person” becomes inevitable.
What it creates: A capability gap
The team exists, but it doesn’t function as intended.
Context Gap: Only One Person “Gets It”
When knowledge isn’t shared, it accumulates.
One person understands the decisions, the trade-offs, the history. Everyone else operates on partial context.
This leads to:
- Repeated explanations
- Misinterpreted requirements
- Increased reliance on one individual
What it creates: A visibility gap
Knowledge becomes concentrated rather than collaborative.
Execution Gap: Work Isn’t Structured
Without clear workflows and handoffs, work becomes reactive.
You’ll notice:
- Tasks bouncing between people
- Delays in simple activities
- Firefighting becoming routine
What it creates: A flow gap
Work moves, but unpredictably and impacts delivery.
Ownership Gap: Everyone’s Involved, No One’s Accountable
When ownership isn’t explicit, responsibility becomes shared and diluted.
This shows up as:
- Tasks sitting idle
- Duplicate efforts
- Escalations for basic decisions
What it creates: An accountability gap
People contribute, but no one owns.
Knowledge Gap: Nothing Is Truly Documented
Documentation is often deprioritised when timelines tighten.
But the cost shows up later:
- Relearning the same things
- Slower onboarding
- Dependency on memory instead of systems
What it creates: A continuity gap
Every absence feels like a reset.
Why This Feels Like a “People Problem” (But Isn’t)
When delivery slows or dependencies grow, the instinct is clear:
“We need stronger profiles.”
But adding more people doesn’t fix unclear roles.
Hiring more seniors doesn’t resolve missing ownership.
In fact, without clarity, even strong hires struggle to integrate. They either overlap, underperform, or unintentionally increase dependency.
You don’t need more stars. You need defined roles and distributed capability.
Or put simply:
You’re not under-resourced. You’re under-defined.
The Real Risks (Beyond the Obvious)
When overdependency leads to project fragility.
- Decisions get delayed but appear “aligned”
- Burnout builds quietly in your strongest contributors
- Confidence grows around one individual instead of the system
- Delivery becomes difficult to scale or stabilise
- Hiring turns reactive, focused on urgency
And the biggest risk?
By the time this becomes visible, timelines are already under pressure and costs are already higher than planned.
Fixing It Without Slowing the Project
You don’t need a full reset. But you do need targeted corrections.
- Clarify Outcomes
Define what success looks like for each role
- Define Ownership Clearly
Who decides? Who executes? Who supports?
If this isn’t clear, dependency is inevitable.
- Rebalance the Team (Even Mid-Project)
Look beyond headcount. Identify missing capabilities.
Sometimes, the right hire at the right time prevents weeks of rework later.
- Reduce Dependency Intentionally
- Shadowing critical roles
- Paired ownership models
- Regular knowledge checkpoints
Make knowledge transfer part of execution.
- Fix the Hiring Input
This is where most projects slip.
Don’t ask for:
“Another senior resource”
Ask for:
- Specific capability gaps
- Defined responsibilities
- Clear outcomes
Because late hiring is expensive, but unclear hiring is even more costly.
If One Person Leaves, Does Your Plan Survive?
That’s the simplest test of team strength.
If everything depends on one person, it is a structural problem.
A strong project doesn’t rely on one talent to hold it together. It delivers because responsibilities are clear, capability is distributed, and the team is built to function.
If you’re seeing the same bottlenecks every week, it’s not a coincidence. It’s a signal.
Fix the structure. Define the roles. Hire with intent, early enough to matter.
Because stronger delivery doesn’t come from working harder.
It comes from building the team right.
