A project is behind schedule.
The team is working long hours. Milestones are being tracked. Risks are documented. Status meetings happen every week. The project plan is updated religiously.
And yet, progress remains slow.
The natural response is to look at the plan.
Are the dates realistic? Are there enough resources? Are dependencies being managed? Do we need to rebaseline the schedule?
Sometimes, the answer is yes.
But often, the project plan is not where the real constraint lives.
The biggest execution constraint is frequently outside the plan.
It lives in the decisions that are not being made, the priorities that keep changing, the ownership that is unclear, or the dependencies that no project manager has the authority to resolve.
The plan can be perfectly reasonable and execution still fail.
A project plan tells us what needs to happen, when it needs to happen, who is expected to do it, and what depends on what.
But a plan does not automatically create the conditions required to execute.
Consider a program where three teams are dependent on a product decision.
The decision is shown as a milestone.
The milestone slips.
So, the team updates the schedule.
Then it slips again.
Another status meeting. Another escalation. Another date moved.
At some point, the organization may conclude that the team has an execution problem.
But the team may not be the constraint at all.
The constraint is the unresolved decision.
Until that decision is made, every downstream activity is effectively waiting.
The project plan is simply documenting the symptom.
So, when an initiative repeatedly misses commitments, don't stop at:
"Which task is late?"
Ask:
"What is preventing this task from moving?"
That second question takes you one level deeper.
A late deliverable may be caused by:
- ›a decision waiting for executive approval
- ›competing priorities across functions
- ›unclear ownership
- ›an unresolved architectural choice
- ›an external dependency
- ›conflicting incentives
- ›a governance process that takes too long
- ›requirements that continue to change
- ›a risk that nobody has the authority to accept
None of these necessarily appears as a problem with the project plan.
Yet any one of them can determine whether the plan succeeds.
The real execution challenge isn't always the work. Sometimes it's the conditions around the work.
In the next DAES Insight, I’ll explore three places leaders can look for hidden constraints, and what to do when they find them.
DAES Insight:
Diagnose the constraint before you optimize the plan.