Pricing your Queues: The Cost of Delay

“Better developer experience” won’t get you a budget. A dollar figure for every week of waiting will.

If you pitch cross-functional feature teams as a way to make developers happier, executives will nod politely, and nothing will change. To convince a CFO or a skeptical VP to restructure an engineering organization, you have to translate delivery mechanics into money.

The most effective tool I know for that translation is Cost of Delay.

What Cost of Delay Measures

Cost of Delay, a cornerstone of Donald Reinertsen’s The Principles of Product Development Flow, asks one simple question: if this feature ships a week later, how much money do we lose?

Every feature that generates revenue or saves cost has a weekly value. While it sits in a queue, that value is not being earned. Waiting is never free; it is just invisible on most dashboards.

A simplified version of the calculation has two parts:

• Unrealized value per week: the revenue the feature would earn, or the cost it would save, once it is live.
• Operational friction per week: what the business spends working around the missing feature in the meantime.

Add them, and you have the weekly cost of the feature not existing.

A Worked Example: The Billing Engine

Imagine a company building a self-service checkout and billing system.

Marketing estimates it will add $40,000 in monthly recurring revenue by reducing cart abandonment: roughly $10,000 per week of unrealized value.

Because checkout is manual today, the customer success team spends 20 hours a week onboarding customers by hand, costing about $1,000 per week in operational friction.

Cost of Delay = $10,000 + $1,000 = $11,000 per week

Now compare two ways of delivering it.

With horizontal teams (frontend, backend, DBA, QA, each with its own backlog), the feature takes 20 weeks, most of it spent in queues and handoffs:

20 weeks × $11,000 = $220,000

With a cross-functional feature pod that owns billing end to end and ships in thin vertical slices, the first working version goes live in 6 weeks:

6 weeks × $11,000 = $66,000

Same people, same technology, same codebase. The only change is the structure of the teams, and it is worth $154,000 on a single feature.

Using It in the Room

Cost of Delay is most powerful when someone makes a resource-utilization argument. The classic one is: “We can’t afford a dedicated QA engineer in every team. Let’s share one across three teams.”

Run the numbers with them. Say sharing QA saves $12,000 a month in salary. But the shared QA queue delays features by an average of 18 days, each feature is worth $50,000 a week, and the teams ship about one feature a month. Eighteen days is about 2.6 weeks, so that queue costs roughly $128,000 a month in delayed value, to save $12,000 in salary. Framed that way, it is not a staffing decision anymore. It is a bad trade.

A few habits make the numbers credible:

• Use the business’s own estimates. Let product and finance supply the weekly value. Your job is the delay, not the forecast.
• Use real lead times. Pull the actual waiting time from your ticket history, or better, from a value stream mapping workshop.
• Be conservative. A rough number everyone accepts beats a precise number nobody trusts.
• Offer an experiment. One pod with a dedicated QA engineer, one with a shared one. Measure both for a month and let the numbers decide.

Wrapping Up

Queues are the most expensive thing in your delivery system, and also the hardest to see. Cost of Delay makes them visible in the only language every executive speaks. Once the conversation moves from “how busy are our people?” to “how much is every week of waiting costing us?”, restructuring around flow stops being an engineering preference and becomes a business decision.

---

This article is adapted from Chapters 2 and 4 of my upcoming book, Vertical Velocity: How to Break Silos, Ship Faster, and Reclaim Engineering Joy. The book goes further, with the queueing math behind slow delivery, scripts for the conversations with managers who resist the change, and a Cost of Delay worksheet you can use with your own numbers. Follow this blog to hear when it’s out.