You know the storage unit. Maybe you pay that monthly charge right now. $200 a month to protect a couch, a pair of lamps, and a dinette set you swear you will will find the space for.
Three years pass.
Rent hits $7,200.
That furniture might get $900 from Craigslist, yet the unit has already cost you eight times that.
Cost to Carry
Organizations rent the same unit. They just call it a backlog. Whether it is refactoring or technical debt or product features or storage or depretiation,
Every half-built feature and every decision parked for next quarter sits on a shelf and charges rent while it waits. No invoice shows up, and no line on the balance sheet admits the expense, so most leaders never see the bill. Finance has a name for it anyway. Carrying Cost.
As Investopedia cites:
Carrying costs represent the financial burden of maintaining inventory, including expenses like storage, insurance, taxes, labor, and opportunity costs. By calculating these costs, businesses can evaluate profitability and adjust inventory levels strategically.
The Cost of Confusion series so far covers three expenses, with Cost of Delay on time, Switching Cost on divided attention, and Opportunity Cost on the wrong bet. This post adds a fourth expense nobody puts in a budget, the price to keep work you never finish.
The first post in this series named three cost Efficiency Three Stooges. ThoseThree Stooges, in actuality had six members over their run, so, introducing a fourth member here hardly breaks ruins the metaphor.
Carrying Cost plays the quiet one.Delay makes noise when a launch slips, and context switches make noise when a deadline gets blown, but carrying cost never makes a sound.
Carrying Cost sits in the corner avoiding eye contact and compounds.
Efficiency’s Three Stooges
1. Cost of Delay (CoD): The Price of Pace
CoD quantifies the financial impact of delays. Every day a project is late, value is lost—whether in revenue, cost savings, or competitive advantage.
- Why It Matters: If a high-value feature is delayed by three months, the lost revenue from that delay could outweigh the cost of building the feature itself.
- Where Confusion Makes It Worse: Unclear priorities and scope creep lead to teams working on the wrong things, pushing back high-value initiatives.
Solution: Use CoD to prioritize work based on economic impact, as provided by the product owner responsibility, and not just stakeholder pressure.
2. Switching Costs: The Tax to Switch Tasks
Every time a team shifts between projects, productivity drops due to the mental effort required to re-engage with a new task. These inefficiencies compound over time.
- Why It Matters: A team working on three projects simultaneously loses 20 to 40% of time due each context-switch. That estimated four-week project now takes five or six weeks.
- Where Confusion Makes It Worse: Lack of clear focus forces teams to juggle multiple priorities, increasing inefficiencies and delaying everything.
Solution: Reduce work in progress (WIP), revisit prioritization against change, and limit task-switching to improve delivery speed.
3. Opportunity Cost: The Price of Wrong
Opportunity cost is the value lost when teams focus on lower-impact work instead of high-value initiatives.
- Why It Matters: If a team spends three months on a low-impact project while delaying a product feature that could generate $1M in annual revenue, that delay costs far more than the intended projected revenue.
- Where Confusion Makes It Worse: Poor prioritization leads to teams that waste time on initiatives past their business value shelf date.
What Carrying Cost Measures
A manufacturer understands Carrying Cost because the bill sits on the warehouse suite. Every pallet of raw material or finished goods ties up capital, takes floor space, needs insurance, and loses value as it ages. Supply chain analysts typically put that bill at 20% to 30% of inventory value per year.
Knowledge work carries inventory too. You just cannot see it.
Look across your portfolio and you will find:
- Approved projects with no team assigned,
- Features built and tested, yet never released,
- Requirements written for a quarter already over,
- Pilots with proven value and no budget to scale,
- Decisions parked until the next governance board,
- Legacy systems scheduled for retirement “next year,” every year
Don Reinertsen makes this point in The Principles of Product Development Flow. Product development inventory lives in information instead of on a warehouse floor, so it stays invisible, physically and financially. Nobody trips over it, and nobody schedules a cleanup.
Where the Money Goes
Carrying Cost in knowledge work breaks into three buckets: capital, upkeep, and decay.
- Capital: Money spent on unfinished work earns zero return. A feature at 80% complete earns the same as a feature never started. Meanwhile, your finance team still expects a return on every dollar.
- Upkeep: Parked work still demands attention. Somebody updates the status report, grooms the backlog, renews the license, and pays the cloud bill for a test environment nobody has touched since March. Every time a parked item resurfaces, teams re-estimate it, stakeholders re-argue its priority, and a new hire asks why it exists. You pay for that same conversation every quarter.
- Decay: Unfinished work spoils. Code drifts from the main branch and merge conflicts pile up. Requirements age past market reality. The people who know the work leave and take the context with them. Factories call this shrinkage. Your teams call it “we need to start over.”
- Delay: Some work never starts at all. Approved projects and proven ideas wait behind run-the-business work, audits, fire drills, reorganizations, and the next urgent request from the executive floor. Nobody kills the work, so it stays on the roadmap, holds a slot in every quarterly plan, and keeps a promise open with the customer who asked for it. Each quarter it waits, the market moves and the payoff shrinks.
Cost of Delay prices that lost value. Carrying Cost adds the bill to keep the work alive in the meantime.
How the Bill Adds Up
Add the four and you have the bill: Carrying Cost = Capital + Upkeep + Decay + Delay
- Start with capital: Your portfolio holds 28 parked initiatives with $2 million of labor already spent. That $2 million earns zero while it sits on the shelf. Your finance team expects a 10% return on capital, so the shelf costs you $200,000 a year in return you never see.
- Then, upkeep: Each parked initiative still pulls about three hours a month from your people for status updates, priority debates, and stakeholder questions. At a blended rate of $120 an hour, those 28 initiatives cost you $120,960 a year to keep alive.
- Then decay: Requirements age, code drifts, and the people who know the work move on. If 10% of the shelved work needs rework for every year it sits, you pay another $200,000 a year to rebuild what you already bought.
- The delay is time and that never stops.
The total comes to about $521,000 a year, or $10,000 a week, for work no customer sees until you finish it. That bill equals 26% of the money already sunk, inside the 20% to 30% range supply chain analysts use for warehouse inventory. Your backlog costs as much to hold as a warehouse full of pallets. Every year the work sits, you pay the bill again.
Little’s Law makes volume worse. Little’s Law posits that lead time equals work in progress over throughput. If your team finishes four initiatives a quarter and holds 12 open, each initiative waits about three quarters. Double the open work to 24 and each initiative waits six quarters. The team works no slower, yet every initiative now pays twice the rent.
Carrying Cost and Cost of Delay are additive, both add time and time without value is waste.
Delay prices the revenue you lose because the work ships late. Carrying Cost prices the cash you spend to hold the work until it ships. A parked initiative charges you both.
Four Costs, by Side
| Cost | Question it answers | What it prices | Confusion symptom |
|---|---|---|---|
| Cost of Delay | What does a late release cost? | Value lost to time | Unplanned priorities shift resources |
| Switching Cost | What does divided attention cost? | Productivity lost per context switch | Teams juggle multiple priorities |
| Opportunity Cost | What does the wrong choice cost? | Value of the path not taken | Low-value work keeps its budget |
| Carrying Cost | What does the decision to keep cost? | Upkeep and decay of unfinished work | “Park it” over “kill it” |
One parked initiative can trigger all four costs at once. It delays value, pulls your people into context switches, blocks a better bet, and charges rent the whole time it sits.
Where Confusion Makes It Worse
1. Approval without Retirement
Issue: Governance boards approve new work with enthusiasm and retire old work with dread, so the portfolio only grows.
Fix: Attach a sunset date and kill criteria to every approval. Hold a quarterly portfolio review and require every parked item to earn its place or leave.
2. Large Batches
Issue: Big releases hold finished work hostage to unfinished work. A feature done in March waits for the June release and pays three months of rent for no reason.
Fix: Shrink the batch and release value as it completes. Smaller batches mean less inventory, shorter holds, and a smaller bill.
3. Parking Decisions
Issue: “Park it” feels free. Leaders use the phrase to avoid a hard no, and the shelf fills with polite indecision.
Fix: Price the shelf. Give every parked item an owner, a review date, and a monthly Carrying Cost estimate. Once “park it” carries a visible price, your leaders treat it like the decision it represents.
Beast of Burden
People carry inventory too, and theirs costs the most.
The Zeigarnik effect suggests unfinished tasks hold attention longer than finished ones. Every open loop on your roadmap also sits as an open loop in somebody’s head, and across a whole team that load becomes a cognitive tax you pay as you make choices elsewhere.
Morale carries a price as well. Your team watches its work sit on a shelf until relevance fades and the project quietly dies. After the third shelved project, people hold back discretionary effort, and you cannot blame them.
Disengagement never shows up in the formula, yet it hits the P&L through turnover, slower delivery, and lost trust, and the leaders who wonder why their best people no longer raise their hands for new initiatives rarely trace the cause back to the shelf.
Leaders with strong emotional intelligence catch this signal early, because to the team that built it, unfinished work feels like a broken promise.
Four steps to put Carrying Cost in the open:
- Count the inventory. List every approved, active, parked, and half-built item. Include the legacy systems everyone “plans to retire.”
- Price the carry. Estimate labor invested to date, apply your cost of capital, add monthly upkeep hours, and estimate rework.
- Publish the bill. Report Carrying Cost next to Cost of Delay in your monthly portfolio review. A number on a slide beats an opinion in a hallway.
- Cost of delay. Revisit this as the cost of avoidance when you choose not to improve something.
- Finish or kill. Finish more and start less. If a piece of work looks too weak to finish and too political to kill, you have a decision-rights problem, and that problem costs more than the work.
Carrying Cost and the Cost of Confusion
Confusion creates inventory. Unclear priorities approve too much work, unclear ownership kills too little, and unclear strategy parks the rest. Every item on that pile charges rent, loses value, and drains the people asked to remember why it exists.
Clarity works like a warehouse audit. Once you see the full inventory, you make better calls about what to finish, what to fund, and what to let go.
The storage unit never thanks you for the rent. Neither does your backlog.
Up next: CD3, Cost of Delay Divided by Duration, and how to rank work with less politics and more proof.
Put This to Work
Ready to see the Carrying Cost bill for your own portfolio? Book a 90-minute Clarity Session through Work with Toby, and leave with a priced inventory and a one-page plan for what to finish, fund, or kill.
Prefer to start on your own? Get the Impact Assessment template and map what each parked initiative touches.
To get the next post in the Cost of Confusion series, subscribe for the weekly round-up.