IT’s Biggest Leadership Problem of 2026
Elevating IT from Cost Center to Economic Asset
While most business functions are evaluated based on the value they generate, IT is still evaluated based on the cost it consumes.
Sure, everyone is talking about Digital Transformation, the Power of AI, and the need to eradicate shadow spend. But when financial pressure increases, leadership sharpens their pencils for some line-item reductions.
If the organization depends so heavily on technology, why are budget discussions often focused more on delivery activity than enterprise impact?
A Different Way to Think About IT
Instead of viewing IT primarily as a cost center that must continuously justify spend, I encourage CIO’s to position IT as an enterprise asset whose purpose is to produce measurable business value over time.
This is a subtle shift in language, but a profound shift in leadership behavior.
Asset-oriented thinking changes the conversation:
- from spend to return,
- from projects to outcomes,
- from technical activity to enterprise performance.
The question is no longer: “How much does IT cost us?”
The more strategic question becomes: “What measurable value is the organization receiving from its technology investment?”
That distinction changes how leadership evaluates IT. Cost alone is an incomplete measure of IT performance.
Value is Experienced, not Declared
One of the most overlooked aspects of IT value is that the business ultimately experiences IT the same way markets experience any enterprise capability: through outcomes, responsiveness, trust, and usability.
In other words, stakeholders don’t care if up-time was 99.9% if their teams fail to adopt the new system.
A technically successful implementation that frustrates users or fails to improve business performance rarely creates meaningful enterprise value.
I’m not recommending CIO’s abandon technical measures – they are important for managing IT. But I am saying greater emphasis on user-centered outcomes will dramatically improve stakeholders’ trust, respect, and confidence in IT.
Where to Start
Begin by introducing more explicit discussions around stakeholder outcomes:
- What business capability improved?
- What operational friction was removed?
- What measurable benefit did the organization experience?
Then work with your teams to identify these measures at the beginning of every project, affirm these with their business sponsors early, and measure the change.
This sounds simple, but it’s a significant change in management approach.
This is a Discipline, and a Skill
I’ve spoken to dozens of CIO’s about this shift, and they understand it intellectually.
But they struggle to operationalize it: IT teams are often far more comfortable discussing system metrics than articulating business outcomes. They want to, but they literally don’t have the vocabulary.
This challenge is one of the reasons we developed ImpactIT™, which is now being piloted with beta clients.
The goal is straightforward: help CIOs continuously connect stakeholder experience, operational outcomes, and IT investment into a clearer narrative of enterprise value.
Because ultimately, the future belongs to CIOs who can move the conversation beyond “What did IT deliver?” and toward “What value did IT create?”
This article is extracted from our white paper, The Disruption and Reengineering of IT Strategy.
