How business relationship managers should use TBM data

In brief

BRMs sit closest to business demand, so they should do more than receive TBM reports. How BRMs can use the bill of IT, intake and value reviews instead.

Steve Elliott

Steve Elliott · · 7 min read


On this page
  1. Why do BRMs matter to a TBM program?
  2. What does TBM Council research say about BRMs?
  3. How should a BRM use the bill of IT?
  4. How do BRMs use TBM data to shape demand and intake?
  5. What does a value realization review look like with TBM data?
  6. What do BRMs and the TBM office need from each other?
  7. Sources

Business relationship managers should use TBM data to shape demand before it turns into cost: in showback conversations, at portfolio intake and in value realization reviews. In return, they should give the TBM office what it can't get from the general ledger, which is how each business unit consumes technology and how that consumption will change.

In our view, most TBM programs don't set the role up that way. Where BRMs are involved at all, they tend to receive the bill of IT like any other business-facing role. We think that wastes the one role in IT whose job description is already about demand.

Why do BRMs matter to a TBM program?

Because the two disciplines describe the same handoff from opposite ends.

The BRM Institute defines the BRM role as the strategic interface between a business function and its business partners, there to "stimulate, surface, and shape business demand" for the function's assets and capabilities. A 2014 BRM Institute article adds the other half: making sure the potential business value is "defined, realized, optimized, and recognized." For IT BRMs, it says they facilitate value realization with the finance BRM, the business, a value management office and/or business analysts. The Institute's current competency model groups the work under four headings: evolve culture, build partnerships, drive value and satisfy purpose.

The TBM Taxonomy has a layer for the same people. In version 5.0 the Business layer was renamed the Consumer layer. Version 5.0.1, the current release, deliberately keeps it lean, with categories such as business functions, value streams, partners and external consumers, so organizations can build their own consumer hierarchies. The TBM Council says the layer exists to "make IT spend visible to the people and functions that fund it," so that costs can be shown or charged back to them. Its guide for TBM practice leads goes further: connecting solutions to the people who consume them gives business leaders the context to shape demand.

In our view, the taxonomy's top layer is the BRM's patch. We think the person who already holds those relationships should help build and use that layer, not just read it.

What does TBM Council research say about BRMs?

Two TBM Council surveys mention the role. Read together, they suggest reporting to BRMs goes with maturity, while treating BRMs as recipients of TBM reporting.

The 2021 State of TBM Report. The Council's first State of TBM survey, with 103 complete responses, asked which roles the TBM office provides reporting to. It described BRMs as those "who wield the catalog or portfolio" when working with business unit leaders on spending and investments. The share of respondents reporting that the role exists and receives TBM reporting rose from 24% in early-stage programs (Crawl) to 34% at Walk and 71% at the combined Run/Fly stage. By our count, that 47-point spread is the widest of the nine roles in the table. The report says the more roles receive TBM reporting, the greater the effect on maturity, or conversely, that more mature programs report to more roles.

The 2022 State of TBM Report. With 563 complete responses, the Council asked how good the reporting is that TBM provides to nine roles. For BRMs, 54% rated it in the top two categories (good or excellent), fifth of nine, just behind IT procurement (55%). IT financial managers ranked highest at 62%.

Two caveats. These are self-reported surveys, and the 2021 sample is small: the Run/Fly group was small enough that the report combined two stages, so the 71% rests on few respondents. The link between BRM reporting and maturity is a correlation, not proof that one causes the other. And both surveys frame the BRM as someone who receives reporting.

The Council's current TBM Roles page lists six core roles for a TBM team: executive sponsor, practice lead, solution owner, change manager, administrator and analyst. The BRM is not among them. That's a fair choice for defining a TBM team. But in our view it explains why BRMs often end up on the distribution list rather than in the room.

How should a BRM use the bill of IT?

As the agenda for a conversation about demand, not as an invoice to explain.

A bill of IT shows a business unit the technology it consumed and what that cost. Whether it is showback or chargeback, it only changes behavior if someone who can change demand reads it with someone who can explain the drivers. The BRM is the natural person to do both. This is our view of how that conversation works best:

  1. Start with volume, not price. Most of what a business unit can change is how much it uses. Rates are usually set by IT and finance.
  2. Name the cost drivers. The TBM Council's guidance on allocation says cost drivers should reflect actual consumption, value delivered or an equitable split, and that involving business unit representatives in reviews helps validate fairness. A BRM can bring that review to the business leader instead of waiting for a dispute.
  3. Separate what the unit controls from what it doesn't. Shared infrastructure allocated on a fixed split is not something a business leader can act on this quarter. Say so.
  4. Leave with a decision or a question. Retire an application, change a service tier, or ask the TBM office to check a driver. If the meeting ends with neither, the bill was a report.

How do BRMs use TBM data to shape demand and intake?

Demand shaping is where the BRM definition and TBM data meet most directly. We think three uses matter most.

  • Before intake. When a business unit raises a new request, the BRM can show what similar solutions already cost to run, from the Solutions and Consumer layers. That makes the run cost of a new idea visible while it is still an idea.
  • In the investment case. A BRM who writes or sponsors the case can use total cost of ownership from the TBM model, including staffing and shared services, rather than a project budget alone. Portfolio boards can then compare requests on the same basis.
  • When demand shifts. If a business unit plans to grow, shrink, merge or change channels, the BRM often hears first. Passing that to the TBM office early is the most useful thing a BRM can do for the forecast.

An illustrative case shows why the last point matters. Suppose a business unit plans to double its customer service headcount next year. If the bill of IT allocates contact center software by seat, its allocated cost roughly doubles too, assuming the per-seat rate holds. The TBM office will see that only when the seats appear, unless the BRM tells it first.

What does a value realization review look like with TBM data?

It compares what an investment was expected to cost and deliver with what it actually costs to run and what the business says it got.

The BRM Institute puts value realization inside the BRM's remit, shared with the finance BRM, the business and a value management office. TBM supplies the cost side. In our view a useful review has three parts, and the BRM chairs it:

  • Cost to run, from the TBM model. The solution's ongoing cost as it now flows to the consuming business unit, set against the run cost assumed in the investment case.
  • Benefit, from the business. The measures the business unit agreed to in the case, reported by the business, not by IT.
  • A decision. Keep, expand, fix or retire.

The TBM data makes the first part repeatable. Without it, we think run cost in value reviews tends to be an estimate nobody can trace.

What do BRMs and the TBM office need from each other?

This split is our view, not a published standard.

The BRM needs from the TBM officeThe TBM office needs from the BRM
A bill of IT per business unit, in business terms, before budget and renewal decisionsConsumption drivers the business recognizes and will accept
Clear notes on which costs the unit controls and which are fixed allocationsDemand forecasts: planned growth, new products, exits and reorganizations
Run cost and total cost of ownership for solutions, for intake and investment casesValidation of Consumer-layer mappings: which units, products and value streams use what
A named analyst to explain drivers and handle disputesEarly warning when a business leader disputes an allocation
Run cost data for value realization reviewsAgreed benefit measures to set against cost

We think the right-hand column is the part TBM programs most often skip. A cost model can be built from the ledger. The Consumer layer can't be built well without the people who know how the business consumes. As we argued in why IT cost transparency projects stall, a bill of IT is only useful if someone who can change demand reads it.

A practical starting point, in our view: invite BRMs to the TBM office's driver review before the next budget cycle, and give each one the bill of IT for their business units a month before it goes to the business leader.

This is where an operating model earns its keep: demand, funding and cost should sit in one place, so the BRM and the TBM office are looking at the same numbers when a business leader asks for more.

Sources

Frequently asked questions

What does a business relationship manager do in TBM?

In our view, a BRM should use TBM data to shape demand: explaining the bill of IT to business leaders, bringing run cost into intake and investment cases, and chairing value realization reviews. In return, the BRM gives the TBM office consumption drivers, demand forecasts and validation of which business units, products and value streams use which solutions.

Is the business relationship manager a TBM Council role?

Not a core one. The TBM Council's TBM Roles page lists executive sponsor, practice lead, solution owner, change manager, administrator and analyst. The Council's State of TBM surveys do include BRMs among the roles that receive TBM reporting, and its 2021 report found reporting to BRMs far more common in self-reported mature programs.

How does the TBM Consumer layer relate to BRMs?

The Consumer layer, renamed from the Business layer in TBM Taxonomy 5.0, identifies who consumes technology solutions: in 5.0.1, business functions, value streams, partners and external consumers, as a lean baseline organizations extend. The TBM Council says it exists to make spend visible to those who fund it. Those consumers are the business partners a BRM already works with.

Should BRMs own showback?

We think the TBM office should own the bill of IT and its allocation policy, while BRMs own the conversation with the business about it. The BRM brings the bill to business leaders, explains what they control, raises disputes over drivers, and feeds changes in demand back to the TBM office before the next forecast.

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.