TBM Framework
What is TBM Framework?
The TBM Framework is the TBM Council's model for running a Technology Business Management practice. It links foundations, the TBM Taxonomy, outcomes such as transparency and benchmarking, and the value they create.
Updated November 2026 · 5 min read
The TBM Framework is the overall structure the TBM Council uses to describe how Technology Business Management works in practice. Where the TBM Taxonomy defines how technology costs are classified, the framework describes everything around it: the data, tools and roles a TBM practice needs, the outcomes it should produce and the business value those outcomes support. It gives organizations a reference point for designing and maturing their own programs.
The framework has evolved since TBM was first defined more than a decade ago. The original version centered on a set of value conversations between IT and the business, while the current version is organized in layers that run from practical foundations to organizational value. Both versions share the same purpose: helping leaders manage technology as a business investment rather than as an opaque cost.
Definition of the TBM Framework
The TBM Framework is a model of the capabilities, standards and outcomes that make up a Technology Business Management practice. It is published by the TBM Council, the nonprofit organization formed in 2012 to define and promote TBM, and it sits alongside the TBM Taxonomy as one of the discipline's core reference materials.
The framework is descriptive rather than prescriptive. It does not dictate a single way to run TBM, but it names the elements a mature practice needs and shows how they relate. Organizations use it to assess where their program is strong, where it has gaps and what to build next.
The Current Framework
The current version of the framework is organized in four layers. Foundations covers the data, tools, methods, roles and change management a practice depends on. The TBM Model covers the TBM Taxonomy, its industry extensions and the connected standards it works alongside, such as frameworks for FinOps, IT service management and strategic portfolio management.
TBM Outcomes describes what a practice delivers: transparency, insights, benchmarking, strategy, alignment and optimization. Organizational Value Drivers describes why those outcomes matter, including financial performance, operational efficiency, innovation, risk and compliance, experience and sustainability. Reading the layers from bottom to top shows how practical work turns into business value.
The Original Framework and Value Conversations
The first version of the framework was introduced in the book Technology Business Management: The Four Value Conversations CIOs Must Have With Their Businesses. It described a set of layers, from positioning for value and creating transparency to planning, governing and continuously improving.
At its center were four value conversations. Two addressed running the business: cost for performance and a business-aligned portfolio. Two addressed changing the business: investment in innovation and enterprise agility. These conversations remain a useful way to frame discussions between technology and business leaders, even though the current framework is organized differently.
Importance of the TBM Framework in IT Financial Management
Many organizations start TBM by building a cost model and stop there. The framework is a reminder that a cost model is only one part of a working practice, and that its value depends on the foundations beneath it and the decisions built on top of it.
It also gives technology finance leaders a shared vocabulary for describing their program to executives, peers and partners, which helps when seeking investment in people, tools or data improvements. It complements the core processes of IT financial management (ITFM), such as budgeting and forecasting, by showing how they fit into a wider practice.
A Blueprint for Building a Practice
The framework shows what a complete TBM practice includes. A team that has a cost model but no clear roles, poor data or no process for acting on insights can see those gaps directly in the Foundations and Outcomes layers.
This makes the framework useful for planning. Organizations can map their current capabilities against each element, decide which gaps matter most and build a roadmap that improves the practice step by step rather than all at once.
Connecting Work to Value
The framework links everyday TBM work to outcomes executives care about. IT cost transparency and benchmarking are useful on their own, but the framework shows how they feed strategy, alignment and optimization, and through them financial performance and innovation.
This connection helps TBM teams explain their work. Instead of presenting a model or a report, they can show how their output supports specific business goals, such as reducing run costs to fund new initiatives or improving the efficiency of technology services.
How to Implement the TBM Framework
Organizations rarely implement the whole framework at once. Most use it as a guide, starting with the elements that matter most to their leaders and expanding as the practice matures.
The TBM Council also offers maturity and practice assessments that help organizations measure their progress against the framework and compare themselves with others.
Starting With Foundations and Transparency
A typical first phase focuses on foundations and transparency. The team gathers financial, asset and consumption data, chooses tools, assigns roles in a TBM office and builds an initial cost model using the taxonomy.
The first outcome is usually transparency: clear reports showing what technology costs by tower, solution and consumer. Delivering this early builds support for the program and reveals data issues that need attention before more advanced outcomes are possible.
Expanding to Insights and Optimization
Once transparency is established, the practice adds insights and benchmarking, such as unit costs, trends and comparisons with peers. These outcomes help leaders identify where spending is out of line or where efficiency can improve.
The most mature practices use the model to shape strategy and drive optimization, influencing annual planning, investment decisions and vendor negotiations. At this stage, TBM becomes part of how the organization manages technology rather than a separate reporting exercise.
Examples of the TBM Framework in IT Financial Management
The examples below show how organizations use the framework to guide their TBM programs.
Both are illustrative, but they reflect common ways the framework is applied in practice.
Assessing a Stalled Program
A healthcare organization has run a TBM cost model for two years, but executives rarely use its reports. Mapping the program against the framework shows strong work in the TBM Model layer but weak foundations: no dedicated roles, manual data collection and no process for turning reports into decisions.
The organization appoints a TBM lead, automates its main data feeds and adds a quarterly review with business leaders. Within a year, the cost model is being used in planning, and executives can point to decisions it influenced.
Linking TBM to Business Goals
A retailer wants to shift spending from maintaining legacy systems to digital initiatives. Using the framework, its TBM team ties the goal to the innovation and financial performance value drivers and designs reports that track run versus change spending each quarter.
The reports show which legacy applications account for the most run cost. Retiring several of them frees budget for digital projects, and the TBM team can show leadership exactly how much was redirected.
Conclusion
The TBM Framework describes the full structure of a Technology Business Management practice, from data, tools and roles to outcomes and the business value they support. It complements the TBM Taxonomy by showing what a practice needs beyond a cost model.
Used as a blueprint, the framework helps organizations assess their programs, plan improvements and connect their work to goals executives care about. Whether framed through the original value conversations or the current layered model, its purpose is the same: managing technology as a business investment.
Related terms
TBM Taxonomy
The TBM Taxonomy is the TBM Council's standard model for classifying technology costs. It organizes spending into cost pools, resource towers, solutions and consumers so costs can be compared and traced.
IT Financial Management (ITFM)
IT Financial Management (ITFM) is the discipline of planning, tracking and managing technology spending. It covers budgeting, forecasting, accounting, cost allocation and reporting for IT.
IT Cost Transparency
IT cost transparency is the ability to show clearly what technology costs, what it pays for and who consumes it. It turns IT spending from a single overhead line into an understandable picture.
Unit Cost
Unit cost is the total cost of producing or delivering one unit of a product or service. It equals total cost divided by units and is used to measure efficiency and set prices.