Cost of Delay
Table of Contents
Delay has a price - sometimes imperfect ship now beats perfect ship after the window closes.
Key Concept
- Cost of delay is what you lose by waiting - revenue, trust, compliance date, or competitive window.
- Minimum Viable Product and There Is No Perfect Solution pair with this when polish blocks a useful now.
- Not every delay is evil - Decision Quality still applies when the ship would create irreversible harm.
Level 1 - Recognize
Cost of delay is the price of waiting - lost revenue, trust, or window while you polish.
Level 2 - Explain
Like holding the rescue boat for perfect weather while the tide rises - sometimes go with good enough now.
Level 3 - Use
Before another refinement sprint, name what waiting a week costs in money, users, or legal exposure.
Level 4 - Connect
Iron Triangle makes the time leg visible; Say No to Protect the Yes stops delay from scope that should have been cut.
Level 5 - Create
Sketch a simple delay cost for the initiative - even a range beats arguing taste in the abstract.
Examples
- Glad we shipped enrollment with manual CSV - waiting for the perfect integration missed the semester start.
- The client lost a campaign week while we tuned animation - cost of delay made the MVP call obvious in retro.
Note Relationships
| Relationship | Wikilink | Reason |
|---|---|---|
| extends | PM Mindset | Time trade inside the hub |
| extends | Iron Triangle | Time leg of constraints |
| extends | Minimum Viable Product | MVP when delay costs more than polish |
| contradicts | Attention to Detail | when polish prevents costly irreversible ship |





