Skip to main content

Cost of Delay. What Does It Mean?

Jim Hayden
Reading: Cost of Delay. What Does It Mean?

Oftentimes when I ask Product Owners how they choose which projects their teams focus on first, they don’t have a technique for prioritization.  Cost of Delay is a concept that a lot of organizations are using and that has gained traction over the years. Unfortunately, many people are still struggling with the concept of Cost of Delay, so I want to put it down in laymen’s terms here in this blog.  Ultimately, the Cost of Delay is a concept that helps you decide—if you have two or more efforts—which order to perform them.

“Cost of Delay” in layman’s terms is the Cost of Delay.

“Well Duh,” you say … doesn’t really help to define the term using the term itself!  Thanks a lot!”

You’re absolutely right, so let’s look at it from a pragmatic vantage point. The cost of delay can mean the loss or deferment of a benefit/value due to the delay and/or incursion of some sort of penalty.

For example, we have all experienced the “cost of delay” getting out of the house late to go to work.  In Atlanta, a 15-minute delay getting out of the house could result in a 30-minute commute becoming an over-hour nightmare. Couple being late with the “penalty” implications of missing an important meeting, and you can clearly visualize the “cost of delay”.

In business, we do projects to accrue some expected benefit from the result of that work.  Delay the realization of that project by a quarter, and you’ve incurred a “Cost” of a quarter’s worth of that benefit this fiscal year.

A graph that shows value over time. Illustrates that delaying a project will make you incur a cost of delay.

Miss an expected market window of opportunity and the Cost of Delay will include an even greater penalty.

Graph that shows value over time. Miss the market window and cost of delay increases.

In Principles of Product Development Flow, Don Reinertsen speaks extensively about Cost of Delay.   He leverages a model that visualizes projects as rectangles with their vertical axis as the Cost of Delay and their horizontal as the time it takes to implement them.

Leveraging this model enables us to determine which order to do the projects to minimize the Cost of Delay.  We can visualize this by plotting the projects on a waterfall diagram as shown below:

side by side Waterfall diagram that illustrates hoe to minimize cost of delay by accelerating projects early

The first project incurs zero Cost of Delay because it was begun immediately.  The second project’s Cost of Delay can be visualized as it waits to begin.  Likewise, the third project’s Cost of Delay can be envisioned as it waits for the others to complete.

Therefore, doing the projects in the order on the left diagram incurs less cumulative Cost of Delay than the order indicated on the right diagram.

You don’t want to prioritize your projects to start slowly and accelerate at the end. You want them to ramp up early and taper off to minimize the Cost of Delay.

see your ROI sooner by implementing cost of delay to your project

Think of this in a different way …  What if we plotted value (above) rather than Cost of Delay.  Wouldn’t you rather have 83% of your money in the bank halfway through the time-period vice only 12.5%?

Final Thoughts on Cost of Delay

One thing to keep in mind while prioritizing projects is: overall value is not just money.  Nor is all cost paid in dollars.  Certainly, you’re looking for a return on investment; however, you also need to consider what will happen to your market share, customer loyalty, and brand integrity as you make tradeoffs to meet or delay deadlines. For example, if you choose to delay a project and your biggest competitor releases their version of your product, what will that do to your market share?  On the flip side, what if you rush to market and release buggy software? How will that impact customer loyalty and, perhaps, overall sales? Will it detract from your brand integrity? These nuances should be saved for another blog post, but I’d be remiss if I didn’t mention some of the less obvious, but ultimately tangible, costs associated with delay.

Remember, too, that the value placed on projects is an expected or anticipated value.  Companies do projects with the hypothesis that they will result in a certain benefit.  What if that hypothesis is incorrect?  Wouldn’t you rather have more time to adjust (so you can hit the overall goal) than less time?!?  How many times have you or your executives bemoaned “I wish we’d known that sooner!!!”   There is certainly a “cost” associated with late feedback!

I hope that this overview of the Cost of Delay is helpful.  For far greater detail, please read Don Reinertsen’s book The Principles of Product Development Flow in which he goes to extensive lengths to describe the Cost of Delay.

Lastly, be sure to check out Marty Bradley’s post on the Cost of Delay. Marty has some really good ideas on this stuff too. In his post he even provides this interactive Excel spreadsheet to help you calculate your cost of delay.

 

Next Should Work Be Assigned During Sprint Planning? with Chris Li

Jim Hayden brings over 25 years of leadership experience pragmatically solving complex problems and delivering tangible, bottom line results. The discipline, teamwork, communication, coordination and ability to “observe and adapt” flying fighter aircraft in the US Air Force are the foundation of what he brings to businesses today.

Comments (2)

  1. Andrew Reeves-Hall
    Reply

    Thank you for this posting! May I use the drawings in my training of colleagues (credit given)?
    Also, the drawing showing the blocks has a mistake, I believe. On the right-hand diagram, box “A” and “B” are reversed (the “A” is a square on left diagram).
    Best wishes,
    ~Andrew~

    Reply
    • Jim Hayden
      Reply

      Absolutely Andrew! Be my guest! Thanks again … and I will correct that labeling! JH

      Reply

Leave a comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

What is the Worth of a Good Product Owner? w/ Tim Wise

This week, on SoundNotes, we’re featuring another question from a student in one of our Certified Scrum classes. The question came from someone who’s working in an organization that doesn’t see value in the role of Product Owner and isn’t convinced that it’s needed as part of the Scrum Team. The question: What is the […]

How Do I Use Scrum on Data Warehouse Projects? w/ Dave Nicolette

In one of my recent Certified Scrum Master classes, I had a number of students who were working on projects involving migrating from a legacy data warehouse to new data warehouses. Figuring out how to apply Scrum to the work they were doing presented a number of challenges and left some open questions.  Here are […]

Maximizing the Amount of Work Not Done

One of the principles of the Agile Manifesto reads: “Simplicity – the art of maximizing the amount of work not done – is essential.” Okay. What does that mean? Does it mean we should avoid doing our work to the extent possible? Well, not exactly. Consistency Between Lean and Agile Principles Without coming at the […]

Prioritizing the Work to Maximize Return w/ Dennis Stevens

This week, on SoundNotes, we’ve got Part 3 of a trio of interviews with LeadingAgile Chief Methodologist and Co-Founder Dennis Stevens. The series focuses on how to build an organization that can embrace change. In the final episode of the series, Dennis and Dave cover how to prioritize work being done to maximize return. During […]