The Classics Every Desk Has: Six Stories, Six Lessons

Friday, 15:30, at Tollgate Foods. Ben is three weeks into his first desk job. He has just closed a ticket in which a label printer in the packing office turned out to be unplugged at the wall. He is faintly embarrassed to have driven across the site for it. Ravi, who has run the desk for nine years, reads the resolution note and says, without unkindness, "That's one. You'll have the full set by the end of the year." Ben asks what the full set is. Ravi counts them on his fingers: the plug, the cup holder, the coffee, and the printer that was off. Then come the password that was the word password and the monitor turned down. Every desk has them. Every desk thinks it is the only one.

A classic is a war story so common that every desk owns a version of it. It has the same shape, the same cheap cause behind the same alarming symptom, and the same lesson. The versions differ only in the names and the make of the printer. This article is part of our Helpdesk War Stories & the Ticket Hall of Fame series. Like every story in the series these six are fictional. The organisations are invented and the people have first names and no existence. What is not fictional is that you will meet all six, and that in every one of them the person who asked for help did something entirely reasonable.

It covers why every desk has the same six stories, then the six themselves, a paragraph each with the lesson under it. Next comes how to tell a classic without turning the user into the joke, followed by the classics as a training set for a new technician. Then comes a short war story, which in an article made of war stories feels like one for the road. We finish with the classics list with lessons, to copy.

Why Every Desk Has the Same Six Stories

The classics recur because the same cheap causes hide behind the same expensive symptoms, and because people describe symptoms, not causes. A screen with the brightness at zero and a screen with a dead panel look identical to the person sitting in front of them. "My monitor is dead" is an honest, accurate report of what they can see. The desk is the party with the information that would separate the two. And the classics are the stories of the desk not using it. That is why the lesson in each one points at the technician, never at the requester.

The shape is always the same. A dramatic symptom, worded plainly. An assumption on the desk that this one is the serious kind. A check is skipped, a spare dispatched or a reset issued. Then comes the twist, which is small, physical and in retrospect the first thing anyone should have looked at. The laugh is in the distance between the effort spent and the size of the cause. And the laugh is at the desk, because the desk had the method and did not use it. Six stories, three lessons, and a van that did not need to leave the car park.

The three lessons are the cheapest check first, ask what changed, and verify before you reset. The first two belong to the diagnostic order, which is the method the classics exist to teach. The third belongs to verifying identity before a reset. Every classic below ends by naming its lesson and pointing at the article that owns it, which is the one rule this series does not bend.

The Plug

At Acme, Margaret, the finance director, raised ticket 2217 on a Tuesday morning: "Monitor dead since Monday, nothing on screen, tried turning it off and on." The desk, reading "finance director" and "dead", escalated it twice in a morning. It sent Sam across the building with a spare monitor from the stores, which he connected. The spare also showed nothing, because the socket it was plugged into was the one Rosa the cleaner used for the vacuum every evening. She had been putting the vacuum's plug back in the socket instead of the monitor's since the previous Thursday. Sam found the monitor's plug on the floor, put it back, labelled the socket, and asked facilities for a second one. Margaret had reported exactly what she saw, and Rosa had done her job with the only free socket in the room. The spare monitor went back to the stores having been out for forty minutes. The lesson is that the cheapest check comes first, before the spare and before the van. It lives in the diagnostic order.

The Tray That Was a Cup Holder

At Tollgate Foods, Greta in the packing office had a desktop tower on a shelf under her desk at knee height. When her knee caught the button on the front of it a tray slid out, flat and steady, at precisely the height of a shelf. She put her mug on it, as anyone would put a mug on a shelf that had just appeared, and the tray snapped off. She rang the desk within a minute and told Ben exactly what had happened, including the part about the mug. She asked whether she had broken something important. Ben swapped the drive for one from the spares shelf in ten minutes. He moved the tower off the floor onto the desk where the button could not be kneed, and thanked her for saying what happened. Without her saying what happened, he would have been diagnosing a drive fault on a machine that had no fault. The lesson is to ask what happened just before, and to make it easy to answer honestly. And it lives in the diagnostic order, under the question that pays.

The Coffee in the Keyboard

At Stonebridge Insurance, Dev in claims raised a ticket at 10:46 that read: "Spilt coffee across the laptop keyboard at about 10:40. Turned it off straight away, unplugged it, it's upside down on a towel. Keys were typing rows of t before I switched it off." Hannah on the desk read it, took a spare laptop off the shelf, and signed Dev into it at his desk. Hannah had him working by 11:05 while the original went to the bench to dry out and, eventually, to the repair vendor. The diagnosis took no time at all because Dev had done it in his ticket. And the repair took no time at all because the spare was on the shelf. The desk had spent two hours a month earlier on a laptop whose owner had said only "the keyboard's gone funny". That had also been coffee. The lesson is that an honest report and a spare on the shelf beat any diagnosis. And it lives in the loaner and spares strategy, with the thank-you in the first reply.

The Printer That Was Off

At Northgate Retail's Harbor Street store, Nadia the store manager raised a ticket saying the stockroom label printer was dead. She added that she had already checked the power button on the printer and it was on. She had been asked this before and did not care to be asked again. Leah on the desk believed her, because it was true, and asked a different question: "Has anything changed in the stockroom this week?" A new chiller cabinet had been installed on the Monday. Facilities had switched off the wall socket the printer shared with the old one and never switched it back on. The printer's own button was on, lit, and connected to nothing. Nadia flipped the wall switch while still on the phone, and the printer woke up with a sigh that both of them heard. The lesson is that "is it on" is a chain from the wall to the device, not a single button. The lesson also says that what changed is usually a person. The lesson lives in the print triage flow.

The Password That Was the Word Password

At Bluewater Bank, Marcus started in lending on a Monday and was given his sign-in by his manager. The manager had set the temporary password to the word password and told him to change it when he had a moment. The moment did not arrive. Five weeks later a policy change at the bank began enforcing complexity rules on the next sign-in. That locked him out at 08:50 with a queue of customers waiting. He phoned the desk, said who he was and what his password was, and asked Dana to reset it. Dana, following the desk's standard, verified him first, exactly as she would have for anyone, before she touched the account. Only then did she reset it to a one-time password that expired at his first sign-in. She then looked at the other starters from the same month and found eleven more accounts in the same state. They were set up by the same hurried process. She reset each of them the same way with a note to each manager. Marcus had done exactly what he was told; the process had told him the wrong thing. The lesson is to verify the person before you touch the account, every time, and never to let a temporary password outlive the first sign-in. The first half lives in verifying identity before a reset and the second in the reset done properly.

The Monitor Turned Down

At Harbourview Clinic, the reception screen was reported dead on three Monday mornings in a row. Each time it had recovered by the time a technician arrived, which is the kind of pattern that makes a desk start muttering about cables. On the fourth Monday Jonah asked Imogen at reception a question that had not been asked: "Who else uses this desk?" The weekend locum, Farah, covered the Saturday night clinic from the same chair. She turned the screen's brightness to its lowest setting because the waiting room lights were dimmed overnight, and left it there. So on Monday morning the screen was on, working and showing an image nobody could see. Jonah turned the brightness up with the button on the screen's edge, put a small note on the desk, and the Monday tickets stopped. Farah had set the screen for the room she worked in, which was the sensible thing to do. The lesson is to ask what changed, including who, and it lives in the diagnostic order.

Telling a Classic Without a Villain

The six stories above have a feature in common that the usual telling leaves out, which is that every person who asked for help behaved well. Margaret reported what she saw. Greta told the truth about the mug within a minute. Dev wrote the best ticket the desk received that month. Nadia had checked the button and said so. Marcus did what his manager told him. Farah set the screen for the room she was in. The technicians, meanwhile, skipped a check, sent a van, or assumed the serious cause, and the stories are about those choices. A classic told with the user as the fool has been edited to remove the desk's part in it. The edit is the only fictional thing about it.

The rewrite is usually one sentence, and the sentence is about what the person did right. "She rang within a minute and told us exactly what happened" is the rewrite. It turns the cup holder from a joke about Greta into a story about an honest report. "He had already checked the button, so we asked a different question" is the rewrite. It turns the printer from a joke about Nadia into a story about the chain from the wall. The laugh survives the rewrite intact, because the laugh was never about the person; it was about a van sent for a plug. There is a whole corner of the industry devoted to collecting foolish-user stories. And the desks that enjoy it most are the ones whose users have quietly stopped calling.

The classics also make good reading for users, if the lesson is turned round. "Before you call: four things to check" is the plug, the printer and the monitor rewritten as a courtesy, with no hint of "you should have". A user who reads it is a user who will check the wall socket and say so in the ticket. If you run QuerySolv, a knowledge base article can be made visible to everyone rather than only to the desk. That way, the before-you-call list sits where the requester is already looking. In any tool the point is the same: the classics are lessons for the desk first. Once the desk has learned them, they can be offered to everyone else without a trace of blame.

The Classics as a Training Set

Six stories carrying three lessons is a training set that fits in a lunch hour. A new technician should hear all six in their first week from someone who was there for the desk's own versions. The order matters a little: the plug, the printer and the monitor come first. They teach the cheapest check, and the technician will meet one of them in their first month. The cup holder and the coffee come next, because they teach the question that pays and the thank-you for an honest answer. The password comes last, because it teaches a rule that must never bend and the reason it must not. The structured version of this induction is in the new technician's first thirty days; the stories are what the structure is remembered by.

Then wait, because the new technician will produce their own. Ben's label printer was his first, and by the end of the year he had the full set. It included a monitor turned down by a night porter and a password that was the name of the company. Each one goes on the page beside the classic it belongs to, with its ticket number. And each one is told at the huddle by the person who closed it. A technician who tells their own plug story in front of the desk has learned the lesson twice and taught it once. They will check the socket for the rest of their career. The classics are not a list to memorise. They are a set of experiences the desk arranges to have in a safe order.

The table in the template below is the written form. And a desk starting its stories page can copy it as the first entry and replace the fictional columns with its own. The fictional versions are a placeholder. The real ones will be funnier, because they will have happened to you.

A Short War Story: The Forty-Minute Drive at Ashgrove Housing

Ashgrove Housing ran a desk at head office and supported six neighbourhood offices spread across a city, the furthest a forty-minute drive away. The furthest office rang on a Thursday to say the manager's monitor had died. A technician called Kasia booked a van, signed out a spare monitor and drove over. Kasia went because the office had no technical staff, and "the screen is completely dead" sounded like exactly what it said. The monitor was plugged into a six-way power strip under the desk. The strip's own switch had been turned off by the office's new portable heater. The heater had been plugged into the same strip that morning and had tripped nothing. But it had been placed with one foot on the rocker switch. Kasia moved the heater, pressed the switch, and drove back, the spare monitor unused. Kasia had spent most of a working day and a tank of fuel on a check that would have taken ninety seconds on the phone. The desk added one line to its phone script for the neighbourhood offices, "has anything new been plugged in near the desk this week?" And the next three remote monitor tickets were closed by phone in under five minutes each. This article has told six war stories already. And the format asks for one more, which is fitting, because the seventh is the one that happens to you. The lesson is that the cheapest check happens on the phone before the van leaves, and it lives in the diagnostic order.

The Classics List With Lessons

The table is the stories page's first entry. It lists the six classics, the symptom as it was reported, the cause, and the lesson in a sentence. It also lists the article in this library that owns the rule. Copy it, replace the fictional columns with your own versions as they happen, and keep the ticket numbers. The ticket is where the facts live and the table is where the lesson does. Beneath it is the six-question checklist that the classics add up to, for the moment before anyone books a van.

The six questions below are the classics turned into a script, for the phone, before any spare is signed out. They take under two minutes to ask and are the difference between the forty-minute drive and the ninety-second fix. Ask them in order, write the answers in the ticket, and ask the last one even when the first five have found nothing.

• Is the device plugged in at both ends, and is the wall socket or power strip switched on?
• Is there a light on the device, and is it the colour it usually is?
• What changed near the desk this week: anything new plugged in, moved, installed or cleaned?
• Who else uses this desk, chair or machine, including evenings and weekends?
• What happened in the minute before it stopped, and is there anything spilt, dropped or knocked?
• If this is an account rather than a device: have I verified the person before I touch anything?

Ben kept the six questions on a card by his phone for a year, by which time he no longer needed the card. Ravi had been right about the full set. He had not mentioned what the seventh classic, the one every desk adds for itself, would turn out to be. It would turn out to be a story Ben told at the huddle about a van he did not, in the end, book.

Frequently Asked Questions