Stop delegating tasks. Delegate the function.

Some leaders think they’re delegating when they’re really just dispatching.

The difference shows up in how the work moves. When you delegate a task, you stay in the loop. You’re approving, nudging, checking in, holding the outcome in your head. When you delegate a function, someone else owns the outcome and moves it forward whether you’re watching or not.

Picture a strong finance lead who owns the function. Budgets get built, forecasts get updated, the audit gets scheduled, cash gets watched. None of it waits on you to ask. Now picture a bookkeeper you have to poke every month to send the close report. Same domain, completely different relationship.

The same pattern shows up in marketing, HR, facilities, and IT.

This is where the conversation about managed IT services tends to go sideways. Leaders evaluate providers on task-level questions: how fast does the helpdesk respond, how quickly do tickets close, how smoothly do new users get set up. Those questions matter. They just aren’t function-level questions. They’re dispatching questions wearing a managed-services costume.

A function-level question sounds different. Does the proactive work that nobody is going to nag anyone about actually happen?

Things like: the annual IT plan that ties technology decisions to where the organization is actually going. The IT budget that doesn’t surprise the board in March. The lifecycle roadmap that says which devices and systems are aging out and when. The cybersecurity audit that gets scheduled because it’s time, not because something broke. The risk review that surfaces what’s quietly drifting. The governance conversation about Microsoft 365, or Copilot, or AI tools that staff are already using whether you’ve sanctioned it or not.

Nobody is going to file a ticket for any of that. It only happens if someone owns it.

A quick example of what function-level ownership actually looks like in practice. We worked with an engineering firm where the brief wasn’t “fix this ticket” or “stand up this server.” It was: build a phased IT roadmap, reduce reliance on aging in-house servers, get SOLIDWORKS workloads into Azure, and set the team up for flexible remote work with centralized cloud storage. That’s a function-level engagement. The output wasn’t a faster helpdesk. The output was a hybrid environment with less complexity, a scalable cost model that grows with the team instead of front-loading capital expense, and the security posture that comes with running inside Microsoft 365. None of that work was going to surface from a ticket queue. Someone had to be thinking about it on the firm’s behalf.

Here’s a test worth running: if you went on a three-month sabbatical tomorrow, would your IT function still move forward? Would the planning happen? Would the renewal conversations get scheduled? Would the risks get surfaced? Would you come back to find decisions waiting for you, or work already moving?

If the honest answer is that tickets would keep closing fast enough that nobody complains, but nothing forward-looking would happen, you haven’t handed off a function. You’ve outsourced a queue. That’s a real service. It just isn’t the same thing.

This is also the question to sit with before deciding whether to outsource IT or build it in-house. The choice isn’t really internal vs. external. It’s queue vs. function. A small in-house team can own the function beautifully if that’s what you’ve asked them to own. An outsourced IT partner can own it too. Either one can also drift into pure dispatch mode if nobody is clear about the brief.

The distinction matters more than it used to, because identity, security, data governance, productivity tooling, vendor sprawl, and employee experience are all being re-examined at once. The organizations that handle this well are the ones where someone is actively thinking about all of that on their behalf, not just reacting when something breaks.

And here’s the part worth sitting with: this isn’t a vendor problem first. It’s a leadership problem first. If you’ve never asked your IT partner (or your internal team) to own the function, they’ve probably defaulted to owning the queue. That’s a rational response to how they’ve been measured. The fix isn’t necessarily a new provider. The fix is changing the conversation about what you’re asking them to own.

A few questions that get at this directly:

What’s our IT plan for the next twelve months, and how does it connect to the business plan? Where are we on the technology lifecycle, and what’s the replacement schedule? What’s our current cybersecurity posture, and what’s changed since last review? What are the top three risks in our environment right now, and what are we doing about each? Where is shadow IT or shadow AI showing up, and how are we responding?

If those questions get answered crisply, without scrambling, you’ve handed off a function. If they get answered with “let me get back to you” or “we’d need to look into that,” you’ve got a dispatcher, not an owner.