I have run service desks where the twelve-month retention rate was sixty percent. I have run service desks where it was ninety. The difference between those two organizations had almost nothing to do with compensation, very little to do with perks, and almost everything to do with whether the leadership team treated service desk roles as careers or as cost lines. That sounds obvious written down. In practice, the framing decision is the entire story, and most organizations get it wrong because the framing decision is invisible.

This is the retention playbook I run. It is not a list of programs. It is a set of decisions, made early, repeated quietly, that compound into a service desk that people stay in long enough to become good at it.

Fig. 1 · Retention against industry benchmark
Service desk twelve-month retention, 2020 to 2024. Industry benchmark roughly flat at 62 to 65 percent. The gap is the playbook.
100% 75% 50% good-enoughthreshold 2020 2021 2022 2023 2024 industry,62% 90%
Source. Industry benchmark: aggregated HDI service desk retention surveys, 2020 to 2024. Maria's teams: Apple Bank and RX Global aggregate, twelve-month voluntary retention, same window.

The framing decision

The first question I ask when I take over a service desk is who the team reports to. Not on the org chart. In the heads of the analysts. If the answer is the service desk manager and only the service desk manager, the team is in a dead-end role and they know it. If the answer is the service desk manager and the head of IT operations and, increasingly, the people two levels up who pay attention to who is rising, the team is in a feeder role and they know that too. The first kind retains at industry rates. The second kind retains at the rates in the chart above. The difference is whether the organization has decided to treat service desk roles as the bottom rung of a ladder or as the bottom rung of nothing.

None of that decision shows up in compensation bands or job titles. It shows up in who attends the new-hire orientation, who shows up to the team's quarterly meetings, who replies when an analyst sends a question up the chain. The decision is operational. It is also recurring. You make it again every week by who you spend time with.

Three career paths, mapped on day one

I have a sixty-minute conversation with every service desk hire in their first month. The conversation has one purpose: to map three plausible career paths they might pursue from this role, and to make clear that all three are equally legitimate. I am not asking which one they want. I am telling them three exist, and that the organization will support whichever they choose. The point is not the answer. The point is the offer.

Fig. 2 · The three paths I map for every hire
A thirty-day conversation that I have used with every service desk hire since 2014. Not prescriptive. Always offered.
01
The technical-deepening path
Toward systems engineering, platform ownership, or specialist tracks like security or infrastructure. The path most analysts assume exists. Confirm it. Name the next two roles. Identify who already walked the path.
02
The leadership path
Toward team lead, service desk manager, service owner, head of operations. The path most analysts do not assume exists for them. State it explicitly. Name the development steps. Make the first one available within twelve months.
03
The cross-functional exit ramp
Toward business analysis, product, project management, vendor management. The path the organization usually loses talent to anyway. Acknowledge it. Make the bridge inside the organization easier to cross than the bridge outside it.
Source. Maria Siegel. Used with every service desk hire since 2014 at RX Global and Apple Bank.

What I stopped doing about compensation

I used to spend a meaningful portion of my retention energy on compensation. Comp surveys, band reviews, retention bonuses for specific high performers, exit-counter offers. None of those moves are wrong. All of them are bandages on the wrong injury. Compensation prevents only one form of attrition: the one driven by an offer with a higher number. Compensation cannot prevent the attrition driven by an offer with a clearer path, a better manager, or a more interesting problem. Those three drive most of the attrition I see in service desk roles.

What I started doing instead was building each of those three things deliberately. The clear path is the conversation above. The better manager is the diligence below. The more interesting problem is a deliberate rotation of the team across the highest-leverage operational projects in the organization, which is what stops the work from feeling repetitive on month nineteen.

The fifteen-minute check I do every quarter

Once a quarter, with every team lead, I run a fifteen-minute conversation I think of as manager diligence. Four questions. First, who on your team would you be most surprised to lose, and what would you change tomorrow to make sure you do not. Second, who on your team is ready for their next role, and what is in their way. Third, who on your team has stopped growing, and is that because they have hit a ceiling we built, or one they brought with them. Fourth, what is one thing I could do as the head of this function that would make your job easier next quarter. The fourth question is the most important one. It is also the question I most need to be reminded to ask.

Your service desk retention rate is a leadership signal, not a labor market signal. The leaders who treat their service desks as a leadership pipeline keep their best people. The leaders who treat them as a turnover pool prove themselves right.

The best leaders lose their best people the right way

The counter-intuitive measure of a great service desk leader is not how many people stay on their team. It is how many of their best people leave their team for promotions elsewhere in the organization. A leader whose team produces three internal promotions per year is doing something profoundly different from a leader whose team produces zero, even if both teams have the same year-over-year headcount. The first leader is feeding the organization. The second is staffing it.

The retention rate on a service desk staffed by a leader who is feeding the organization will often look lower at first glance, because the leader is intentionally graduating their best analysts into other parts of the company. The aggregate retention to the organization, which is the number that actually matters, is dramatically higher. That distinction matters and almost no executive dashboard captures it. I have started reporting both numbers when I report service desk retention. The conversation it produces with my CFO is one of the most useful conversations I have all year.

What the 90 actually costs

The honest part of the playbook is that the retention rate is expensive in a way that does not show up on a budget line. It costs me time. The thirty-day conversation costs an hour per hire. The quarterly manager diligence costs an hour per lead, multiplied by the number of leads, repeated every quarter. The internal-promotion pipeline costs a recurring willingness to lose my best people. None of those are line items. All of them are decisions I make about where my attention goes.

If you can spend that attention, you can build a service desk that retains at the rates in the chart above. The chart is not a metric. The chart is a record of where attention has been spent. That is the entire playbook. Everything else is decoration.