metricData, experimentation & growth

Cost of Delay

Cost of Delay estimates the economic or mission value lost while an initiative remains unavailable, reframing priority around time.

Download Markdown (.md)

01What it means

Cost of Delay represents the value forgone because an outcome is delivered later rather than sooner. Depending on context, that value may include delayed revenue, avoidable operating cost, missed learning, increased risk exposure, or harm to users and mission outcomes.[1][2][3]

Value forgone while an outcome waits Different outcomes lose value through different delay profiles
  1. 01Constant lossSimilar value forgone for each unit of time
  2. 02Fixed-date urgencyCost rises sharply around a deadline or event
  3. 03Decaying opportunityValue falls as a window closes or competitors move
  4. 04Risk or harm exposureUsers or the mission continue bearing avoidable cost

Estimate ranges and confidence from evidence; compare delay cost with job size, dependencies, and capacity instead of disguising assumptions as precision.

02Why it matters

Backlogs often compare total benefits while ignoring timing. Cost of Delay reveals why a smaller initiative with a closing market window or accumulating risk can deserve attention before a larger initiative whose value changes little over time.

03When to use it

Use Cost of Delay when sequencing valuable work whose benefits or risks are time-sensitive. It is most useful when teams can describe how value changes with delay and compare options over a shared interval, even if estimates are ranges rather than exact currency.

04How it works

  1. Define the outcome, affected stakeholders, and a common unit of delay such as a week or month.
  2. Identify value that is postponed or lost, including revenue, savings, learning, risk reduction, service quality, or mission impact.
  3. Describe the delay profile: relatively constant, urgent around a date, or decaying as an opportunity closes.
  4. Estimate a range and confidence level using evidence rather than disguising assumptions as precise forecasts.
  5. Compare the cost of waiting with job size, dependencies, and capacity; update estimates when the context changes.

05A practical example

Example

A marketplace can improve general recommendations or complete a tax-reporting change before a regulatory date. Recommendations have larger long-term upside, but delaying compliance beyond the date creates rapidly increasing operational and customer costs. The team schedules compliance first and preserves discovery work for recommendations.

06Where it breaks

Many consequences are difficult to express in one unit, and monetary estimates can marginalize safety, accessibility, or public value. Forecasts are uncertain and vulnerable to advocacy bias. Cost of Delay should inform sequencing, not justify unsafe speed or pretend that all value is financial.

Common mistakes

  • Estimating total value but not how that value changes with time.
  • Forcing intangible harms into spurious dollar precision.
  • Ignoring dependencies or the cost of interrupting work already in progress.

07Sources

  1. Cost of DelayScaled Agile, Inc. · Framework referenceCost of Delay
  2. Cost of Delay – interview with Don ReinertsenSofthouse · Creator interviewCost of Delay – interview with Don Reinertsen
  3. Second Generation Lean Product DevelopmentReinertsen & Associates · Authoritative practitioner sourceSecond Generation Lean Product Development
View saved topics

Start typing to search titles, definitions, categories, and frameworks.