Value Signal Diagnostic

Do you know what
your IT investment
is actually worth?

Request a Diagnostic → See a diagnostic in action ↓
The problem

Technology spend keeps rising.
Demonstrable return does not.

The gap between IT investment and measurable business value is the most expensive problem most organisations are not solving. It is not a technology problem. It is a measurement problem.

See the answer ↓
The answer

The Value Signal
Diagnostic.

01
Value leakage, quantified.
Every dollar leaving without return, identified and sized.
02
Recovery opportunities, mapped.
Technology already in place, unmapped to business outcomes.
03
A roadmap to act on.
Prioritised by impact. Delivered in five weeks. Yours to keep.
Request a Diagnostic → See a diagnostic in action ↓
The diagnostic in action

Is this your situation?
See what it uncovers.

How it works

Five weeks. Fixed scope.

01

Commission

Week 0

One call. Pack issued. You sign and return. Done.

02

Analyse

Weeks 1 to 4

We do the work. A few short interviews. Less than a day of your team's time.

03

Deliver

Week 5

Live workshop. Full findings. Everything handed over. No ongoing dependency.

One question.
One engagement.
One answer.

Start the conversation →
VS
Illustrative Scenarios

What the diagnostic
finds in practice.

$520K
Recoverable Value
Illustrative Scenario 01
Professional Services · 180 staff
The Situation
A mid-size advisory firm grown through acquisition. IT costs rising. The CFO had no defensible line between what was being spent and what it was returning.
The Result
$520K in recoverable value identified. Board-ready roadmap delivered at week five. No ongoing dependency.
Every figure supported by documented evidence, stated assumptions, and an explicit methodology structured to withstand scrutiny from a board, an investor, or a buyer.
$520K identified → board-ready roadmap at week five
$680K
Recoverable Value
Illustrative Scenario 02
Private Equity · Pre-exit portfolio company
The Situation
A PE firm preparing a portfolio company for exit. The technology estate had never been independently assessed. The deal team needed a quantified value position before the information memorandum opened. Not a risk register. A number.
The Result
$680K in recoverable value documented across the estate. Findings structured as an EBITDA improvement pathway ready for the information memorandum and buyer due diligence.
Every figure supported by documented evidence, stated assumptions, and an explicit methodology structured to withstand scrutiny from a board, an investor, or a buyer.
$680K identified → EBITDA pathway ready for the IM
Every technology estate has a number in it.
The diagnostic produces it.
Find your number →
From the practice

Why most technology investment
fails to return what it should.

Most organisations know their technology investment is underperforming. Few understand why, or that the gap is measurable, recoverable, and financally expressible. These pieces explain both.

From the Practice
20266 min read
Who This Work Is For
The Value Signal Diagnostic is commissioned by five distinct roles, each with a different problem and a different need. Private equity and M&A advisors need a number before a process opens. Boards need a return figure independent of the technology team. CFOs need recoverable margin without new capital. CTOs need a credible figure they can present without qualification. This piece sets out what each role gets.
Read→
The Value Gap — A Three-Part Primer
Part One
The Value Gap: Why the Returns Never Arrived
8 min read →
Part Two
Why Measuring More Does Not Solve It
7 min read →
Part Three
A Different Instrument for a Structural Problem
9 min read →
Part One of Three
20268 min read

The Value Gap: Why the Returns Never Arrived

Global IT expenditure has crossed $5 trillion. And yet 56 percent of CEOs report they are not seeing financial returns. The problem is not the technology. It is the failure to treat technology investment as a financial discipline.

Organisations are spending more on technology than at any point in history. And yet a quiet unease has settled into the C-suite. The systems are live. The projects are closed. And the financial returns that justified the investment have largely not arrived.

📉
56%
of CEOs reported their organisations were not yet seeing financial returns from technology investments. PwC, 28th Annual Global CEO Survey, 2025.

McKinsey estimates that 70 percent of digital transformation initiatives fail to meet their stated objectives. Bloch, Blumberg, and Laartz, analysing more than 5,400 large IT projects, found that the average project delivers 56 percent less value than predicted. These are not outliers. They are the average.

The problem is not technology adoption. It is the failure to treat technology investment as a financial discipline. We call the resulting shortfall the Value Gap: the cumulative, portfolio-level difference between projected and realised financial returns.

The research

The Technology Was Never the Problem

When a technology investment underperforms, the instinct is to interrogate the technology. Three decades of research point consistently elsewhere.

Schweikl and Obermaier, reviewing 86 firm-level studies, found that mismanagement remains the most neglected explanation for IT underperformance. Brynjolfsson and Hitt demonstrated that variance in IT returns across firms is driven primarily by organisational factors, not technology differences.

Two organisations can deploy identical systems and produce materially different financial outcomes. The technology is not the variable that explains the difference.

The mechanism, as Soh and Markus identified, is sequential: technology must convert expenditure into functional assets, assets into operational impact, and operational impact into financial performance. Failure at any stage interrupts the value chain. The project succeeds. The value does not arrive.

The four patterns

The Patterns Are Repeatable. The Leakage Is Live.

What makes the Value Gap so persistent is that it is not a historical problem waiting to be resolved. It is a set of structural patterns that repeat with every investment cycle.

01
Unattributed spend accumulates with every cycle
Each new investment adds licences, subscriptions, and shadow tools that governance never catches. Gartner estimates 10 to 30 percent of technology expenditure delivers no confirmed outcome.
02
Every approval repeats the same validation gap
47 percent of executives acknowledged overstating projected benefits to secure investment approval. That incentive structure has not changed. Ward, Taylor & Bond.
03
Every go-live creates a new realisation gap
Process changes are deferred, adoption falls short, benefit tracking is never instrumented, the accountable owner moves on. The assets are already paid for. The value has not been claimed.
04
Every renewal renews the pricing asymmetry
Without independent benchmarks, each renewal is a conversation conducted on the vendor's terms. The cost premium resets upward with each cycle.
💰
44¢
returned for every dollar of IT benefit expected. The remaining 56 cents is the Value Gap. Bloch, Blumberg & Laartz (2012), analysing 5,400+ large IT projects.

Understanding why these patterns persist, despite years of executive attention and governance investment, requires looking at a problem that sits beneath all four of them. That is the subject of part two.

Part One: The Value Gap Part Two: Why Measuring More Does Not Solve It → Part Three: A Different Instrument →
Warren Gabryk
Ph.D. · Founder and Principal · Axiom Value Partners · Sydney, Australia
View LinkedIn →

References

Bloch, M., Blumberg, S., & Laartz, J. (2012). Delivering large-scale IT projects on time, on budget, and on value. McKinsey Quarterly.

Brynjolfsson, E., & Hitt, L.M. (1998). Beyond the productivity paradox. Communications of the ACM, 41(8), 49–55.

Gartner (2024). Gartner forecasts worldwide IT spending.

McKinsey & Company (2018). Unlocking success in digital transformations.

PwC (2025). 28th Annual Global CEO Survey.

Schweikl, S., & Obermaier, R. (2020). Lessons from three decades of IT productivity research. Management Review Quarterly, 70(4), 461–507.

Soh, C., & Markus, M.L. (1995). How IT creates business value: A process theory synthesis. ICIS Proceedings.

Ward, J., Taylor, P., & Bond, P. (1996). Evaluation and realization of IS/IT benefits. European Journal of Information Systems, 4(4), 214–225.

Part Two of Three
20267 min read

Why Measuring More Does Not Solve It

Most organisations have more data about their technology estate than they know what to do with. They can tell you what every system costs. They cannot tell you what the estate is actually returning.

We established in part one that the Value Gap is not an occasional failure. It is a structural pattern that repeats with every investment cycle. The natural response is to measure more carefully. Track adoption. Instrument benefit realisation. Build better dashboards. And yet the gap persists.

The reason is not a lack of measurement effort. It is a fundamental mismatch between what most organisations measure and what actually determines whether technology investment creates financial value.

The core problem

Delivery Is Not Value

Organisations commit capital on projected value and close the budget cycle once the system is live, treating delivery as a proxy for value realised. Kohli and Grover identified this as the primary unresolved problem in the field: the near-universal absence of infrastructure to verify whether the value an investment was designed to produce has actually materialised.

The consequence is self-perpetuating. Each new investment decision is made on a foundation the organisation cannot see. Business cases are built on assumptions never tested against prior outcomes. The same failure modes repeat. The gap compounds.

Why measurement fails

The Mechanism Is What Matters

What most diagnostic approaches miss is that technology creates value through distinct causal mechanisms, and the mechanism matters. A system that enables a new capability creates value differently from one that automates a manual process, which is different again from one that reduces risk exposure or governs behaviour. Measuring adoption, or even usage, tells you nothing about whether the mechanism is actually operating.

⚠️
70%
of digital transformation initiatives fail to meet their stated objectives. Not because the technology failed, but because the value mechanism was never verified. McKinsey & Company (2018).

A CRM system may be fully adopted and still not drive the revenue growth it was designed to produce, because the sales process it was supposed to change has not changed. Programme reporting shows green. Financial performance disappoints.

The structural gap

Data-Rich, Evidence-Poor

The absence of value measurement is not a data problem. Most organisations have more data about their technology estate than they know what to do with. It is a structural problem: the data collected is not connected to the questions that matter.

Most organisations are data-rich and evidence-poor. They can tell you what every system costs. They cannot tell you what it is returning.

Schweikl and Obermaier, synthesising three decades of IT productivity research, found that inadequate returns are attributable not to the technology itself but to the system of organisational conditions that must accompany it. The vocabulary changes with each technology cycle. The failure mode does not.

Knowing that the measurement problem is structural is the precondition for solving it. Solving it requires a diagnostic framework built around the right questions. That is the subject of part three.

← Part One Part Two: Why Measuring More Does Not Solve It Part Three →
Warren Gabryk
Ph.D. · Founder and Principal · Axiom Value Partners · Sydney, Australia
View LinkedIn →

References

Kohli, R., & Grover, V. (2008). Business value of IT. Journal of the Association for Information Systems, 9(1), 23–39.

McKinsey & Company (2018). Unlocking success in digital transformations.

Schweikl, S., & Obermaier, R. (2023). Lost in translation: IT business value research and resource complementarity. Management Review Quarterly, 73(4), 1713–1749.

Part Three of Three
20269 min read

A Different Instrument for a Structural Problem

Conventional measurement asks what was built and what was adopted. The right question is different: through what mechanism is this technology supposed to create financial value, and is that mechanism actually operating?

This is the third in a three-part series. Part one and part two are worth reading first.

The first two pieces established the problem and why conventional measurement cannot solve it. The right question is not what was built. It is what mechanism was supposed to operate, and whether it is. Answering that for an entire technology portfolio, in terms defensible to a board, requires a diagnostic built specifically for it.

The framework

Tracing the Mechanism, Not Just the Deployment

Most diagnostic approaches stop at deployment. The Value Signal Map asks a different question for each asset: through what mechanism is this technology supposed to create financial value, and is that mechanism actually operating?

Technology creates value in fundamentally different ways. Some systems enable new capabilities. Others automate labour, reduce friction, govern behaviour, or preserve institutional knowledge. Each mechanism fails differently. Treating them as equivalent is precisely why so much value goes unrecovered.

Three urgent contexts

When the Analysis Becomes Urgent

Three contexts make this analysis urgent rather than merely useful.

🏦
Pre-exit
The Value Gap is a valuation problem before it is an operational one. Recoverable value identified before the process opens is directly multiple-able at exit. The diagnostic answers what a buyer will ask. Independently produced.
📊
Margin
Recovering value from a system already deployed carries no incremental capital outlay and no implementation risk. The investment has been made. What is required is the diagnostic to locate where the value chain has broken.
🏛️
Board
The capacity to answer what the technology estate is returning is no longer deferrable. The Value Signal Map makes it answerable, with evidence graded, assumptions explicit, and findings available for challenge.
The conclusion

The Gap Is Not Inevitable

The research is unambiguous: IT investment underperforms not because the technology fails, but because the conditions required to convert investment into financial performance are absent, mismanaged, or never measured. Those conditions can be identified, quantified, and managed.

When they are, technology stops functioning as a cost that must be periodically justified and starts functioning as a financial asset that returns measurable value.

The Value Gap is not a technology problem. It is a measurement problem. And measurement problems have solutions.

Know the range. Understand the assumptions. Close the gap.

← Part One ← Part Two Part Three: The Diagnostic
Warren Gabryk
Ph.D. · Founder and Principal · Axiom Value Partners · Sydney, Australia
Doctoral research in IT business value. Two decades spanning software development, enterprise architecture, C-level operations leadership, and Big Four financial advisory. Every engagement led at principal level.
View LinkedIn →

References

Bloch, M., Blumberg, S., & Laartz, J. (2012). Delivering large-scale IT projects on time, on budget, and on value. McKinsey Quarterly.

Brynjolfsson, E., & Hitt, L.M. (1998). Beyond the productivity paradox. Communications of the ACM, 41(8), 49–55.

Kohli, R., & Grover, V. (2008). Business value of IT. Journal of the Association for Information Systems, 9(1), 23–39.

Schweikl, S., & Obermaier, R. (2023). Lost in translation. Management Review Quarterly, 73(4), 1713–1749.

Ward, J., & Daniel, E. (2006). Benefits management: Delivering value from IS & IT investments. Wiley.

From the Practice
20266 min read

Who This Work Is For

The Value Signal Diagnostic is a single engagement with a single output: a financially expressed, evidence-graded assessment of what your technology investment is actually returning. The roles that commission it share one thing. They are making consequential decisions and need a number they can defend.
Private equity

You need a technology value number. Whether you are buying, holding, or selling.

Private equity firms encounter the technology value problem at every stage of the investment cycle. The diagnostic is structured to serve all three.

Buy
Acquisition due diligence
Before committing capital, you need to know whether the technology estate represents recoverable value or embedded risk. The diagnostic produces an independent, evidence-graded assessment of leakage, stranded investment, and governance exposure, expressed in financial terms your investment committee will recognise.
Hold
Value creation during the hold period
Technology spend is a significant and often under-scrutinised operating cost in a portfolio company. Understanding what it is returning, where value is leaking, and what dormant capability can be activated without new capital is a direct input to EBITDA improvement. The diagnostic identifies and sequences those opportunities.
Sell
Pre-exit vendor narrative
Value identified before the process opens is multiple-able. The same value identified during buyer due diligence becomes a discount. The diagnostic produces the technology value narrative before the information memorandum is drafted, on the seller's timeline and in the seller's interests.
🏦
What you get
An independent, evidence-graded technology value assessment. Expressed as leakage recovered and opportunity activated. Structured for the investment committee, the information memorandum, or both. Produced in five weeks at fixed scope.
M&A advisors

You need technology risk surfaced before it becomes a deal problem

Technology findings that emerge late in a transaction create price renegotiations, condition precedents, and sometimes deal failure. The diagnostic is structured to surface and quantify technology risk early: governance gaps, licence exposure, compliance obligations unmet, and transformation investment that has not delivered. Each finding is graded by evidence quality, not opinion.

⚖️
What you get
An independently produced technology risk and value assessment, evidence-graded and not generated by either party to the transaction. Each finding is expressed in financial terms with its evidence basis stated explicitly, so it can be challenged, defended, and relied upon by advisors on both sides.
Board and executive

You need a return figure the board can act on

Technology spend has become material. Boards and investors are asking what it is returning. The technology team can report on delivery and uptime. It cannot produce a financially expressed return figure independent of its own interests. That independence is the point.

🏛️
What you get
A technology value report structured for board presentation. Return on IT investment expressed in terms the board and investors recognise. Findings graded by evidence quality, assumptions made explicit, and a recovery roadmap sequenced by financial impact.

The board is not asking whether the technology works. It is asking whether the investment is performing. Most organisations only have an answer to the first question.

CFO and finance

You need margin recovery without a new capital programme

The most common source of recoverable margin in an established technology estate is not inefficiency in the business. It is unrecovered value already paid for: platforms deployed but not activated, licences renewed without challenge, vendor contracts running above market rates, and transformation investment that was never connected to the P&L. None of these require new capital to address.

01
Unactivated platform capability
Already licenced. Already deployed. The return has not been claimed because configuration was never completed.
02
Duplicate and redundant spend
Acquisitions and decentralised purchasing leave overlapping tools across the estate. Consolidation is recoverable at next renewal.
03
Vendor contracts above market rate
Without independent benchmarks, renewals run on the vendor's terms. The cost premium compounds with each cycle.
📊
What you get
A quantified leakage and recovery figure, expressed in dollars, with a phased roadmap. Immediate, short-term, and strategic actions sequenced by financial return. No new capital required.
CTO and CIO

You need an independent number to take to the board

The challenge for technology leaders is not capability. It is credibility. A return figure produced by the technology team will always carry the perception that it was produced by the team being evaluated. An independent assessment, graded against an explicit evidence hierarchy, removes that problem. The findings are yours to present. The independence is ours to provide.

💡
What you get
An externally produced technology value assessment you can present to the board without qualification. Evidence-graded findings, explicit assumptions, and a roadmap you can own and execute.
The common thread

One engagement. One output. Complete transparency on what your technology investment is actually worth.

Every role above is dealing with the same underlying problem. Technology investment is significant. The question of what it is returning is legitimate. And the answer does not currently exist in a form that survives scrutiny from a board, an investor, or a buyer.

The Value Signal Diagnostic was built to produce that answer. Five weeks. Fixed scope. Principal-led. Expressed in financial terms and graded by evidence so that every finding can be challenged, and stands up when it is.

If you recognise your role above, the conversation starts with a single call.

← The Value Gap ← Why Measuring More Does Not Solve It ← A Different Instrument From the Practice
Warren Gabryk
Ph.D. · Founder and Principal · Axiom Value Partners · Sydney, Australia
Two decades spanning software development, enterprise architecture, C-level operations leadership, and Big Four financial advisory. Every engagement led at principal level.
View LinkedIn →