The Strategic Liability of Viewing Technology as a Cost Center
Walk into most boardrooms and ask: “What's the role of technology in your business?” You'll hear variations of the same answer: “Technology is critical to our operations. We need to keep the lights on, minimize downtime, and keep costs under control.”
Translation: technology is an operational function. A necessary cost. Like facilities or HR.
That mindset is a competitive liability. Every board that views technology as a cost center—rather than as a source of competitive advantage—is leaving money on the table. And worse, they're ceding advantage to competitors who get it right.
The organizations winning in their industries are the ones where the board understands technology as strategic. Where board-level conversations about technology happen on par with conversations about market strategy and customer experience. Where technology investments are evaluated on their competitive impact, not just their operational cost.
“Boards that treat technology as a cost center are making a strategic error they don't realize they're making.”
Misconception 1: Technology Is an Operational Function
The Misconception:Technology's job is to keep the systems running reliably and keep costs under control.
The Reality:In the modern economy, technology is strategy. How you deploy technology determines competitive positioning. Amazon's competitive advantage isn't just low prices—it's a technology platform that enables fast, convenient shopping. Netflix's advantage isn't just great content—it's recommendation algorithms that keep people watching. Stripe's advantage isn't just payment processing—it's developer experience that makes integration easy.
Your organization has the same dynamic. Customers don't choose you just because of what you sell. They choose you based on how you deliver it. And how you deliver it is determined by your technology.
If your CTO reports to your COO (Chief Operations Officer), you've signaled that technology is an operational function. If your CTO reports to the CEO, you've signaled that technology is strategic.
The best organizations have CTO-level leadership that sits at the strategy table alongside sales, marketing, product, and finance.
Misconception 2: We Need to Spend More on Technology
The Misconception: Our technology challenges are about budget. We need to invest more.
The Reality:Most organizations don't have a spending problem. They have a spending prioritization problem. They're investing in the wrong things, in the wrong order, with the wrong governance.
A typical enterprise is spending 4-6% of revenue on technology. The problem is rarely that this amount is too low. The problem is usually that:
- 70% goes to maintaining legacy systems (cost of keeping the lights on)
- 20% goes to requested projects (many of which don't deliver value)
- 10% goes to strategic investments (the competitive differentiators)
The solution isn't spending more. It's reallocating. It's asking hard questions about the 70% going to maintenance. Can you modernize systems to reduce maintenance costs? Can you divest from systems that aren't creating value?
Once you've optimized the 70%, you can invest more in the 10%. That's where competitive advantage lives.
But this reallocation is hard because it requires making decisions about what to stop doing. Many boards avoid this conversation.
Misconception 3: Our CTO Handles Technology, So the Board Doesn't Need to Understand It
The Misconception:We hired a capable CTO. That person handles all technology decisions. The board doesn't need to be involved.
The Reality:Delegating technology decisions is abdicating board oversight. The board's job is to understand the business and identify risks. Major technology decisions create major business risks.
If your organization is making a major platform migration, the board should understand what the risks are, what the timeline looks like, what the exit strategy is if things go wrong. You don't need to understand the technical details, but you need to understand the business implications.
If your organization is acquiring another company, the board should do technology due diligence. What are their systems? How do they integrate with yours? What technical debt are you inheriting? Again, not the details—but the implications.
The best boards ask good questions about technology without pretending to be engineers. “What happens if this migration fails?” “How long would we be down?” “What would recovery look like?” “What's our worst-case scenario?” “How confident are you in this plan, and what would change your mind?”
These are the questions that separate boards that govern well from boards that abdicate.
Misconception 4: We Can Evaluate Technology Investments Like Other Capital Expenditure
The Misconception: We have a process for evaluating capital expenditure. We should use the same process for technology investments.
The Reality:Technology investments are different. They're harder to evaluate upfront because the outcomes are less certain. They often enable opportunities you didn't know would exist. They create competitive advantages that aren't easily quantified.
A capital investment in new manufacturing equipment has a clear ROI calculation: it costs X, saves Y per year in labor, has payback period of Z years. Done.
A technology investment to build a new analytics platform has a less clear ROI: it enables better decision-making, faster time-to-insight, improved customer understanding. But you can't easily quantify all of that upfront.
This doesn't mean you shouldn't evaluate technology investments. You should. But the evaluation framework is different:
- What decisions will this enable that we can't make now?
- What competitive advantage does this create?
- What would happen if we don't make this investment?
- What's the timeline for value realization?
- What are the risks if we move too slowly vs. too fast?
These are strategic questions, not just financial questions. They require board-level judgment, not just financial analysis.
What Effective Board Technology Governance Actually Looks Like
Practice 1: Regular, Structured Technology Updates
The board receives quarterly updates on the state of technology in the organization. Not the technical details, but the business implications: major initiatives underway, risks on the horizon, resource constraints, competitive moves requiring technology response.
This should come from the CTO or technology leader. It should be 30-45 minutes. It should be structured so the board can ask good questions.
Practice 2: A Technology Strategy That's Part of Business Strategy
Your organization has a business strategy. Your board discusses it, challenges it, approves it. You should have an equally explicit technology strategy.
Not a 200-page technology roadmap. A one-page articulation of: What competitive advantages are we trying to create through technology? What platforms are critical? What legacy systems need modernization? What capabilities do we need to build or acquire?
Your board should debate this. Challenge it. Make sure it's aligned with business strategy. And then hold management accountable for executing against it.
Practice 3: Board-Level Understanding of Key Technology Risks
What are the technology risks that could materially impact the organization? Security? Data privacy? System failures? Talent? Legacy system fragility?
Your audit committee should have a framework for assessing technology risk and regularly evaluating how management is managing the top risks.
This doesn't mean the board becomes a technology committee. It means the board identifies key risks and has confidence that management is managing them.
How to Improve Board-Level Technology Fluency
Not everyone needs a PhD in computer science.But board members should develop basic technology literacy. You don't need to understand how machine learning algorithms work. You do need to understand what ML can and can't do, and what risks come with it.
Hire board members with technology backgrounds. Your audit committee should have someone with technology expertise. Your overall board composition should reflect the importance of technology to your business.
Ask good questions.The best questions don't require technical knowledge: “What would change your mind about this technology decision?” “What's your worst-case scenario?” “How would you know if this strategy isn't working?”
Take time to understand your technology landscape.Spend a day every year learning about your organization's technology. Visit the engineering team. Understand what systems are critical. Understand what's broken.
Bring in outside expertise when needed. For major technology decisions or risks, bring in advisors who can help the board ask good questions and understand the implications.
The Competitive Reality
Here's the competitive reality: the organizations that will win in the next decade are the ones where boards understand technology as strategic. Where board members can have intelligent conversations about artificial intelligence, data platforms, and software architecture. Where technology investment decisions are made with the same rigor as business strategy decisions.
Organizations where boards view technology as an operational cost center will steadily lose competitive advantage. They'll fall behind. They won't understand why.
It's not complicated. It just requires recognizing that in the modern economy, technology isn't a support function. It's the foundation of competitive advantage.