The first two articles in this series established why cost centre thinking is the root cause of IT performance problems and what designing IT as an internal service provider looks like in operational terms. This third article addresses the measurement framework that proves the transformation is working, and without which the transformation cannot sustain executive sponsorship or investment.<\/p>\n
The measurement challenge for IT operating model transformation is specific. The cost centre model’s metrics are well understood: budget adherence, project delivery against plan, operational availability, ticket resolution times. These metrics are clear, objective, and easily defensible to finance audiences. They are also the metrics that measure the wrong thing.<\/p>\n
The value engine model’s metrics measure business outcomes. Business outcome metrics are more meaningful and harder to dispute when the outcomes are positive. They are also more complex to define, more difficult to attribute to IT, and more vulnerable to the objection that IT’s contribution cannot be isolated from other factors. Building a metrics architecture that is both business-outcome-oriented and defensible to finance requires deliberate design.<\/p>\n
The business outcome metrics that replace traditional IT operational metrics fall into four categories, each corresponding to a different dimension of IT’s business value contribution.<\/p>\n
Revenue enablement metrics measure IT’s contribution to the revenue that digital channels, digital products, and technology-enabled services generate. For organisations where digital revenue is material, the platform’s availability, performance, and release velocity directly affect revenue outcomes. The metric is not application uptime. It is the revenue at risk from application degradation, compared to the revenue achieved, with IT’s platform investment as the differentiating factor.<\/p>\n
Risk reduction metrics measure IT’s contribution to the reduction of business risk: security incidents that did not occur, compliance violations that were prevented, operational resilience that was demonstrated in crisis conditions. These metrics require the probability-weighted cost framework described in earlier articles to be expressed in financial terms, but the methodology exists and the estimates are defensible with explicit assumptions.<\/p>\n
Operational efficiency metrics measure IT’s contribution to the reduction of operational cost in the business functions that IT serves. The finance team’s processing overhead, the supply chain team’s inventory management cost, the customer service team’s handling time: each of these has a technology component that IT investment affects. Tracking the efficiency metrics of IT’s business unit customers and attributing the improvement to IT investments creates a direct line between IT’s work and the business unit’s performance.<\/p>\n
Delivery velocity metrics measure the speed at which IT delivers the capabilities that business units request: time from approved investment to deployed capability. This metric is not a surrogate for business value. It is the measure of IT’s ability to convert business investment into business capability at the pace the business strategy requires.<\/p>\n
The metrics above tell the story of IT’s business value contribution. The financial transparency model makes that story credible to the CFO and the board.<\/p>\n
Financial transparency requires that IT reports its investment portfolio with the same level of detail and discipline that any other significant business investment portfolio receives. Each material technology investment should have: a documented business case with expected return, a timeline for return realisation, a measurement mechanism for tracking actual return against expected, and a regular reporting cadence that surfaces the comparison.<\/p>\n
Technology investments that are delivering expected returns are presented as evidence of the investment thesis. Those that are not are presented with an honest assessment of the gap and a plan to close it or, if the investment is not recoverable, a proposal to reallocate it. This portfolio management approach treats technology investment as a financial discipline, not as a cost to be managed.<\/p>\n
The CFO who receives this reporting is not being asked to trust IT’s judgment about technology. They are reviewing financial performance data about a portfolio of investments in their organisation’s technology capabilities. That is a conversation that CFOs are equipped to participate in, and the IT leaders who bring them this data are having a different quality of conversation than those who bring them cost variance reports.<\/p>\n
The board-level metrics for IT governance are a subset of the financial transparency model, filtered for the risk and strategic dimensions that board governance requires.<\/p>\n
Technology investment concentration risk: what proportion of the technology investment portfolio is concentrated in single vendors, single platforms, or single capability areas, and what is the organisational exposure if those concentrations become problematic? This metric connects to the strategic governance questions that boards should be asking about technology vendor dependency.<\/p>\n
Regulatory compliance status: what is the current compliance posture across the regulatory requirements that apply to the organisation’s technology operations, and where are the gaps that require board-level attention? NIS2, DORA, AI Act, and GDPR obligations all have technology components; the board’s oversight responsibility requires visibility into compliance status.<\/p>\n
Technology debt exposure: what is the current quantified technology debt across the organisation’s technology estate, and what is the remediation investment required to bring it to an acceptable level? Technology debt is a balance sheet risk that boards should have visibility into, expressed in financial terms as the cost of the remediation deferred, not as a technical description of the systems involved.<\/p>\n
AI governance status: for AI systems that carry regulatory or reputational risk, what is the current governance posture, what are the oversight mechanisms in place, and where are the gaps? As AI deployment scales, the board governance function for AI systems requires the same measurement visibility as other strategic risk areas.<\/p>\n
The metrics above are only as valuable as the credibility of the data behind them. Business outcome metrics that are constructed rather than measured destroy the trust they are meant to build.<\/p>\n
The measurement programme that makes these metrics credible has two requirements. The first is independence: the metrics should be measured by a system that IT does not control, or audited by someone outside the IT function. Business outcome metrics that IT reports on its own behalf are vulnerable to the accusation that they reflect IT’s interpretation rather than the business’s experience.<\/p>\n
The second requirement is consistency: the metrics should be reported on a defined cadence, with historical comparison, so that trends are visible rather than only point-in-time snapshots. A single data point is anecdote. A consistent trend is evidence.<\/p>\n
The metrics architecture that meets both requirements uses business intelligence infrastructure and reporting processes that are shared across the organisation, with IT’s metrics reported in the same format and through the same channels as other business unit performance metrics. This positions IT as a business unit measuring its performance against business outcomes, not as a technology function reporting on its own activities.<\/p>\n
The three articles in this series have together made a single argument: IT operating model transformation from cost centre to value engine is a governance change before it is a management change, a measurement change before it is a technology change, and a sustained leadership commitment before it is a programme.<\/p>\n
The metrics framework in this third article is the completion of that argument. Cost centre IT is measured on costs. Value engine IT is measured on business outcomes. The transition between them is visible in the measurement framework, which is why getting the measurement right is not the final step of the transformation but the proving ground on which its success is determined.<\/p>\n
An IT function with the right governance, the right operating model design, and the right metrics framework is ready to have a fundamentally different conversation with its board, its CFO, and its business unit partners. That conversation is the goal. The metrics make it possible.<\/p>\n","protected":false},"excerpt":{"rendered":"
The operating model redesign succeeds or fails on the strength of its measurement framework. IT organisations that have made the transition from cost centre to value engine need metrics that demonstrate business impact, not operational efficiency.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[],"class_list":["post-125","post","type-post","status-publish","format-standard","hentry","category-operating-models"],"_links":{"self":[{"href":"https:\/\/baecke.io\/index.php?rest_route=\/wp\/v2\/posts\/125","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/baecke.io\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/baecke.io\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/baecke.io\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/baecke.io\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=125"}],"version-history":[{"count":0,"href":"https:\/\/baecke.io\/index.php?rest_route=\/wp\/v2\/posts\/125\/revisions"}],"wp:attachment":[{"href":"https:\/\/baecke.io\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=125"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/baecke.io\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=125"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/baecke.io\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=125"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}