Cost of Delay is a concept that can be used to determine which product or product feature should be given a higher priority, and it’s a mandatory concept for every Digital Product Company.
ADAPT Methodology® is a unique Digital Product Development framework to change traditional project-centric companies toward product-led companies!
Society changed and leaders need support in the way how they lead and design their digital product organizations, that is the reason why the ADAPT Methodology® was created, but now let’s get a deep dive into Communities Of Practice if you want to get a deeper knowledge about this topic.
A lot of companies are now taking the Cost of Delay (CoD) into account when it comes to projects and running their company. Most people are admittedly confused about this concept as they look at CoD as some mathematical formula that can give exact revenue numbers. The cost of Delay is so much more than that.
Cost of Delay – An Introduction from Joshua Arnold on Vimeo.
The cost of Delay is a means of understanding and sharing the impact of time against a projected result. It provides companies with a way to compute and compare the cost of not finishing a project or feature by opting to do it at a later time.
In layman's terms, the Cost of Delay means exactly what the word implies. It is the loss or postponement of a benefit or value because of a delay. For instance, you left home 15 minutes late.
This delay led to your being stuck in traffic for more than an hour, which in turn caused you to be late for an important meeting. You can probably imagine what the day's delays have cost you.
However, the stakes are higher when it comes to delays in business. A delayed project or feature means extended labor costs and lost opportunities. It can also mean the release of substandard products and a damaged reputation.
Backlogs in business can cause a drop in revenue. This is why some experts say that if you want to make a profit or save money, you have to prioritize your backlog in terms of money.
Bear in mind that each product or project has different features or benefits.
Consumers often think all these features are important. But the reality is that each feature takes a different time to create and implement.
They also don't have the same level of worth in the business. Prioritizing one means limiting or delaying the other. And every day that a feature is not in production means another day that the company is not profiting from it.
By utilizing the Cost of Delay, the company can determine which feature will cost them the most by a delay in the delivery. It also sets a clear guideline on what projects would matter most for the company and other stakeholders without the friction of other decision-making obstacles which brings us to the next point below.
Are you familiar with the following acronyms and concepts?
MoSCoW Method (Must have, Should have, and Could have Would have) - An attempt to make qualitative prioritisation based on opinions.
Equity Model - Prioritizations are based on allocated funds for each department.
HiPPO (Highest Paid Person's Opinion) - Priorities are made by the person who has the fattest paycheck.
If you're familiar with all these concepts (and HiPPO reminded you of a loudmouth in your office), then it's easier for you to understand how flawed and dysfunctional these frameworks of prioritizations are.
The MosCow method often puts everything in the "Must-Have" bucket. Imagine if your company has a limited resource and manpower. The quality of work and output will surely suffer.
The Equity method could have been a "logical" approach to prioritization because it makes sense to prioritize departments with higher budgets. Unfortunately, an organization operates in a co-dependency environment in which departments affect the performance of other teams.
A HiPPo is rarely a reliable framework. This is why we have the adage that says "Two heads are better than one".
These counterproductive default prioritization processes of companies can be easily remedied by determining the Cost of Delays. If you put everything into perspective and provide figures, and context to different factors involved in the decision process, your company will easily aim in the right direction.
Using the framework of CoD, the company has to determine what delaying or not doing the project at all will cost the company. This is challenging as there's an undefined financial result. So how can an organization decide on its next step?
Based on what Don Reinertsen wrote in Principles of Product Development Flow, there are three elements to consider in CoD -
Reinertsen says that adding those three elements equals the Cost of Delay. He also introduced a model that assists organizations in determining the importance of each project and which one should be given priority. He calls this the Weighted Shortest Job First (WSJF). Essentially, WSJF is the Cost of Delay divided by the Job Size.
Now that the parameters and baseline formula have been established, the next step is to assign the value. The user has to understand that the values are subject to what the team wants to use. Some use a Fibonacci Scale while others assign points agreed on by the team.
There are several reasons why quantifying the Cost of Delays helps a company:
Contrary to what most people believe, quantifying the CoD can be easy as long as you remember its three key elements. Start by understanding the benefits or its business value. Then think about the impact time will have on the project's value. Combine all these into a CoD in terms of $/week.
Doing this also helps a company test its assumptions regarding the project, thereby reducing the economic risk. Following these three steps can make quantifying the CoD simpler:
Put three or more features of the project in a table and compare them based on the duration it would take to develop each feature and its value.
Once you have compared the features, envision different scenarios that show when you would get a return on your investment based on the choice of priority.
Visualize how these features would fare if:
Evaluate the financial impact of the three features based on the four priorities. You might be surprised by the results. Sometimes you might find that doing the most valuable feature first is not the best choice financially or that doing the feature that can be finished quickly might cause delays in the project.
There are circumstances wherein a qualitative evaluation of the cost of delay makes more sense than a quantitative one. This takes more effort and imagination but is well worth it. Like other CoD methods, a qualitative evaluation will also help a company in prioritizing a project and changing the focus of discussion.
Cost of Delay has two key ingredients - Value and Urgency. Unfortunately, people are not very good at distinguishing "urgency" and "value." But when it comes to making business decisions, one has to understand how valuable something is and how urgent it is.
When using this method, you can use a 3x3 matrix. Value can be placed on the vertical axis and Urgency on the horizontal. Instead of values, you can use more descriptive terms for their values.
Let's start with Value. Instead of using a Low, Medium, or High rating, you can use "Meh," "Cool," or "Bodacious"
Bodacious represents the highest value. These are the factors that if we're successful, we'll have a bodacious future.
Cool is in the middle range. These are factors that are dependent on the context. For instance, these can be things that our customers love and we want to push them on.
With it, our customers will either want to remain with us or pay us for it. In a different context, it can also mean that the feature will provide us with even more revenue.
Of course, Meh is at the bottom of the spectrum. These are features that are still good but not something too exciting.
Once you have determined the value, it's time to focus on Urgency. Again, you can use more descriptive expressions like "Right Now," Soon" or "Whenever."
Plug all these determinants in your matrix and rate the features or your ideas based on them. This will give you a feel for what the Cost of Delay is from a qualitative perspective.
Delays in a project can be costly so companies have to learn to prioritize. Using the Cost of Delay concept can help in determining which ones to put first to maximize profits, business impact, and strategic use of limited resources.
We enable leaders to become highly valued and recognized to make an impact on the World by helping them to design Digital Product Companies that will thrive and nourish in the Digital Age, we do this by applying our own ADAPT Methodology®.
If you want to know how we can help you to start your transformation please check out our: Training.
If you are interested in doing a transformation in your company please check out our: Consulting.