NEW

Introducing SmartServices — AI-powered enterprise services for a smarter, scalable, experience-based service ecosystem. Learn more →

What Should IT Still Own?

Pomeroy

Related Articles

Facebook
X
LinkedIn
Email

The most valuable work for IT isn’t always the work that takes the most time.

Ask an IT leader what their team is responsible for, and the answer is rarely short. There are business priorities to support, risks to manage, new capabilities to deliver, and employees who expect technology to work. Then there’s the daily queue of requests, fixes, updates, escalations, and follow-ups. None of it disappears when a project ends, or a new person joins the team.

So, it’s worth asking more often what IT actually needs to own and what it just needs to make sure gets done well.

Those aren’t the same thing, and confusing them can leave capable teams spending too much of their day keeping things moving, with too little time to improve what comes next.

Ownership costs more than the work itself

Owning a responsibility means more than completing the task. Someone has to keep an eye on the process and catch problems before users notice them. When a fix depends on a hardware vendor or software provider, someone has to manage the handoff and keep following up until the issue is resolved. And when something escalates, it usually pulls senior people away from planned work at the worst possible moment.

Some of these costs are harder to see. Routine work often sits with one or two people who have handled it for years. When they take vacation, change roles or leave, the team finds out how much was never written down. Coverage creates a similar strain. Support doesn’t pause for holidays or open job requisitions, so someone still has to step in when the usual owner isn’t available.

You won’t find most of this in a ticket count. More often, you’ll find it in a roadmap that keeps getting pushed to next quarter.

Ownership is a decision, not a default

Keeping a responsibility in-house can be the right call. Some work is too closely tied to business strategy, sensitive decisions, or institutional knowledge to hand off. But “we’ve always done it” is not much of an ownership strategy.

A useful place to start is with five questions. Does this work help differentiate the business? Where must accountability and risk decisions sit? Does it require expertise the team needs to build or retain? How often does the work repeat? And what level of responsiveness or consistency does the business expect?

Consider endpoint support. IT may need to set security standards, define the employee experience and decide which issues warrant a business-level response. That doesn’t necessarily mean the same internal team needs to handle every routine ticket, device issue, or service request.

The goal isn’t to give up control. It’s to be more deliberate about where control matters most.

Four moments when the question becomes urgent

This ownership conversation often surfaces at familiar points in an IT organization’s growth.

You add people, but the backlog stays. Additional staffing can bring much needed skills and capacity. Yet if new hires inherit the same stream of repetitive work, the team may get busier without getting ahead. Before adding another role, it’s worth asking which tasks really require a permanent internal owner.

Finishing a project can add to the pile too. Go-live feels like the finish line, but for the team supporting the new system, the work is just getting started. Someone still needs to monitor performance, respond to issues, maintain documentation, and manage changes. When those responsibilities aren’t defined early, they tend to land on whoever knows the solution best, whether or not that’s a good long-term use of their time.

Even a well-built plan can stall for the same reason. Advisory work can clarify priorities and build a credible roadmap, but the harder part is often finding room to act on it. When the same people are expected to deliver transformation while handling every daily interruption, progress becomes difficult to sustain.

Device rollouts tend to play out the same way. Getting technology into people’s hands is only the beginning. Over time, devices age and applications get updated, and employees keep needing help as their expectations rise. Lifecycle planning has to connect with ongoing support, or the experience starts to slip a few months after rollout.

Each of these starts in a different place, but they all end up in the same spot, with the work of running IT crowding out the work of moving it forward.

There’s more than one way to own the outcome

This doesn’t have to be a choice between doing everything internally and outsourcing everything. Most organizations need a mix.

1. Keep It In-House

Retain ownership of work that drives competitive advantage, requires close business judgment or needs direct internal oversight.

2. Co-Manage

Share responsibilities with a trusted partner when internal knowledge and external expertise or operational support are both needed. This allows IT teams to stay involved without carrying the full workload.

3. Transfer Day-to-Day Operations

Move routine, repeatable tasks to a trusted partner who can deliver against clearly defined service expectations. Internal IT continues to set priorities, provide direction, and oversee performance.

Whichever model you choose, governance has to be clear. IT should know who makes decisions and who tracks performance. It should also know how exceptions are escalated and what happens when business needs change. A service agreement can describe the work, but the partnership itself depends on people talking to each other and working through problems together.

The best arrangement is the one that gives the business dependable service without leaving ownership ambiguous.

Start with one workload

You don’t need to redesign the entire IT operating model to make progress. Pick one recurring responsibility that consumes more attention than it should. It might be device support, routine maintenance, service desk requests, or the operational follow-through after a deployment.

Write down who owns it today, how often it comes up, what happens when it slips, who handles escalation, and what a good outcome would look like. Then ask a simple question: does the current owner need to perform this work, or do they need to be accountable for the result?

That distinction can reveal opportunities to reduce interruptions, establish clearer service levels, and make better use of internal expertise. It may also confirm that some responsibilities belong exactly where they are. Both are useful answers.

Make room for the work only IT can do

IT leadership is measured by how well technology supports the business. It shows in how carefully the team manages risk and how confidently the organization can act on new opportunities.

See where IT can offload the work

The question IT leaders should be asking is whether their teams are owning the right things, not if they should own less.

What’s taking up your IT team’s time?

Take a closer look at which responsibilities belong with your internal team and where ongoing operational support could make a difference.

Facebook
X
LinkedIn
Email

Resources

Add Your Heading Text Here

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

not clickable

Meet
The enterprise AI platform that lets you focus on ​more of what matters.