What Does It Cost To Delay Each Opportunity?

When every initiative is a priority, your teams inherit the job of deciding what actually gets done. They juggle competing requests, start more work than they can finish, and spend valuable time explaining why everything is taking so long. Another prioritization meeting may simply produce a still longer list of urgent commitments. Lean Portfolio Management brings a more useful – and interesting – question to the table: What does it cost us to delay each opportunity? That question helps move the conversation beyond who asked first, who speaks loudest, and whose initiative has the most impressive slide deck. (Sound familiar?) 

“Cost of Delay” makes the consequences of waiting visible. Will postponing an initiative mean lost revenue, continued operating costs, or a missed market opportunity? How does that impact change over time? Delaying an efficiency improvement might forfeit savings every week, while missing a market window could sharply reduce a feature’s value. Start with reasonable estimates and make the assumptions explicit. Dollar estimates help compare opportunities across the portfolio. Relative scores can help establish an initial order, but they won’t tell you what another month of waiting costs. Precision is welcome; however a six-week exercise to perfect the estimate somewhat misses the point. 

Weighted Shortest Job First (WSJF) adds delivery duration to the decision. Its economic foundation is straightforward: divide estimated Cost of Delay by estimated duration to identify work that can reduce the cost of waiting most effectively. Higher scores generally suggest earlier delivery, subject to dependencies and genuine constraints. This also invites teams to break large initiatives into smaller pieces that deliver useful outcomes independently – and earlier. A valuable capability shouldn’t have to wait for every enhancement bundled into the original proposal; some of those “extras” are passengers with very persuasive business cases. 

Then comes the difficult leadership decision leaders are actually paid for: choose what to finish and what will wait. An ordered portfolio only helps if you limit work in progress and give teams room to complete the most valuable work. Revisit the order as opportunities, urgency, and evidence change. Treat benefit estimates as hypotheses to test, and use feedback to improve the next decision. At agilityIRL, we help leaders turn competing priorities into practical economic choices and manageable commitments. Your portfolio can contain plenty of good ideas…your teams need a clear answer about which ones deserve their attention now. 

Too Many Priorities? Check Your Portfolio 

Can your organization explain why one initiative should happen before another—and give teams the capacity to finish it? 

Take this quick assessment to see how your portfolio prioritization practices stack up and identify where a small change could make a meaningful difference. 

Time: 3–4 minutes 
Instructions: Think about one portfolio or business area you know well. Choose the answer that best describes what usually happens today. 

1. How do initiatives become a priority? 

1. Seniority, persistence, or the latest urgent request usually determines the order. 

2. We discuss value, but different sponsors use different criteria. 

3. We compare initiatives using shared criteria and explain the resulting order. 

4. We use shared criteria, examine supporting assumptions, and make tradeoffs explicit. 

2. How clearly do you understand the benefits of proposed work? 

1. Most proposals describe deliverables rather than expected benefits. 

2. Proposals describe benefits, but estimates and assumptions are often unclear. 

3. Most proposals estimate benefits and explain the assumptions behind them. 

4. We compare benefit estimates consistently and challenge assumptions with relevant experts. 

3. How do you evaluate the cost of waiting? 

1. We rarely discuss what happens if an initiative is delayed. 

2. We identify deadlines or urgency, but seldom explain the consequences. 

3. We estimate the impact of delay using consistent relative comparisons or dollar estimates. 

4. We also examine how that impact changes over time, including market windows and deadlines. 

4. How does delivery duration influence sequencing? 

1. A. We choose priorities without considering how long they will take. 

2. B. We consider duration informally, often favoring quick wins or large strategic initiatives. 

3. C. We consistently weigh the cost of waiting against estimated delivery duration. 

4. D. We use that comparison to inform sequencing and make dependencies or exceptions explicit. 

5. How do you break down large initiatives? 

1. We generally approve and deliver them as complete packages. 

2. We divide them into phases, but benefits usually arrive near the end. 

3. We identify smaller pieces that can deliver useful benefits independently. 

4. We compare those pieces by value and urgency, then use feedback to decide what comes next. 

6. What happens when demand exceeds available capacity? 

1. We start more work and expect teams to juggle it. 

2. We acknowledge the overload, but rarely pause or defer anything. 

3. We limit active initiatives and explicitly decide what will wait. 

4. We maintain those limits and resolve exceptions by deciding what will stop, finish, or wait. 

7. When do you reconsider portfolio priorities? 

1. Mainly during annual planning or when a senior leader intervenes. 

2. Periodically, although commitments are difficult to change. 

3. Regularly, using changes in value, urgency, capacity, and dependencies. 

4. We also respond to new evidence and opportunities, making deliberate choices about existing commitments. 

8. What happens after work is delivered? 

1. We primarily check whether it met scope, schedule, and budget. 

2. We discuss benefits informally, with limited follow-up. 

3. We review actual outcomes against expected benefits. 

4. We use those findings to improve future estimates and investment decisions, treating estimates as hypotheses to learn from. 

Your results 

Each answer earns points: A = 0, B = 1, C = 2, D = 3. Your total is out of 24. 

Score	Your current pattern	Recommended next step
0–6	Competing requests drive the portfolio. Teams may be receiving more commitments than they can realistically complete.	Bring leaders together to order the active initiatives, identify expected benefits, and agree what will wait.
7–12	Useful practices, uneven decisions. Some economic thinking exists, but urgency and competing expectations may override it.	Apply a shared set of value, delay, and duration questions to a small group of upcoming initiatives. Make assumptions visible.
13–18	A foundation for economic prioritization. You have several practices that support deliberate choices, with gaps that may weaken execution.	Use your lowest-scoring answers to select one improvement. Check whether the agreed priority order actually controls what teams start.
19–24	Economic prioritization is established. Your answers suggest consistent attention to value, timing, capacity, and learning.	Test the quality of your estimates against outcomes and look for smaller delivery slices or emerging opportunities that deserve earlier attention.

Your score describes your reported practices. Your lowest-scoring answers point to the most useful conversations. A strong total can still hide a significant problem — for example, clear priorities alongside too much active work. 

Where to focus first 

Show recommendations for the respondent’s two lowest-scoring questions: 

Question	Suggested improvement
1. Priority decisions	Agree on shared criteria and record why an initiative ranks above another. Make leadership exceptions visible.
2. Benefits	Describe the expected outcome, estimate its benefit, and document the assumptions. Include relevant business and delivery expertise.
3. Cost of waiting	Ask: “What would another month of delay cost us?” Identify whether that impact stays steady or changes over time.
4. Duration	Compare Cost of Delay with delivery duration. Use WSJF to inform sequencing while considering dependencies and constraints.
5. Smaller delivery slices	Identify the smallest independently useful outcome. Estimate its own benefits rather than assigning it the value of the entire initiative.
6. Capacity	Set an explicit limit on active work. When something new starts, decide what finishes, stops, or waits.
7. Reprioritization	Establish a regular portfolio review that can change decisions, using updated evidence rather than status reports alone.
8. Learning	Schedule a benefit review after delivery. Use differences between estimates and outcomes to improve decisions without discouraging honest estimates.

Ready to turn competing priorities into clear choices? 

agilityIRL helps leaders apply Cost of Delay, WSJF, and practical Lean Portfolio Management to their own environment. 

Button: Talk with agilityIRL 

For the website, show results immediately and make email capture optional afterward. Use one question per screen with a progress indicator, or a short form with all eight questions. If several questions tie for the lowest score, let the visitor choose which two they want to explore.