Sanjay K Mohindroo
Why boards must stop measuring IT by cost alone. Explore five practical changes to make technology accountable for growth, resilience, and business value.
From Cost Center to Growth Engine.
Reframing the IT Mandate
The biggest obstacle to turning IT into a growth engine is not technology. It is the way leadership defines, funds, and measures its contribution.
The Cost Center Trap Starts in the Boardroom
A 10% reduction in IT spending can look like a management victory. Until the business discovers that the savings have delayed a product launch, weakened customer retention, or constrained expansion into a new market.
I have spent close to three decades working with enterprise technology across industries, geographies, and leadership teams. One pattern has remained remarkably consistent: organizations expect technology to transform the business while continuing to manage IT primarily as a cost to be controlled.
That contradiction has consequences.
The conventional wisdom is that IT must first prove its efficiency before earning the right to participate in growth discussions. I believe that thinking is outdated.
IT should not have to graduate from cost center to strategic partner. Its mandate should be defined by business outcomes from the outset.
This does not mean technology spending deserves immunity from scrutiny. Quite the opposite. It means IT investments should face the same commercial discipline as investments in new markets, products, acquisitions, or manufacturing capacity.
The question is no longer simply, "How much does IT cost?"
It is, "What business value are we buying with that investment?"
Why Traditional IT Cost Management Falls Short
Most boards receive detailed information on technology expenditure. They see operating budgets, capital commitments, cybersecurity spending, infrastructure costs, and major transformation programs.
What they often do not see clearly is the relationship between those expenditures and business performance.
Consider two competing investment proposals.
One promises to reduce infrastructure costs by 15%. The other promises to reduce customer onboarding time from ten days to two, potentially improving conversion and accelerating revenue recognition.
The first proposal fits comfortably into a traditional IT efficiency discussion. The second requires technology, operations, finance, and commercial leadership to agree on a shared business case.
That is precisely why the second conversation is more difficult, and potentially more valuable.
Cost optimization is necessary. But treating it as the primary measure of IT performance creates an incentive to protect the current operating model rather than challenge it.
An efficient IT function supporting an increasingly uncompetitive business is not a strategic success.
The Real Shift: From Technology Delivery to Business Accountability
There is a fundamental difference between delivering a technology project and delivering a business outcome.
A platform can go live on time, within budget, and meet every technical requirement while failing to generate meaningful commercial value.
Conversely, a technology initiative may require additional investment but create substantial competitive advantage through faster market entry, better customer economics, or a more scalable operating model.
Boards must learn to distinguish between the two.
Imagine a global manufacturer operating across four continents. Its technology team proposes a major investment in supply chain visibility.
The traditional business case emphasizes systems integration, reporting improvements, and process automation.
A stronger business case asks different questions.
How much working capital could be released through lower inventory? How much revenue is lost through stockouts? Could better demand visibility reduce emergency logistics costs? How quickly would the investment pay for itself?
The technology may be identical in both proposals. The management conversation is entirely different.
One asks the board to approve a system. The other asks it to allocate capital against measurable economic outcomes.
That is what reframing the IT mandate actually means.
A Five-Part Framework for Making IT a Growth Engine
The transition requires more than appointing a commercially minded CIO or renaming IT as a digital business function.
It requires five changes in how leadership governs technology.
1. Start With Business Value, Not Technology Budgets
Every significant technology investment should connect to at least one measurable business objective: revenue growth, margin improvement, capital efficiency, risk reduction, or competitive differentiation.
Boards should demand a clear baseline, a target outcome, and a timeframe.
A proposal promising improved customer experience is insufficient. A proposal targeting a measurable reduction in customer acquisition costs or improvement in retention creates accountability.
2. Establish Joint Ownership of Outcomes
The CIO cannot independently deliver revenue growth, customer retention, or operational productivity.
Those outcomes depend on commercial decisions, process redesign, employee adoption, and management execution.
Every major technology initiative therefore needs a business executive who shares accountability with technology leadership.
If the project succeeds technically but fails commercially, both owners should be expected to explain why.
This eliminates the familiar situation in which IT declares successful delivery while the business reports disappointing results.
3. Rebalance the Technology Investment Portfolio
Boards should examine how much technology expenditure maintains existing operations, improves productivity, and creates future business opportunities.
There is no universally correct allocation.
A heavily regulated financial institution may reasonably dedicate more resources to resilience and compliance than a rapidly expanding digital business.
The critical question is whether the allocation reflects deliberate strategic choices or simply historical spending patterns.
Without this distinction, maintaining the past can quietly consume the capital needed to build the future.
4. Measure Value Realization, Not Project Completion
Traditional IT scorecards emphasize uptime, project milestones, budget adherence, and service performance.
These remain important, but they are incomplete.
Boards also need evidence of realized value: incremental revenue, reduced cost-to-serve, improved working capital, faster product launches, and lower exposure to material business risks.
Benefits should be reviewed after implementation, not merely forecast before approval.
If an investment promised measurable value within 18 months, leadership should revisit that commitment at 6, 12, and 18 months.
5. Give Technology Leadership a Role in Capital Allocation
Technology decisions increasingly shape business models, customer relationships, and competitive positioning.
Yet in many organizations, technology leaders enter strategic discussions only after major commercial decisions have already been made.
That sequencing is flawed.
The CIO should participate early in evaluating growth opportunities, acquisitions, operating model changes, and investment priorities.
Not because every strategic decision is a technology decision, but because technology increasingly determines the economics and feasibility of execution.
Growth Cannot Come at the Expense of Resilience
There is an important counterargument.
Not every technology investment produces visible revenue. Cybersecurity, regulatory compliance, disaster recovery, and infrastructure resilience may prevent losses rather than create new sales.
That does not make them less strategic.
A major outage can destroy customer trust. A security failure can create financial, regulatory, and reputational consequences far exceeding the cost of prevention.
Boards should therefore distinguish between investments that generate growth and investments that protect the organization's capacity to grow.
Both deserve rigorous economic evaluation, even when their benefits require different measures.
The objective is not to turn every technology function into a profit center. It is to stop confusing the absence of direct revenue with the absence of business value.
What Boards Should Ask at the Next Meeting
The most effective change may begin with a different set of questions.
Instead of asking only whether IT is operating within budget, ask which technology investments have produced measurable business results.
Instead of focusing exclusively on project delivery, ask which expected benefits have not materialized and who is accountable.
And instead of approving next year's technology budget as a continuation of last year's expenditure, ask whether the investment portfolio reflects the company's future competitive priorities.
These questions change behavior because they change what leadership rewards.
Technology leaders become more commercially accountable. Business executives become more responsible for adoption and value realization. Boards gain a clearer basis for allocating scarce capital.
The IT Mandate Is Ultimately a Leadership Decision
The shift from cost center to growth engine will not be achieved through another transformation slogan, organizational restructuring, or wave of technology investment.
It begins when the CEO and board stop treating technology strategy as something separate from business strategy.
Over three decades, the technology landscape has changed beyond recognition. What has changed far less is the tendency to judge IT by what it spends rather than what the enterprise achieves.
That is the mindset that must change.
The future of IT is not about spending more on technology. It is about demanding more business value from every technology decision.
The real question for boards is this: If your CIO delivered every project on time and within budget, but the business gained no competitive advantage, would you still call IT successful?
Share your perspective in the comments, or subscribe to TechnologyTrends for more boardroom-level insights on technology, leadership, and business value.