Good IT operations should largely be invisible.
People should be able to work, systems should be reliable, risks should be understood and technology should support the direction of the business.
When that happens consistently, IT can move beyond simply keeping the lights on and become a genuine business partner.
This repository brings together practical approaches to operating, governing and continuously improving a technology function.
I tend to think about IT operations across six connected areas:
Strategy → Governance → Delivery → Operations → Measurement → Improvement
- Strategy determines where technology needs to go.
- Governance makes priorities, ownership and risk visible.
- Delivery turns decisions into change.
- Operations keeps services reliable and secure.
- Measurement tells us whether things are working.
- Improvement prevents the operating model from becoming static.
The value comes from keeping these areas connected.
Technology teams will always have priorities originating within IT, including:
- cybersecurity;
- infrastructure lifecycle;
- technical debt;
- resilience;
- end-of-life systems;
- regulatory requirements.
But IT should not independently determine the business value of every initiative.
A healthier model considers:
Business Value + Technology Risk + Cost + Capacity + Strategic Alignment
This creates a more transparent approach to prioritisation and helps technology become part of normal business planning.
I prefer to think of the people supported by technology as customers rather than simply users.
A user consumes a system.
A customer has a business need, an expectation of service and a perspective on what is important.
That distinction influences how technology teams listen, communicate, prioritise and measure service.
Practical approaches to technology governance and supplier management.
Operating disciplines that support reliable and resilient technology services.
Connecting technology investment to organisational priorities and future capability.
Creating visibility for technology leadership and executive decision-making.
IT service management should provide enough structure to make services reliable, supportable and continuously improving without creating process for its own sake.
Useful questions include:
- Are critical services performing as expected?
- Can people get help when they need it?
- Are recurring problems being removed?
- Can change be introduced without unnecessary disruption?
- Can critical services be recovered when something fails?
Business Continuity and Disaster Recovery should therefore be connected to normal technology operations rather than treated as separate documentation exercises.
Technology reporting should help leaders make decisions rather than simply demonstrate activity.
Useful measures may cover:
- service performance;
- risk and resilience;
- delivery progress;
- financial performance;
- capacity;
- improvement.
The purpose of a dashboard is to create visibility.
If a metric does not support a conversation, decision or action, it is worth asking why it is being reported.
Related examples in the Technology Leadership repository show how these principles can be applied in practice.
A practical example of shifting technology prioritisation away from being determined solely within IT.
Read: From IT-Led Priorities to Business-Led Technology
An example of using a multi-year technology roadmap to coordinate infrastructure, cloud, ERP, CRM, data, cybersecurity and organisational change.
Read: Leading a Multi-Year Digital Transformation
I don't see IT operations as the opposite of technology strategy.
Good operations create the foundation that allows strategy to happen.
Reliable Service → Trust → Business Partnership → Strategic Influence
That is where an IT function starts becoming an organisational technology capability.