Why IT Has a Brand Whether It Wants One or Not

Tuesday, 10:40, the second-floor kitchen at Meridian Parts. Dana runs the four-person desk and is waiting for the kettle. Behind her, Ray from purchasing is telling a new starter how things work. "If your laptop does anything weird, ask Lena in accounts first. She knows most of it. IT are fine, but you'll get a ticket number and then it'll be Thursday." The new starter nods and writes down Lena's name. Dana takes her tea back to her desk. The queue shows nine open tickets, none older than two days, and a satisfaction score that has been comfortably high for a year. None of that was in the kitchen.

A brand, for an internal IT department, is the sentence people say about it when nobody from IT is in the room. It is not a logo, a slogan or a colour scheme, and it is not the mission statement on the intranet. It is "it'll be Thursday", or "they're great if you can get hold of them", or "don't bother, just ask Lena", repeated by people who have never read a service level and never will. This article is part of our IT's Internal Brand series, which is about taking the pen back. The desk cannot stop people writing that sentence, but it can change what the sentence says.

It covers what a brand is when you are an IT department and why you have one already. Next come the six things people say in the kitchen and what each is really about. Then it covers where the cost-centre reputation comes from and why the desk cannot opt out. Next is the brand audit, done by asking five people five questions. Then it covers how to read what you heard, what you can change and what you cannot. Finally come a short war story and the reputation audit sheet to copy, in that order.

What a Brand Is, When You Are an IT Department

A brand is formed by other people from the moments they can see, and the desk gets no vote. A requester experiences three things from a ticket: the wait, the reply and the fix. From those three, and from what colleagues told them before they asked, they build an opinion. The opinion is short, because nobody carries a long opinion about an internal department. It is sticky, because people repeat it to new starters, who then experience the desk through it. The new starter at Meridian will wait a day for a ticket to be touched and think "Thursday, as Ray said", even if it is Wednesday morning.

The desk already has one, which is the part people find hardest to accept. There is a temptation to say "we don't do branding, we fix computers". It is a fair thing to say, but it does not stop the sentence being said in the kitchen. It only means the desk is not in the room when it is written. A department that does not shape its reputation has not avoided having one. It has outsourced the job to whoever had the worst week.

The useful thing about a brand is that it is made of specific moments, and specific moments can be changed. "They talk to you like you're stupid" is about one reply, or a style of reply, and the style can be changed. "It'll be Thursday" is about one wait, or the memory of one, and the wait can be shortened or at least explained. Treating the brand as a vague feeling makes it unfixable. Treating it as a list of sentences, each traceable to a thing the desk does, makes it a backlog. Desks are good at backlogs.

What People Say in the Kitchen

Most of what gets said about an internal IT department falls into about six sentences. Each one points at a different part of the desk. The table below lists the ones I have heard most often, in roughly every organisation I have worked in or visited. It shows what the sentence is really about and where in this library the fix lives. Two are compliments. They are worth reading as closely as the other four, because a compliment tells you what to protect.

Notice that none of the six is about the thing the desk is proudest of. Nobody in a kitchen has ever said "their resolution time is excellent" or "I admire their patching cadence". People talk about how it felt to ask, how long they waited, and whether the reply sounded like a person. The desk measures the fix. The kitchen measures the experience, which is the point made at length in How Support Feels Versus How Fast It Closes. The brand is written in the kitchen's units, not the desk's.

Notice also that four of the six are about moments that happen before the fix: the wait, the no, the reply, the way in. A desk can be technically excellent and have a poor brand, because its excellence arrives after the requester has already formed an opinion. Dana's desk was fixing things inside two days. Ray's sentence was about the twenty-four hours before anyone replied.

Where the Cost-Centre Reputation Comes From

A cost centre is an accounting term for a part of the organisation that spends money and does not directly bring any in. It is a neutral label on a budget sheet. It becomes a reputation when the organisation can see what IT costs and cannot see what IT does. The budget line is visible every month. The work it pays for is visible only when it fails. Over a few years, that asymmetry produces a story: IT is a cost, IT is slow, IT says no. The story is not a lie. It is a description of the only evidence the organisation was ever shown.

The first source of the story is invisible work. Most of what a desk and its administrators do produces no ticket and no visible event. Examples are the patches applied, the certificates renewed before they expired, the backups tested, and the laptop model quietly retired because it kept failing. When it works, nothing happens, and nothing happening is not news. The desk at Meridian prevented perhaps forty small outages last quarter and could not name one, because they did not occur. Making the Invisible Work Visible is the next article in this series and is about that half of the problem.

The second source is visible failure. The outage, the printer that took two days, the laptop that arrived a week after the new starter, the ticket that went quiet. Each one is seen by many people, discussed, and remembered, because a failure has a story and a success does not. One bad week in a year of good ones is what gets repeated. That is not because people are unfair but because it is the only week that gave them something to say. Failures are also the moments where the brand can be rewritten fastest, which is the subject of Service Recovery Moments. For now it is enough to know that the failures are where the current story was written.

The third source is the no. IT is, for most people, the department that tells them what they cannot have: the software they wanted, the admin rights, the personal device on the network, the exception. Every one of those refusals may be correct, and the sum of them is still a reputation for refusing. The craft of declining without leaving a wall, and of offering the alternative, lives in Saying No Professionally. The brand point is simpler: each no is remembered as a no, however well-reasoned, unless something was offered in its place.

Underneath all three is the money. The organisation sees the IT budget as a line and the desk as the people who spend it. Nothing on the line says "forty outages prevented" or "nine hours a week given back to finance". The arithmetic that turns the desk's work into hours the organisation can count is in The Economics of Support. This series comes back to the story the arithmetic supports in Escaping the Cost-Centre Story. The desk did not choose to be a cost centre. It was given the label by a spreadsheet, and the spreadsheet has never once attended a kitchen.

Why the Desk Cannot Opt Out

The brand is formed from whatever evidence is available. In the absence of evidence from the desk, the evidence is the failures. That is the whole mechanism, and it is why "we don't do branding" is not a neutral position. A desk that publishes nothing about its own work has not stayed out of the conversation. It has handed the conversation the only material it had, which was the outage and the two-day printer. Silence is not modesty. It is a vote for the other side's version.

The second reason is that a brand compounds. A new starter who was told "it'll be Thursday" waits before raising a ticket and raises it late. They experience the desk as slow because their own deadline was already close. They then tell the next new starter. A desk with a poor reputation receives worse tickets, later, from people who expected little, and the tickets confirm the reputation. The reverse is also true, and it is the only cheerful sentence in this section. A desk people trust gets told about problems early, when they are small, which makes the desk look better still.

The third reason is that the brand decides what the desk is allowed to do next. The headcount case, the tooling case, the request for a protected hour of prevention each week: all of them are heard by people who already have a sentence about IT in their heads. The sentence is the first thing the case has to get past. I have watched a well-evidenced request for a second technician fail in a meeting because the director's own laptop ticket had gone quiet the previous month. The evidence was fine. The brand voted first.

The Brand Audit: Five People, Five Questions

The brand audit is a structured way of finding out what the sentences are. It is done by asking five people five questions, in person, for about ten minutes each. It includes writing down what they say in their own words. It is not a survey. Surveys get the score, and the score is covered properly in Beyond the Score. The audit gets the sentence, which the score cannot carry. Five is enough to hear the pattern and few enough to do in a week. Twenty would be better and would never happen.

Choose the five deliberately, because five friends of the desk will tell you the desk is fine. One person from the department that raises the fewest tickets for its size, since a quiet department usually has another route. One manager who has recently asked for something and been declined. One person who started in the last three months, who carries the version of the brand they were handed on day one. One person who has been there longest, who remembers the desk before you. And one person who has complained, in a ticket or out loud, in the last year. If a name makes you wince, that is the name.

Ask the five questions in order and do not defend anything. The first is "When you last needed IT help, what did you do first?" This finds the shadow channels and the kitchen advice. The honest answer is often a person's name rather than "raised a ticket". The second is "What do you expect to happen after you raise a ticket?" This finds the expected wait and the expected silence. The third is "Tell me about a time IT did something well". This finds what to protect and is, for some people, a surprisingly long pause. The fourth is "What is the one thing you would change?" The question is singular, because one thing is a priority and a list is a complaint. The fifth is "If you were describing IT to a new colleague in one sentence, what would you say?" The answer is the brand, verbatim, from the person who will actually say it.

Write the answers down as they are said, in the person's words, and resist every urge to correct them. When Ray says "it'll be Thursday" and the desk's figures say otherwise, Ray is still right about what he experienced and what he tells people. An audit that argues with its subjects learns nothing. Say thank you, say what you will do with it, and leave. The explaining comes later, and it comes in the form of a better desk rather than a better argument. (You will want to explain. Do not.)

Ten minutes a person, five people, one week, and a page of sentences at the end of it. The whole exercise costs the desk less than one afternoon and gives it the only thing it did not have, which is the outside view. Most desks have never done it, because the dashboard already looked fine and nobody wants to go looking for a bad sentence. The sentence is there regardless. The audit only decides whether the desk hears it first or the new starter does.

Reading What You Heard

Lay the five pages side by side and look for the sentence that appears more than once, in different words. Three people who mention waiting are describing the first reply, not three unrelated problems. Two people who mention a specific technician by name, kindly, are describing a shadow channel and a compliment at once. One person who says the desk is wonderful and four who hesitate are describing a desk that is wonderful to some. The pattern across five is the brand; any single answer is one person's Tuesday.

Sort what you heard into four piles: speed, tone, scope and visibility. Speed is the wait and the silence during it. Tone is how the replies read. Scope is the no, and whether it came with an alternative. Visibility is whether anyone knew what the desk had done, or did at all. Nearly every kitchen sentence lands in one pile. Each pile has an owner in this library and in the rest of this series. The wait belongs to expectations and the first reply, and tone to the language of the desk. Scope belongs to saying no and the written scope, and visibility to the monthly note.

Then compare the piles with what the desk measures, and expect a gap. Dana's dashboard measured resolution time and satisfaction among people who answered the survey. The kitchen measured the hours before the first human reply and the experience of the people who had stopped raising tickets. Both were accurate. They were answering different questions, and the kitchen's question was the one that decided the brand. The gap between the two is the audit's most useful output. It says what the desk has been optimising that nobody outside it can see, and what nobody inside it has been counting.

The sentence that hurts most is usually the most useful one. It is worth saying so to the team before they read the pages. "They talk to you like you're stupid" is painful to hear about replies you wrote with care. It is also the most fixable sentence in the set, because it is about a style and a style can be changed in a month. Treat each sentence as a ticket: it has a cause, an owner and a fix. The team that takes the audit personally will defend the desk. The team that takes it as a backlog will improve it.

What You Can Change and What You Cannot

Be honest with yourself about which sentences the desk controls. The wait before the first reply, the words in that reply, the alternative offered with a no, the visibility of the work done and the handling of the next failure are all the desk's to change. The rest of this series is about those five. Each has a mechanism elsewhere in the library, from the first reply within the hour to the handling of the person who is already angry. The mechanism is the fix; this series only says why the fix matters to the brand.

Some sentences the desk does not control, and it should say so rather than promise otherwise. "Everything takes a week" may be true because the desk is two people for four hundred staff. That is a staffing decision made above the desk, and the honest route is the headcount case with evidence rather than a cheerful poster. "They always say no" may be true because the organisation's rules are strict, and the desk enforces them. The alternative and the reason are the desk's; the rule is not. A brand effort that promises what the desk cannot deliver creates one more sentence: "they said it would get better". Do not add that one to the list.

The honest position is the one that wins over time: the desk says what it is changing, changes it, and shows the change. If you run QuerySolv, the event history on every ticket is a help here. When someone says "my ticket went quiet for a week", the desk can look at exactly what happened and when. It can answer with the record rather than with a feeling. The same is true of any tool that keeps a full history. Some things the record will confirm. Some it will not, and the desk gets to say "you're right, and here is what we have changed". That sentence, said in a kitchen, does more for a brand than any amount of being correct.

Finally, give the audit a date to be repeated. A brand is not fixed once; it drifts with every bad week and every new starter. The five questions asked again in a year, to five different people, tell you whether the sentences have changed. The repeat is the subject of Measuring the Brand, which turns this one-off audit into a scorecard. For now, do it once, this month, before the next failure writes the next line.

A Short War Story: The Thursday Desk at Tollgate Foods

Marta took over the three-person desk at Tollgate Foods and, in her second week, did the five-person audit. Four of the five said some version of "it'll be next week" before she had finished asking the second question. The desk's own figures said most tickets were resolved inside a day, which was true. The audit found the three tickets that had built the sentence. A payroll printer had waited nine working days for a part. A laptop for a new starter in finance had taken eleven days through procurement. And a request for a second screen had gone quiet and been closed without a reply. The cost showed up when Marta checked the asset list against the finance team's expense claims and found eleven laptops bought on personal cards over the previous year. None of them were managed. One of them was already lost with a spreadsheet of supplier bank details on it. Nobody in finance had been trying to bypass IT. They had simply believed, from three tickets and a sentence, that asking would take a fortnight. A brand is written from the worst ticket people can remember, not from the average one. Marta's average had never stood a chance against a payroll printer.

The Reputation Audit

The sheet below is the audit as a one-page form: who to ask, what to ask, where to write it down and how to sort it afterwards. Fill one sheet per person during the conversation, then use the sorting section at the bottom once all five are done. Keep the sheets; the repeat audit in a year is compared against them. The sentences in the last box are the measure of whether anything changed.

IT REPUTATION AUDIT — ONE SHEET PER PERSON
Date: ____________   Asked by: ______________   Person: ______________ (role: ______________)

WHO (tick the one this person represents; five sheets cover all five)
  [ ] the quietest department for its size      [ ] a manager recently declined
  [ ] a starter in the last three months        [ ] the longest-serving colleague
  [ ] someone who complained in the last year

THE FIVE QUESTIONS (write the answer in their words; do not explain or defend)
1. When you last needed IT help, what did you do first?
   ______________________________________________________________________
2. What do you expect to happen after you raise a ticket?
   ______________________________________________________________________
3. Tell me about a time IT did something well.
   ______________________________________________________________________
4. What is the one thing you would change?
   ______________________________________________________________________
5. Describing IT to a new colleague in one sentence, what would you say?
   ______________________________________________________________________

AFTER ALL FIVE (one summary for the set)
  Sentences heard more than once: ________________________________________
  Pile:  speed ____   tone ____   scope ____   visibility ____  (count of mentions)
  What to protect (from question 3): ______________________________________
  Gap between what the desk measures and what people said: ________________
  The desk controls: _______________________________________________________
  The desk does not control (and will say so): _____________________________
  First change, owner and date: _____________________________________________
  Repeat audit due: ____________   Sheets kept at: ______________________

Dana did the audit at Meridian Parts the week after the kitchen, starting with Ray. He was surprised to be asked and gave her a better answer than the one she had overheard. The ticket itself had been fine; the day before anyone replied had not. Four of five said something about that first day. She changed one thing: a human reply to every new ticket within the hour saying who had it and when they would be back. She did nothing else for a quarter. Ray's sentence, when she next heard it, was "they get back to you pretty fast now". It was not a slogan. Nobody in a kitchen has ever repeated a slogan.

Frequently Asked Questions