Donald Reinertsen spent three decades studying product development economics. His conclusion, first published in "The Principles of Product Development Flow" in 2009, still lands like an uninvited truth. Roughly 85% of product managers do not know the Cost of Delay for their projects [1]. Not a rough number. Not a rough range. Nothing.
That statistic has not aged. It has calcified.
Think about what it means. The people responsible for sequencing work, defending roadmaps, negotiating with engineering, and reporting to executives cannot answer the one economic question that matters most. What does it cost us if this ships a month late? Without an answer, prioritization collapses into opinion, politics, and whoever spoke last in the steering meeting.
What Cost of Delay Actually Is
Cost of Delay is the economic value lost per unit of time when a feature is delayed. That sounds abstract until you apply it to two real features.
Feature A generates $50,000 per week when it ships. Feature B generates $5,000 per week. Both take the same effort to build. A stack ranking exercise treats them as equal candidates for the next sprint. A Cost of Delay calculation exposes the obvious. Delaying Feature A by one month costs the business $200,000 in foregone value. Delaying Feature B by one month costs $20,000. Ten times the economic gap, invisible in story points, obvious in dollars.
Reinertsen's exact words in the book are worth memorizing. "If you only quantify one thing, quantify the Cost of Delay" [2]. Not velocity. Not throughput. Not story point burndown. Time, measured in money.
This reframes prioritization as an economic discipline rather than a negotiation. Product School's analysis makes the same point bluntly. Without a Cost of Delay model, teams optimize for whichever metric is loudest in the room [3]. That is how feature factories get built.
Why Invisible Queues Bleed Value
Reinertsen's deeper insight runs underneath the Cost of Delay headline. Product development queues are the primary driver of poor performance, and they are invisible [4].
In a factory, inventory piles up where you can see it. Half-finished parts sit on the floor. Managers walk past them, count them, and know where the bottleneck lives. In product development, the inventory is digital. Requirements waiting for clarification. Designs waiting for review. Code waiting for QA. Decisions waiting for a meeting that gets rescheduled twice. None of it shows up in a spreadsheet. All of it consumes economic value every day it waits.
When you combine invisible queues with unknown Cost of Delay, you get the worst of both worlds. Work sits idle, and nobody knows how much that idling costs. The organization runs on the comforting illusion that busy people mean value is being created. Reinertsen's economics say otherwise. Capacity utilization above about 80% makes queues grow exponentially, and every day of queue time eats the Cost of Delay you never calculated.
Why Most Teams Skip It
Teams default to relative estimation because quantifying economic value feels uncertain. Story points, T-shirt sizes, MoSCoW buckets, and stack rankings feel safer because they do not force a number with a dollar sign attached to it. Uncertainty gets outsourced to the appearance of rigor.
This is a trap I wrote about in "Organizational Complexity Is Accumulated Decision Debt." Bloated backlogs with 300 items are not prioritization. They are avoidance. Every item that sits in a backlog without a Cost of Delay estimate is a decision postponed into a later quarter where it will get postponed again.
Canny's survey of prioritization frameworks across product organizations shows the pattern clearly [5]. Teams adopt multiple frameworks in parallel, RICE on Mondays, MoSCoW on Wednesdays, stack ranking on Fridays. Each framework gives a different answer. None of them reference economic value. Monday.com's prioritization guide lists fifteen frameworks without a single mention of Cost of Delay as a primary lens [6]. The message to product teams is clear. Pick any framework, they are all equivalent. Reinertsen would disagree sharply.
An imprecise economic estimate beats a precise effort estimate every single time. A Cost of Delay number that is wrong by 30% still produces better sequencing than a story point total that is precise to the half-point.
WSJF Is Just CD3 in a Suit
Reinertsen built the mathematics behind this. CD3, Cost of Delay Divided by Duration, produces a rational sequencing algorithm. Shorter, higher-value work goes first. The economics are inescapable once you have the two numbers [7].
SAFe packaged CD3 as Weighted Shortest Job First and made it famous. That is fine. The branding matters less than the underlying discipline. Whether you call it WSJF, CD3, or Reinertsen's rule, the math is the same. Quantify time in economic terms, divide by effort, and let the numbers sequence the backlog.
Why AI Makes This More Urgent
Execution is getting cheaper every quarter. Foundation models and code generation compress development cycles. Teams that used to need three months now need three weeks. This is the backdrop I covered in my previous article "When AI Clones Your Product, What's Left?" The competitive advantage is no longer in how fast you can build a feature. It is in what you choose to build and when.
Time, however, is not getting cheaper. Time windows are shrinking. A feature that gave you a six-month competitive lead in 2022 gives you six weeks in 2026. Competitors clone capabilities faster than anyone anticipated. Pricing time has gone from a useful discipline to a survival capability.
In "The Time Poverty Paradox" I showed that product leaders spend 66% of their time on coordination work while lacking the analytical capacity to influence the outcomes they are accountable for. Time poverty is exactly what prevents the Cost of Delay analysis from happening. The analysis takes an afternoon of clear thinking, and clear thinking is the scarcest resource in most organizations.
The Starting Move
You do not need a spreadsheet with 40 cells to begin. You need one backlog item and one honest conversation.
Pick the next feature your team is about to build. Ask three questions. What weekly revenue do we expect when this ships? What happens if this ships six months later instead of next sprint? Does this unlock any other work that is currently waiting?
The answers will be uncomfortable. They will feel uncertain. They will also be the first economic reasoning your team has produced in months. Treat the numbers as a first draft, not a final answer. Then do it again with the next feature. And the next.
After five items, you will notice something. The ranked list will look different from your current backlog order. That difference is the value of the discipline.
Closing the Loop
Evidence-Based Management gives you the measurement architecture to track whether your prioritization is actually producing value. Current Value and Unrealized Value sit on either side of every Cost of Delay calculation. A Product Operating Model worthy of the name treats time as an economic variable, not a project management detail.
Reinertsen's 85% number is not a data point. It is an indictment. Seventeen years after the book was published, the majority of product teams still cannot answer the one question that separates product management from feature management. What does time cost us?
Price your time. Everything else is a negotiation about opinions.
Ralph Jocham is Europe's first Professional Scrum Trainer, co-author of "Professional Product Owner," and contributor to the Scrum Guide Expansion Pack. As an ICF ACC certified coach, he works with organizations to build Product Operating Models where strategic clarity, operational excellence, and adaptive learning create measurable competitive advantage. Learn more at effective agile.
References
[1] Reinertsen, D.G. (2009) The Principles of Product Development Flow: Second Generation Lean Product Development. Celeritas Publishing. Available at: https://www.amazon.com/Principles-Product-Development-Flow-Generation/dp/1935401009
[2] Black Swan Farming (2024) 'SAFe and Weighted Shortest Job First (WSJF)'. Available at: https://blackswanfarming.com/safe-and-weighted-shortest-job-first-wsjf/
[3] Product School (2024) 'Cost of Delay in Product Management'. Available at: https://productschool.com/blog/product-fundamentals/cost-delay
[4] Cotellese, J. (2023) 'Principles of Product Development Flow: Book Summary'. Available at: https://joecotellese.com/posts/principles-of-product-development-flow-book-summary/
[5] Canny (2024) 'Product Prioritization Frameworks: A Complete Guide'. Available at: https://canny.io/blog/product-prioritization-frameworks/
[6] Monday.com (2024) 'Product Prioritization Frameworks'. Available at: https://monday.com/blog/rnd/product-prioritization-frameworks/
[7] Wind4Change (2023) 'Cost of Delay Divided by Duration (CD3), WSJF, Reinertsen and SAFe'. Available at: https://wind4change.com/cost-delay-divided-duration-cd3-wsjf-reinertsen-safe/