Why IT cost transparency projects stall

In brief

Many IT cost transparency projects don't fail outright. They publish a model and little changes. Why that happens, and how to restart around one decision.

Steve Elliott

Steve Elliott · · 4 min read


On this page
  1. What happened with federal TBM?
  2. A second reading of the federal case
  3. A test you can run this week
  4. Three patterns we see in stalled programs
  5. How to restart a stalled program
  6. Sources

Many IT cost transparency projects don't fail outright. They build a cost model, publish the reports, and then little changes. Sponsorship and data quality tend to get the blame. In our view the more common cause is that no budget, portfolio or sourcing decision was set up to use the numbers, so transparency becomes the goal rather than the means.

A well-documented public example is the US federal government's TBM effort, which GAO reviewed in 2025. GAO's diagnosis is different from ours, and both are worth reading.

What happened with federal TBM?

In August 2017, the Office of Management and Budget (OMB) announced it would improve insight into IT spending by having agencies adopt TBM. GAO's July 2025 report on 26 agencies found the effort stalled:

  • 15 of the 26 agencies had no plan for implementing TBM.
  • 18 had only partly implemented, or not implemented, a reliable cost allocation methodology.
  • Twelve agencies reported total implementation costs for all or part of fiscal years 2017 to 2023, ranging from about $1.5 million to $28.9 million each, or about $91 million combined by our count.
  • Of the 20 agencies that described benefits, most cited more transparency into IT spending. Many cited more consistent budget formulation, and some cited the ability to analyze IT spending data for decision making.
  • None of the agencies provided cost savings estimates, and 19 said they had not yet achieved any savings.

GAO's conclusion is that OMB's "lack of action and guidance over the last 8 years has led to substantial TBM delays." OMB had required only part of the taxonomy, and without fuller guidance most agencies hadn't built plans. GAO recommended that OMB either end the government-wide effort, with agencies spending nothing more on it, or make TBM an administration priority and track its costs and benefits. OMB neither agreed nor disagreed.

A second reading of the federal case

GAO's diagnosis is missing guidance. We'd add a second reading.

Nine agencies said they had not fully developed their own plans because they were following OMB's high-level time frames. Many that hadn't implemented the remaining taxonomy said they would wait for OMB to require it, citing the cost, competing priorities and a wish to improve the data already required. Those are reasonable choices. But they suggest programs organized around a reporting requirement. Some agencies said they could now analyze their spending, yet none provided a savings estimate.

Our reading: when a transparency program is built to satisfy a requirement rather than to feed a specific decision, it can produce real visibility and still change little. Private companies don't have an OMB. In our work with IT finance teams, we see the same shape when a program is organized around a report, a taxonomy or a software rollout, with the decisions left for later.

A test you can run this week

List the decisions your cost model informed last quarter. Not reports produced, decisions made: a renewal renegotiated, a service retired, a budget moved, a project stopped.

If the list is short, data quality probably isn't the main problem. The model isn't wired to the choices it was meant to inform.

Three patterns we see in stalled programs

These are our observations, not survey findings.

  1. The model is built for completeness before it answers a question. Teams try to map every general ledger line to every tower before anyone has asked something the model can answer.
  2. Reports land after the decision. If cost reports arrive after budgets are set and renewals are signed, they explain the past instead of shaping the next choice.
  3. No one on the business side owns consumption. A bill of IT is only useful if someone who can change demand reads it. Without a named business owner for each major service, showback goes to an inbox.

Allocation quality matters too. The TBM Council lists weak cost drivers and over-reliance on flat splits among the most frequent causes of unmapped or low-quality data. In our experience, business leaders are quick to dispute numbers built on drivers that don't reflect consumption, such as storage split by headcount rather than gigabytes used.

How to restart a stalled program

Work backward from one decision instead of forward from the taxonomy.

  1. Pick one decision with a date. Next year's run budget, a major software renewal or a data center exit are good candidates because they have deadlines and owners.
  2. Build the minimum model that decision needs. That might be cost pools and a few towers for one domain, not the whole estate.
  3. Make unmapped cost visible instead of hiding it. The TBM Council suggests measuring mapped spend as a share of total spend at each layer, and setting a threshold, such as keeping unmapped cost-pool spend under 1%, that triggers review.
  4. Put the numbers in front of the decision owner before the decision. In our view, timing matters more than precision.
  5. Expand only when another decision needs it. Each new domain should arrive with its own decision attached.

This is what an operating model is for: the cost of the work should sit next to the plan and the funding decision it informs, so the numbers are in the room when the choice is made rather than in a report afterward.

Sources

Frequently asked questions

Why do TBM programs fail?

Weak executive sponsorship and poor data quality tend to get the blame, and both matter. In our view the more common underlying cause is that no budget, portfolio or sourcing decision was set up to use the numbers, so the program produces reports without changing what the organization does.

What is fallout in a TBM model?

Fallout is cost that can't be fully mapped through the model and lands in buckets such as "Unmapped," "Unassigned" or "Other." The TBM Council says it isn't a symptom of low maturity, since every organization has some. It recommends measuring mapped spend at each layer, detecting fallout monthly and revalidating mappings quarterly.

Did federal TBM save money?

Not that agencies could show. In GAO's 2025 review of 26 agencies, those describing benefits cited transparency, more consistent budgeting and better analysis of IT spending. None provided cost savings estimates, and 19 said they had not yet achieved savings. GAO attributed the stall mainly to missing guidance from OMB.

How do you restart a stalled cost transparency program?

Work backward from one decision with a date and an owner, such as next year's run budget or a major renewal. Build only the model that decision needs, make unmapped cost visible, deliver the numbers before the decision is made, and expand to new areas only when another decision needs them.

Free playbooks

In-depth guides for product and operations leaders.

Browse the playbooks
Steve Elliott

Steve Elliott

Published November 22, 2026

More on TBM & IT Financial Management

Cost pools, towers, showback, unit cost.