Many IT departments are busy all the time yet still seen by the business as slow, expensive and hard to work with. Requests disappear into inboxes, the same outages recur, priorities change weekly, and licenses are paid for but barely used. In my experience, the cause is rarely a lack of effort or talent. It is the absence of a well-designed operating model and an operational excellence mindset.
What an IT operating model covers
- Structure and roles. Who is accountable for each service, platform and decision.
- Processes. How requests, incidents, changes and problems are handled, consistently and measurably.
- Governance. How priorities are set, investments approved and performance reviewed.
- Sourcing and vendors. What is done in-house, what is outsourced and how suppliers are managed.
- Skills and culture. The capabilities the team needs and the behaviors expected.
Designed deliberately, these elements make IT run like a service organization rather than a collection of busy individuals.
Borrow from best practice
Frameworks such as ITIL capture decades of experience in running technology services. You don't need every practice, but a few core ones deliver outsized value:
- Service catalog. A clear list of IT services with agreed service levels.
- Incident and request management. One front door, consistent handling and visibility of what is outstanding.
- Change management. Fewer self-inflicted outages through planned and approved changes.
- Problem management. Fixing root causes instead of the same symptoms every week.
- Portfolio and capacity planning. Matching demand to resources so the most valuable work comes first.
- Supplier management. Holding vendors to measurable performance.
When I introduced ITIL-based service management, the most visible change was a single point of contact for every IT service. Staff no longer had to know whom to email or call; every request and incident entered one front door and was tracked to completion. Just as valuable, we could finally monitor performance and produce reliable metrics. Those numbers brought accountability to the IT team, transparency to the business about what was being delivered, and a factual basis for continuous improvement.
Fit-for-purpose, fully used technology
Operational excellence also means getting full value from every technology investment. Many organizations pay for features they never switch on, run several tools for the same job, or buy new systems when existing platforms could meet the need. A disciplined operating model tracks consumption, retires duplication and makes sure new technology is chosen because it fits a business need.
The same discipline applies to cloud. Without cost governance, known as FinOps, cloud bills grow faster than the value they deliver. With it, resources scale to real demand and spending becomes transparent to the business.
The mindset behind it
Frameworks help, but operational excellence is ultimately a mindset: measure what matters, fix root causes, standardize what can be standardized, and keep improving. Teams that work this way deliver more reliable services, respond faster to the business and free up budget for innovation.
A quick self-check for leaders
- Do we have a published catalog of IT services with agreed service levels?
- Do we know which incidents keep recurring, and why?
- How many of our software licenses are actually used?
- Do our vendors report against measurable performance targets?
- Can we explain our cloud costs to the business by service or department?