^{READ TIME: 6 MINUTES}

Apologies! I’ve been AWOL for a few weeks. In June we had a wedding in the family and then a big family trip to Italy (a great pic here). And to top it all off, my wife and I moved house across the country last week. To say it has been a hectic time would be a massive understatement!!

To kick things off again though, this week I’d like to focus on what is easily the single biggest challenge holding back data teams and their leaders among the data leadership folks I work with: The Data Service Desk

This is easy the top challenge I deal with among my data leadership coaching clients precisely because it is holding them back from achieving more as leaders.

It’s when data teams operate as pure service desks, supporting ad hoc and often random requests from a wide range of stakeholders across the business. This is sometimes managed via a ticketing system but more often than not, the intake process for requests is informal. Requests will come in via slack messages, WhatsApps, Teams DMs, scrunched up little pieces of paper, or even just shouted across the room at you: usually at around 5pm on a Friday 🤬

While there should always be some room for ad hoc requests to come via the data team, it shouldn’t be their main pillar of focus or primary source of work to be done.

Some teams I encounter spend 95%+ of their time working on requests of this nature.

It’s a dynamic that is holding data teams back and limiting their ability to be strategically impactful. As a data leader, navigating away from pure service desk to a more sustainable support/strategic ratio should be your highest priority. Today’s edition of Strategic Data Leadership will explore how.

Let’s dive in 👇🏻

Getting out of service mode isn't optional if you want to have real influence in your organisation. Teams that stay reactive get treated as internal support, and once that reputation sets in, it's very hard to shake off.

For data leaders like you, escaping the service trap won't automatically land you a seat at the strategy table. But staying stuck in service mode guarantees you'll never get anywhere near it. You can't build a case for strategic influence while you're stuck fixing dashboards no one looks at.

Your team feels this too. People want to work on things that matter, not just clear a queue of requests from around the business. And the organisation feels it in its own way: when the data team is stuck in reactive/service mode, it is not available provide key insights and to support crucial decisions. So they’re made without it.

This is worth fixing as soon as possible.

_{Quick Poll}

Unfortunately, staying stuck in service mode doesn't just cost you time. It also rewires how the business sees your function, and once that perception sets, it's brutally hard to shift away from it.

Here's what it costs you:

🔹 You become the default answer to "can someone just pull this?" Every time you say yes to a low-value ask without push back, you teach the business that this is what your team is for. That lesson sticks. Reversing it takes ten times the effort it took to create.

🔹 Your best people will leave first. Constant context-switching between someone's dashboard emergency and an actual piece of analysis is exhausting, and your strongest analysts are the ones with the most options elsewhere.

🔹 You lose the right to say no. While you're seen as a service function, "no" comes across as unhelpful rather than strategic. It looks like you’re just trying to get out of having to do something rather than being someone who ruthlessly prioritises what is key for the business’s success.

🔹 You're permanently on the back foot in budget conversations. A team that fields requests can't easily point to outcomes it drove. A team that's constantly reactive struggles to show the business what it would lose without them, which makes them an easy line to cut when finance get tight.

🔹 Strategic work never gets protected time, because there's always a more urgent ad hoc request in the queue. You keep telling yourself you'll get to the important stuff once things calm down. They never calm down. And you never get to those items.

None of this requires a reorg or a new operating model for the team. It requires you to change how your team responds to requests and how you talk about the team's role around the business.

✅ Triage like a mo-fo. A simple intake process is essential. It's a mechanism that stops "everything is urgent" from being the default. For every request, ask what decision it enables and what happens if it doesn't get done. If nobody can answer that, it goes to the bottom of the list or gets automated. The goal isn't to say no more but rather to say yes to the right things.

✅ Protect proactive time like you'd protect a client meeting. Waiting for a quiet week to get on with more strategic work is a fools errand. Block it in the calendar, treat it as non-negotiable, and defend it the same way you'd defend time with your most important stakeholder.

✅ Pick one hero project and make it undeniable. Choose a single initiative with clear, visible and strategic business value, resource it properly, and over-deliver. This is your proof of concept for what the team can do when it isn't always reacting.

✅ Build self-serve so your team stops being the bottleneck. Recurring requests are a signal that something should be automated. Stop answering the same question forty times.

✅ Change your vocab with stakeholders. Stop responding to requests with "sure, when do you need it." Start responding with "here's what would actually move the needle, and here's why." The shift in language repositions you as a business partner, rather than someones errand boy/girl.

This becomes a standard you hold every time a new request lands on your desk. Do it consistently and the perception shift will follow.

Helping data leaders overcome this challenge is one of the core focuses of my data leadership coaching. If you’d like help tacking this, why not set up a free 30 mins with me to discuss ways I can help.

Head here to book time with me.

Free resources:
Data Leadership Playbook · Data Career Compass · Data Leader Assessment

Tristan Burns
Find me on LinkedIn