Why IT Operations Must Align with Business Goals: Key Metrics and Strategies

Preface

IT operations is a complex discipline; to do it well you must understand not only what it is but also why it matters.

IT Is a Core Element of Modern Enterprises

Internet companies build their entire business on IT systems, which are themselves the concrete expression of that business. Modern IT systems are increasingly complex, relying on hardware, software, and network support.

If an IT system is built but left unmanaged, it will run for a while and then encounter problems, eventually failing, because its components can never be 100% reliable and many steps require human intervention.

The rise of the Internet adds a new challenge: performance. Traditional IT workloads are stable and predictable, whereas public‑facing services can experience sudden spikes that exceed capacity, as illustrated by the early 12306 ticketing system failures.

Because business depends on IT, enterprises must not only build systems but also keep them running smoothly. This is the fundamental reason why IT operations is essential.

To succeed in IT operations, several basic facts must be recognized:

All IT components (software, hardware, network) will encounter problems.

People make mistakes.

Every system has thresholds; exceeding them causes failure.

Business evolves, systems change, and technology advances.

Every action in an enterprise incurs both explicit and implicit costs.

All operational work revolves around these facts.

The Crucial Question

What is the goal of IT operations, and to what extent should a system be maintained?

This question is often overlooked by technical staff and becomes a source of conflict between decision‑makers and implementers. Enterprises set overall goals that are broken down into sub‑goals, one of which is IT operations.

For example: “Our IT system must be stable, reliable, and secure, but we cannot overspend.” Stability, reliability, and security are sub‑goals; cost is another sub‑goal, and these can conflict because achieving the former typically increases expense.

Typically, cost control and IT operations are handled by separate teams, leading to clashes when their objectives diverge.

How much should we spend? Where is the balance point?

The answer is that IT operation goals must align with business objectives. Both falling short of and exceeding those objectives create problems: excess effort incurs unnecessary cost, which is a loss for the enterprise.

To operationalize this alignment, specific indicators are needed, such as guaranteeing 5‑8 or 7‑24 availability, defining maximum tolerable downtime, maintenance windows, and whether service degradation is permissible. The core idea is to assess the impact of system unavailability on business and design constraints accordingly.

Generally, two metrics are used: the longest allowable downtime and the frequency of outages. These metrics together reflect system availability.

Short, frequent outages may be acceptable, but if they become too frequent they degrade user experience, as seen in the 12306 example where many brief interruptions still caused significant frustration.

Conclusion

Effective IT operations requires understanding that its purpose is to serve business goals and must be measured with concrete metrics to ensure alignment.