What Burnout Actually Looks Like on a Help Desk

Thursday, 15:40, at Tollgate Foods. Nadia runs a desk of four and has just scrolled through the tickets Oskar closed this week. There are twenty-three of them, which is about normal, and the last fourteen carry the same resolution note: "Done." Oskar used to write the best notes on the desk, the kind a stranger could follow a year later. He is at his desk now, headphones on, and the phone beside him rang four times before he picked it up. Nothing is broken. The queue stands at sixty-one, and nobody has complained. Nadia cannot name a single thing that is wrong, which is why she has said nothing for three weeks.

She has, without the vocabulary for it, noticed the early shape of burnout. Burnout, as this series uses the word, is what happens to a person when the work has taken more from them, for longer, than they have been able to put back. They are worn out, and they have gone distant from the work and the people in it. They have stopped believing that what they do changes anything. That is a description of a working condition, not a medical finding. This article, and the whole of our Helpdesk Burnout series, treats it as an occupational matter: something a desk's design and management produce, and something they can therefore reduce. Where a person is unwell, the right advice is to speak to a doctor, or to the organisation's support programme if it has one. This library does not go further than that.

It covers why a help desk wears people differently from most jobs, and the four shapes burnout takes on a desk. Then come the early signs a colleague can notice, the early signs you can notice in yourself, and the signs that show in the ticket data. It covers how to tell a bad fortnight from a pattern, and what to do when you see it. It ends with a short war story and the early-signs checklist for self and manager, in that order.

Why a Help Desk Wears People Differently

A help desk is one of the few jobs where the work arrives already upset, in small pieces, all day, from people who can see you. A developer gets a bad bug and a quiet afternoon to think about it. A technician gets forty bad small things, each with a person attached who is late for a meeting, and no afternoon at all. None of the forty is hard. The weight is in the number and the pace. It is also in the fact that each one needs the technician to be pleasant on arrival, whatever the previous thirty-nine were like.

The second difference is that the work is never finished. A project has a last task. A queue has a next one. Even a desk that is keeping up, closing as many tickets as arrive, ends every day with a queue that looks exactly as it did that morning. The technician's sense of progress has to come from somewhere other than the number going down. Most of the time it does not come from anywhere. The queue is not ungrateful, exactly. It simply has no mechanism for noticing effort.

The third difference is visibility. The technician is the face of every system in the building, including the ones they did not choose, cannot fix and were not told about. When the mail service is slow, the technician hears about it fourteen times before lunch. The person actually responsible for the mail service hears about it once, from the technician, politely. Being the point of contact for other people's failures is a job in itself, and it is rarely in the job description.

Put those three together and a desk can wear a good person down without any single day being bad. That is what makes it hard to see. There is no outage week to point at, no project that went wrong, no incident with a date on it. There is a person who was fine in the spring and is not fine now. There is a queue that looks the same as it always did.

The Four Shapes It Takes on a Desk

The first shape is all-day interruption: a working day made entirely of other people's timing. The phone, the chat window, the person at the elbow and the e-mail that begins "quick one" each arrive on their own schedule. The technician's own plan for the day, if they had one, is abandoned by ten past nine. The cost is larger than it looks, because every interruption also spoils the few minutes before and after it. That cost is the subject of the next article in this series, The Interruption Load and Why It Is Different. Here it is enough to say that a day of forty small things is heavier than a day of four large ones. Most desks are built as if the opposite were true.

The second shape is emotional labour. It is the work of being calm and kind on the outside regardless of what is happening on the inside, repeated for every requester. Most people on a desk are good at it, which is why it goes unnoticed. There is the requester who is frightened about a lost file, and the manager who is angry about a laptop. There is the colleague who is rude because they are embarrassed. Each takes something from the technician that appears in no ticket field. The in-the-moment handling of an angry requester is covered in Working With Frustrated Users. What matters here is that each of those conversations has a cost even when it goes well, and the cost accumulates.

The third shape is the queue that never reaches zero. Technicians are, by selection, people who like finishing things, and a desk is a place where nothing is ever finished. A good day on a desk is one where the queue is the same size as yesterday. On a bad week it grows, and the growth is visible on every screen in the room, all day, with a count on it. I have watched capable people start to take the count personally, as though sixty-one open tickets were a verdict on them rather than on the staffing. The count has never once returned the feeling.

The fourth shape is the person who is always available. This is the technician who answers the phone on the first ring and replies to chat in the evening. They take the walk-ups because they sit nearest the door, and cover the gaps because they are the one who can. They are usually the best person on the desk and often the most senior, and the desk is quietly organised around their availability. The hero pattern is one of the ways support quietly fails as a system; the point here is what it does to the person. Being the one who is always there is not a personality trait. It is a load, and it is the one load the rota never shows.

The Early Signs a Colleague Can Notice

The signs that matter are the ones that show early, in behaviour, to someone who sits nearby. By the time a person says "I cannot do this any more", or stops coming in, the early signs have been visible for weeks to anyone who was looking. Usually nobody was, because the person was still there and the queue was still moving. The table lists the five I have seen most often, what each looks like on a desk, and what it is usually mistaken for. The mistake is the reason it goes unnoticed.

Two of those deserve a longer look because they are the ones most often praised. The quiet technician is the hardest to see, because a person who has stopped complaining looks, from a manager's chair, like a person who has matured. They have not. They have stopped believing that complaining changes anything, which is a different thing and a worse one. A desk where the complaints have stopped has either fixed everything or lost the people who noticed, and the first has never happened.

Tickets closed badly is the sign a manager can see without looking at the person at all. The notes shorten first, because a note is the part of the job the requester does not see and nobody checks. Then the closing reply goes, then the confirmation, then the category. Each is a small withdrawal of care from the part of the work that only the desk itself values. Together they are a person conserving what they have left for the parts that will be noticed. What a proper close looks like is in Closing Tickets Properly; here, the change is the point. The technician who wrote good notes in the spring and writes "done" in the autumn has not forgotten how.

Cynicism needs one caution. Every desk has gallows humour, and most of it is healthy. A team that cannot laugh at the printer that has failed for the ninth time this month is in more trouble than one that can. The sign is not the joke. It is the joke that has stopped being fond. When "they'll only break it again" is said with a smile, it is the desk coping. When it is said flat, to nobody, it is somebody who has stopped seeing a person at the other end of the ticket. That is the change to notice.

The Early Signs You Can Notice in Yourself

The signs in yourself are harder to see than the signs in a colleague, because the person doing the looking is the person who is tired. A few are reliable because they are about facts rather than feelings. You are at your desk before anyone else and after everyone else, and the queue is no smaller for it. You check the queue from your phone in the evening and feel worse, not better, for knowing. The first ring of the phone produces something closer to dread than readiness. A ticket you would have found interesting a year ago now produces nothing at all.

The clearest sign I know is the weekend test. A tired person recovers over a weekend and arrives on Monday at something like their normal level. A person on the way to burnout arrives on Monday at Friday's level, the weekend having done nothing. After a few weeks of that the holiday does nothing either. If you come back from time off feeling as though you never left, that is information, and it is not information about your character.

Second, notice what you have stopped doing. Not what you are doing badly; what you have quietly dropped. The note you used to write. The knowledge base article you used to draft when you found a fix. The question you used to ask in the huddle. The walk over to a colleague's desk to see how their week was. Each of those was something you did because you had something left over. The list of what you have stopped is a fair measure of what is left.

If you are reading this paragraph and recognising yourself, two things are true at once. The first is that the desk's design is doing this to you, and the rest of this series is about changing the design. The second is that a person who is genuinely unwell, who is not sleeping, who cannot face the building, is beyond what a management article can help with. In that case, the right next step is a doctor, or the organisation's support programme if there is one. Those two truths do not compete. You can fix the rota and see a doctor in the same week, and the people I have known who recovered well did both.

The Signs in the Ticket Data

A desk that keeps proper tickets leaves a record of its people's condition whether or not anyone reads it. The record is useful because it is not an opinion. The signs are the same ones a colleague would notice, translated into fields. Resolution notes get shorter, measurably, over a month. The reopen rate on one person's tickets climbs while their close count holds, which is a person closing faster than they are fixing. Activity on tickets appears in the evening and at weekends, from the same name, where it did not before. Leave is carried over and not booked. The close count per week goes up and the hours in the building go up with it.

Read those signals the way the last article in this series, Measuring Load Without Surveillance, describes. Read them as capacity signals about the desk, never as performance figures about a person, and never from a small sample. A per-person reopen rate from a dozen tickets is noise. The same rate from a hundred and fifty, moving steadily for six weeks, is a conversation that needs having. The conversation is "what has changed about the work", not "what has changed about you". Any tool with a complete event history on each ticket will show the pattern. If you run QuerySolv, the history is already on every ticket, and shortening notes are a filter rather than an impression.

The data has one advantage over the colleague and one disadvantage. The advantage is that it does not look away, and it never decides that a person who has stopped complaining has matured. The disadvantage is that it cannot tell you why. A rising reopen rate might be a tired technician, a broken fix for a recurring problem, or a new requester who reopens everything to say thank you. The data points at the person; the conversation finds out which. Do not skip the conversation on the strength of a chart. A chart has never once asked anyone how they were.

A Bad Fortnight or a Pattern?

Every desk has bad fortnights, and the difference between a bad fortnight and burnout is not how bad it is but what happens afterwards. A bad fortnight has a cause you can name: the upgrade, the outage, the colleague on leave, the start of term. It has an end, and when the end comes the person recovers, usually within a week, and goes back to writing notes and asking questions. Every sign in the table above appears during a bad fortnight. That is normal. It is a person under load behaving like a person under load.

A pattern is when the signs stay after the cause has gone, or when there was never a cause you could name. The outage ended three weeks ago and the notes are still one word. The colleague came back from leave and the quiet technician is still quiet. The weekend test keeps failing. Six weeks is a reasonable line. A person who is still showing the signs six weeks after the thing that caused them is not having a bad fortnight. Waiting another six to be sure is the most common way a manager turns a recoverable situation into a resignation.

The second test is whether the signs track the queue. A person whose mood rises and falls with the ticket count is tired, which is a load problem and a rota problem, both fixable. A person whose signs have stopped responding to the queue at all, who is no better on a quiet Friday than on a bad Monday, has moved past tired. The queue is no longer the thing doing it; the accumulated weight of all the previous queues is. That is the point at which the fix is no longer a quieter week, and Recovery After a Bad Stretch is about what the fix is instead.

What to Do When You See It

If you are the colleague, say what you saw, not what you concluded. "Your notes have got really short lately and you've been eating at your desk; is everything all right?" is something a person can answer. "I think you're burning out" is a verdict, and most people's first response to a verdict is to dispute it. You are not there to diagnose anyone. You are there to say that you noticed, which on a busy desk is rarer than it should be. You are there to make it easy for the person to say more if they want to. Then, if what they say worries you, tell the manager, with the person's knowledge where you can. Carrying it alone helps nobody and adds a second tired person to the desk.

If you are the manager, lighten the load first and ask second, because asking a tired person to describe their tiredness is itself a task. Take them off queue duty for a week. Move the project deadline. Take the evening chat off their phone. Then have the conversation, and have it as a question about the work rather than about them. Ask what has changed, what is heaviest, and what they would drop if they could. The questions that make that conversation useful are the template in The Manager's Responsibilities. What you do with the answers is the rest of this series.

If you are the person, the single most useful thing you can do is tell somebody who can change the rota, in plain words. Do it before the weekend test has failed for the sixth time. It is not weakness and it is not a complaint. It is operational information about the desk's capacity, which the desk needs and cannot get any other way. And where the tiredness has become something a quieter week will not touch, speak to a doctor. That sentence appears twice in this article on purpose.

Whatever your seat, do not wait for certainty. Nobody is ever certain, because the signs are ordinary behaviour done slightly less, and there is no moment at which they stop being ordinary. The cost of acting on a false alarm is a week of lighter rota for someone who was merely tired, which is a week they would have benefited from anyway. The cost of waiting is in the next section.

A Short War Story: The Quiet Technician at Ashgrove Housing

At Ashgrove Housing, a technician called Dev had been the desk's steady centre for four years: first in, last out, the one whose runbooks everyone else used. Over one winter his notes shrank from paragraphs to "fixed", and he stopped coming to the Friday huddle. His manager, Rhea, read the quiet as a good sign, because he had stopped complaining about the tenant portal. In the spring Dev resigned with a two-line e-mail. The desk discovered that about a third of what it knew about the portal, the housing system and the field laptops had been in his head and his inbox. He had stopped writing any of it down at about the time the notes shrank. Replacing him took five months. The two remaining technicians each worked a month of long days covering the gap, and one of them left before the replacement started. Rhea's review of the year listed the early signs she had seen, with dates, and every one was in the table above. The lesson she wrote at the bottom was that a technician who has stopped complaining has not stopped having anything to complain about.

The Early-Signs Checklist

The checklist has two halves, one for you and one for a manager or colleague looking at someone else. Both are meant to be run on a calendar rather than when something feels wrong. The whole point is that nothing feels wrong until late. Run the self half once a month, honestly, on a quiet day. Run the manager half for each person on the desk once a month, from what you have seen and from the ticket data. Write the date beside any item you tick. Three ticks in one month is a conversation. Three ticks in each of two months is a pattern, and the rest of this series is what to do about it.

EARLY-SIGNS CHECKLIST — SELF AND MANAGER
Month: ____________   Desk: ______________________

PART A — FOR YOURSELF (once a month, on a quiet day)
  [ ] The weekend did not restore me; Monday felt like Friday
  [ ] I check the queue in the evening and feel worse for it
  [ ] The phone ringing produces dread rather than readiness
  [ ] I have stopped writing proper notes, drafting articles, or asking in the huddle
  [ ] I am in the building longer and the queue is no smaller for it
  [ ] I have leave I could take and have not booked it
  [ ] A ticket I would once have found interesting produces nothing
  [ ] I cannot name a cause for the above, or the cause ended weeks ago
  Ticks this month: ____   Last month: ____
  Three or more: tell someone who can change the rota: ______________

PART B — FOR A MANAGER OR COLLEAGUE (per person, once a month)
  Person: ______________   Looked at by: ______________
  Seen in behaviour
  [ ] Jokes about requesters have turned flat rather than fond
  [ ] Careless mistakes from a careful person
  [ ] Lunch at the desk; headphones all day; absent from the huddle
  [ ] Stopped asking questions, suggesting fixes, or raising problems
  [ ] First in, last out, and defensive when it is mentioned
  Seen in the tickets
  [ ] Resolution notes have shortened over the month
  [ ] Reopen rate on their tickets rising while the close count holds
  [ ] Activity on tickets in the evening or at the weekend, newly
  [ ] Leave carried over and not booked
  Ticks this month: ____   Last month: ____
  A named cause (outage, leave cover, project): ______________   Ended on: ________
  Three or more, or three in each of two months: lighten the load this week,
  then hold the conversation.   Done on: ________

Nadia ran the manager half for Oskar on the Friday and ticked five. She took him off the phone for the following week and moved the laptop refresh he had been doing in the evenings to a colleague. On the Tuesday she asked him what had changed about the work since the summer. The answer took forty minutes and was mostly about the warehouse scanners and a project nobody had told the desk was starting. None of it was about Oskar. It rarely is.

Frequently Asked Questions