For many businesses, IT is still discussed mainly when something needs attention. A system needs replacing. A security issue emerges. A new employee needs equipment. A site needs connectivity. A software contract is up for renewal.
Those are all legitimate technology conversations. But for organisations whose day-to-day operations depend heavily on technology, there is a bigger question worth asking: Is IT being considered as part of the operational strategy — or mainly after operational decisions have already been made?
Because as technology becomes more deeply embedded in how businesses operate, grow and serve customers, IT decisions increasingly become business decisions too.
For many leadership teams, the traditional measure of IT has been fairly straightforward. Are systems available? Can employees work? Are issues being resolved? Is cybersecurity being managed? Are costs under control?
Those questions still matter. But an environment can technically be “working” while still creating friction for the business. A new location may be difficult to bring online. Different sites may use inconsistent systems. Employees may rely on workarounds that management rarely sees. Important projects may take longer because the underlying technology is difficult to change. Leadership may spend more time dealing with technology issues than it would like.
None of those problems necessarily mean IT has failed. They may simply mean the organisation has evolved faster than the technology strategy supporting it. So the more useful question becomes: Is our technology helping us operate the way we want to?
Consider some fairly ordinary business decisions.
Opening another location.
Expanding a warehouse or production capability.
Hiring a larger field workforce.
Introducing a new customer service model.
Acquiring another business.
Launching a new digital service.
Introducing automation or AI.
Every one of those decisions can create technology requirements. Users need access. Devices need managing. Networks need extending. Systems may need integrating. Data needs to be available and secure. Support requirements may increase.
If IT becomes involved only after the operational decision has been made, the technology team is left answering: “How do we make this work?” A better conversation happens earlier: “What does the technology environment need to look like for this plan to work well?” That difference can have a meaningful impact on cost, risk and implementation speed.
Growth is usually good news. But it can also expose weaknesses that weren't particularly important when the organisation was smaller. A business operating from one location might manage technology relatively simply. Add another site, then another, and suddenly connectivity, identity, device management, support and security become more complex.
Add specialist applications, customer platforms, cloud services or operational systems and the environment becomes more interconnected again. None of these decisions is necessarily wrong.
The challenge is that complexity accumulates. If technology planning doesn't keep pace, growth can create an IT environment that becomes disproportionately difficult to manage. That can translate into slower projects, recurring issues, higher support effort and less flexibility when the business wants to change again.
Executives don't need to understand the technical architecture of every system. But they should have visibility over where technology is affecting operational performance. Some signs are obvious. Frequent outages. Slow systems. Recurring support issues. Other signs are more subtle.
Employees maintaining spreadsheets because systems don't exchange information reliably. Managers spending time fixing technology issues. Different locations developing their own processes because central systems don't meet operational needs. Projects taking longer because changing one system affects several others.
A useful leadership conversation therefore isn't simply: “What technology problems do we have?” It's: “Where is technology creating unnecessary friction in the operation?” That framing makes the issue easier to connect with productivity, customer experience, cost and growth.
Technology planning can easily become a list of things to buy or replace. Servers. Laptops. Security tools. Cloud services. Applications. Those decisions matter, but they should ideally follow a clearer understanding of what the business is trying to achieve.
If the operational priority is growth, technology might need to become easier to scale. If the priority is resilience, critical dependencies and recovery may deserve attention.
If the priority is improving productivity, integration or workflow problems may be more important than infrastructure. If the organisation wants to adopt AI, the first requirement may actually be better data or more consistent systems. The technology roadmap should therefore reflect operational priorities, rather than existing as a separate list of IT projects.
Good technology strategy requires two-way visibility. IT needs to understand where the business is heading. What growth is planned? What operational changes are coming? Which processes are creating frustration? What new customer expectations are emerging?
Leadership, in turn, needs enough visibility into the technology environment to understand constraints, dependencies and investment priorities. That doesn't mean executives need to become technical specialists. It means both groups should be planning from the same picture.
Otherwise, IT can optimise for stability while the business prioritises rapid change — or leadership can commit to an operational initiative without understanding the technology work needed to support it.
Alignment doesn't require IT to sit in every strategic meeting. It requires technology implications to be considered before they become urgent.
This is another useful indicator. In some organisations, senior leaders become surprisingly involved in day-to-day technology problems. They chase support issues. Coordinate vendors. Make decisions about applications. Help employees work around recurring problems.
Sometimes that is unavoidable. But if management is consistently spending time dealing with operational technology issues, it is worth asking whether the support model or technology environment is still right for the organisation.
The cost isn't only the IT issue itself. It's the management attention being pulled away from other priorities. That becomes particularly important as an organisation grows.
A technology approach that worked perfectly well at one stage of the business may no longer scale when the number of people, locations, systems or operational dependencies increases.
You don't need a detailed technology roadmap to begin connecting IT with operational strategy. Start with five questions.
Which systems, locations or processes would create the greatest disruption if technology didn't work as expected?
Look beyond major failures. Where are employees compensating for system limitations or inefficient processes?
Growth, new locations, acquisitions, automation, customer initiatives and workforce changes can all create technology implications.
Or will the organisation first need to address infrastructure, integration, security, data or support constraints?
A reactive approach isn't always avoidable.
But if every IT decision is triggered by something failing, reaching end of life or becoming urgent, the organisation may be missing opportunities to plan ahead.
Operational businesses increasingly depend on technology to function. That doesn't mean every technology decision belongs in the boardroom. It does mean that leadership should understand how the technology environment supports — or constrains — the organisation's broader plans.
The goal isn't to build an IT strategy for its own sake. It's to make sure technology can support growth, resilience, productivity and change without becoming an unnecessary source of friction.
Because the most useful question isn't simply: “Is our IT working?” It's: “Is our technology helping us run the business the way we want to — and will it still do that as the business changes?”
When those conversations happen early, IT stops being something the organisation reacts to. It becomes part of how the organisation plans what comes next.