Skip to content
Founders’ price Launch pricing for your first twelve months. 40 Playbooks, 40% discount for Founders. View the playbooks →

Cost of Delay

TTool · Cost of Delay

By , Editor · · Playbooks for Leaders

Concept and planning by Will Rowan. Researched and drafted with AI. Edited and checked by Will Rowan.

“A framework quantifying the economic impact of time on feature value, developed by Donald Reinertsen and popularised by Joshua Arnold.”

You're arguing about which feature goes next. Everyone has an opinion. Nobody has a number.

Cost of Delay is Donald Reinertsen's technique for quantifying the economic impact of time on feature value. You ask one question — what does it cost us each week we don't have this? — and let the answer sequence your backlog.

A three-step horizontal flow numbered 01 to 03, labelled frame, score, and compare, each with a short caption about setting a cost-per-week-of-delay figure.
Method visual: Cost of Delay

It kills subjective priority debates. Different features have different delay profiles: some decay steadily, others hit a cliff at a deadline, and some lose all value overnight. Once you've mapped those profiles, sequencing becomes arithmetic rather than politics — particularly when combined with Weighted Shortest Job First (WSJF).

The technique demands real financial data, which is both its power and its constraint. Without credible numbers, the exercise produces false precision that's worse than gut feel. It also flattens out when every item has similar time sensitivity — if nothing's urgent, the model has nothing to differentiate.

Your next move: What's the weekly cost of the decision your team has been quietly deferring for a month — and would anyone in the meeting be willing to say it out loud?

What it looked like for them

Monitor110, 2005–2008. Monitor110 was a New York start-up that searched the internet for information institutional investors could act on. Jeff Stewart ran technology and product, Roger Ehrenberg ran the business side, and neither was in charge. The technology team tried to analyse most of the web in real time. Staff closer to customers wanted a smaller set of high-quality sources.

The company had raised plenty of money, so nobody had to settle the argument, and it ran for months. Ehrenberg's post-mortem blames the "two-headed structure". Monitor110 changed approach too late and closed on 15 July 2008. Every month the argument stayed open, the company paid for both directions. Cost of delay puts a number on that month before it passes.

- returns a SafeString and get.js throws on it }}
A move inside a Playbook

“The dashboard says we're fine but I don't believe it.”

Open the Playbook →

Share the Playbooks