#12: The Morphology of a Delay

Not All Delays Are Created Equal

I once managed a procurement cost optimization project for a huge bottling company.

From day one, it felt delayed. We were in constant motion—meetings with vendors, renegotiating contracts for PET preforms, glass bottles, labels, logistics, raw materials. The team was working at maximum capacity. Yet my boss kept the project status red, constantly unhappy with our timeline progress, applying relentless pressure.

When we finally delivered, senior managers said something surprising:

"This has never been done so quickly before."

What was wrong?

The plan was wrong.

This experience made me realize that not all delays are created equal. And understanding the difference can save your project—and your sanity.

The Hidden Benchmark: The Execution Optimum

Traditional project management tracks Plan vs. Actuals.

We use Schedule Variance (SV) and Schedule Performance Index (SPI) to measure how we're doing against the baseline.

But there's a third dimension we rarely acknowledge:

The Execution Optimum.

The Execution Optimum is the timeline people should be able to achieve, given the project's realities (type of project, experience with such projects, benchmarks, team capabilities, constraints, etc.).

Theoretically, it is not too wide (relaxed timeline) nor too narrow (hardly achievable). It is the middle, the optimum.

Think of it this way: if you're building a standard two-story house, the industry average might be 8 months. But your specific project—given the site conditions, local regulations, and team experience—has an Execution Optimum of 9 months. That's the best you can realistically achieve.

Now, what if an executive pushed you to plan for 5 months and you deliver in 8 months?

How big is the delay?

Is there a delay?

The first dimension is key to understanding the following two types of delays.

Type A Delay: The Planning Gap

The Situation:

You plan for 5 months.

The Execution Optimum is 9 months.

You deliver in 8 months.

You're "late" by 3 months. Everyone feels the pressure. The status is red.

But here's the truth: you executed realistically, although not up to expectations. You came close (or even in advance) to the best possible outcome (the Execution Optimum).

This is what happened on my procurement project. We committed to an aggressive timeline under executive pressure. The Execution Optimum for complex, multi-vendor negotiations was simply longer than what we promised.

We executed exceptionally well, but we looked "delayed" the entire way.

The Damage:

This type of delay causes soft damage—but don't underestimate it:

• Expectation gaps with stakeholders and sponsors
• Downstream dependencies get impacted (other teams waiting on you)
• Trust erosion—people start doubting your competence
• Constant "red status". Team morale suffers.

The business case might still hold. The work quality is there. But the perception is broken.

What to Do:

First, be clear about your situation.

Type A usually comes from too strong of a top-down push. An executive wants something fast because it fits their mental model or desire, not because it's realistic.

Do your math. Emotions and desires can be tackled through facts. Well-ordered facts.

Let's say your boss wants a new product feature in 2 months—before Christmas. It would be perfect to have this before the strong sales period, right? That's what his brain keeps telling him.

You cannot simply say "no." So start collecting data and estimating: How long does it take to develop such a feature usually? How many resources are needed? How many do we have available in that period? Etc.

The idea is you bring a correct number as an estimate, in a way that they will trust what they see.

"Hey, the average time for such a feature is 2.5 months—here is the data from the last 5 times we did something similar. Furthermore, the 3 developers that can make it in 2.5 months are working on the other assignment, which is also a must for Christmas. Should we move them away from it and aim for 2.5 months, or we better work on another plan?"

Fix the planning process and manage stakeholder expectations, not the team. You have an estimation problem, not an execution problem. Or at least—not yet.

Type B Delay: The Execution Drift

The Situation: You plan for 9 months. The Execution Optimum is 9 months. You deliver in 14 months.

This is the classic delay—what most PMs think of when they hear "project delay."

Your plan was realistic, but execution drifts away.

The Damage:

This is where real business damage occurs:

• The business case deteriorates—more costs, delayed benefits
• Resources are inefficiently used, burning cash
• Market timing may be missed
• Team confidence and momentum erode

Unlike Type A, this isn't about perception. This is actual value destruction.

This is where PM intervention matters most.

What to Do:

Early detection ->  Root-cause analysis -> Action Plan.

First, we need to be awake and react in the earliest possible moment. We said you will be late for the 9-month deadline. You must realize months before month 9 that you are heading towards 14 months. (SPI and SV thinking helps a lot here!)

After you capture it, you need to dig. First step is to create data, if not readily available. We pull it from day-to-day work and what our people do (or don't do).

But numbers alone aren't enough. We basically need the data to get to the actual cause of the delay—the root cause.

You may think the analyst is slow on creating the deliverables you need. However, it may be due to extra-long waiting times for certain reports to be exported from the system. And that may be caused by poor database query optimization or insufficient server capacity during peak hours. The analyst isn't slow—they're blocked by infrastructure bottlenecks you didn't see.

You get the point—you need to dig.

Once you covered detection and identified the root-cause, it is time to move with an action plan. Consider a project reset, rebaseline, increase oversight, address resource or performance issues – use your PM magic.

Conclusion

Different delays need different responses.

Planning Gap (Type A) is about soft damage—expectations, communication, trust. Fix your planning process. Bring data. Manage stakeholders. Protect your team's morale—they may have performed brilliantly.

Execution Drift (Type B) is about hard damage—business case destruction. Dig into root causes. Act decisively. Reset if needed. This is where your project management skills are tested most.

Understanding which type of delay you're facing is the first step to solving it.