A weekly help desk metrics meeting earns its hour when it ends with one decision and one owner, and fails when it ends with everyone having seen the numbers. Four charts are enough to get there: ticket volume, backlog age, response time and resolution time. Anything beyond those four is a different meeting. I used to think more charts meant a better review. They just meant a longer one.
I ran this review weekly at a UK platform business in the late 2000s. We printed the pack the afternoon before and stuck the charts to a whiteboard, and the useful part was always the marker pen: whatever got written under a chart was what the week was about. A chart with nothing written under it hadn’t earned its place. The version below is the cleaned-up agenda, with the Excel behind it, laid out so you can rebuild the sheet from scratch.
What does a one-hour metrics meeting look like?
The hour is split into five blocks, and the times are hard limits. This is an illustrative agenda, so adjust the minutes to your team, but keep the shape. The shape matters more than the minutes because it forces the meeting to start with accountability and finish with a decision. Everything in between is there to feed that decision.
| Minutes | Block | Who leads |
|---|---|---|
| 0-5 | Last week’s decision: did it happen? | Meeting owner |
| 5-25 | The four charts, about five minutes each | A different shift lead per chart |
| 25-45 | The one question the charts raise | Whoever owns that queue |
| 45-55 | The decision, written on the board | Meeting owner |
| 55-60 | Actions, owners, dates | Note-taker |
Rotating the presenter does more than share the load. Call Centre Helper’s advice on rotating who presents the performance data, with the manager adding commentary afterwards, matches what I saw. A shift lead who has to explain a chart in front of peers checks it first. Bad data gets caught the afternoon before rather than ten minutes into the meeting. It also means the manager stops being the only person in the room who understands the numbers, which is a fragile place for any team to be.
The first five minutes matter most and get skipped most. If last week’s decision was “move two people to the evening shift” and nobody can say whether it happened, the rest of the hour is theatre. Ask the question out loud, every week, before a single chart goes up. If the answer is no, find out why before you make a new decision on top of an old one. A team that never closes last week’s loop learns that decisions in this room don’t stick.
Which four charts earn a place on the wall?
Volume tells you what came in. Backlog age tells you what you haven’t dealt with. Response time tells you how long people waited to hear from you, and resolution time tells you how long until it was fixed. Together they show a queue from both ends, which is why I stopped adding a fifth. Every fifth chart I tried turned out to be one of these four cut a different way.
The one most teams get wrong is backlog age. A backlog count of 10 tickets sounds fine, but it hides the difference between ten tickets raised this morning and ten raised three weeks ago. Age is what your customers feel, and it’s the chart that usually produces the week’s decision. The ticket categories you pick decide whether you can split these charts by type of work, so settle that taxonomy first or every chart will argue with the last. A count tells you how busy you are. Age tells you who’s been forgotten.
Keep response and resolution on the same page, because they pull against each other. Pick the response measure deliberately too: average speed of answer and service level tell different stories, and the chart should show only one of them. Pushing a fast first reply is easy, because an acknowledgement that says nothing will do it. If response time improves while resolution time slips, you’ve bought a number, not a service. Put the two lines on one chart with the same weeks along the bottom, and that trade-off is visible from the back of the room.
Volume is the chart people want to skip, because it rarely moves the decision on its own. Keep it anyway. It’s the context that tells you whether a slower resolution week was the team getting worse or the queue getting bigger, and those need very different responses.
How do you build the backlog-age chart in Excel?
Use one workbook with one sheet, called Tickets, refreshed from your help desk export each Monday. Row 1 holds the headings. Column A is the ticket ID, column B is the date opened, column C is the date closed (left blank while the ticket is still open), and column D is the age you calculate. Each ticket gets its own row from row 2 down, and the formulas below assume up to row 500, which is room for 499 tickets. If your export is bigger, change 500 to a bigger number everywhere it appears. I kept a simple weekly tracking sheet for my other KPIs, and this one follows the same idea: one row per item, one calculated column, one small summary table.
In D2 type =IF(C2="",TODAY()-B2,"") and fill it down to D500. Read it left to right. IF asks a question, here “is C2 empty?”. If it is, the ticket is still open, so TODAY() minus the open date in B2 gives its age in days. If C2 has a date, the ticket is closed and the formula returns “”, an empty piece of text, so closed tickets carry no age at all. If your export includes times as well as dates, wrap it as =IF(C2="",INT(TODAY()-B2),""), because INT drops the fraction of a day and keeps the buckets clean.
Next, build a small summary table on the same sheet in columns F and G. Put the labels in F1 to F5: “Age bucket”, “0-2 days”, “3-7 days”, “8-14 days” and “15+ days”. Put “Tickets” in G1, and the counts go in G2 to G5. In G2 type =COUNTIFS($D$2:$D$500,">=0",$D$2:$D$500,"<=2"). COUNTIFS counts the rows that pass every test you give it, and here there are two tests on the same column: age of at least 0, and age of no more than 2. The dollar signs lock the range so it doesn’t slide when you copy the formula down. G3 is the same formula with 3 and 7, G4 with 8 and 14, and G5 is simply =COUNTIF($D$2:$D$500,">=15"), one test for the oldest bucket.
Finally, put “Median age” in F7 and =MEDIAN($D$2:$D$500) in G7, then “Average age” in F8 and =AVERAGE($D$2:$D$500) in G8. Both functions skip the empty text that closed tickets return, so they only see open tickets. COUNTIFS arrived in Excel 2007. On Excel 2003, use =SUMPRODUCT(ISNUMBER($D$2:$D$500)*($D$2:$D$500>=0)*($D$2:$D$500<=2)) instead. Each bracket gives a TRUE or FALSE per row, multiplying them turns those into 1s and 0s, and SUMPRODUCT adds them up. ISNUMBER matters because Excel treats text as bigger than any number, so without it the empty cells would sneak into a “15 or more” count. Chart G2 to G5 as a bar chart and that’s the backlog-age chart. The same formulas work unchanged in current Excel and in Google Sheets.

What does a worked example tell you?
Here is a small example, illustrative only, so you can check your own sheet against it. Ten open tickets sit in rows 2 to 11 with ages in column D of 0, 1, 1, 2, 3, 5, 6, 9, 14 and 21 days. G2 counts the ages from 0 to 2, which are 0, 1, 1 and 2, so it shows 4. G3 counts 3 to 7, which are 3, 5 and 6, so it shows 3. G4 counts 8 to 14, which are 9 and 14, so it shows 2, and G5 counts the single 21-day ticket, so it shows 1. Add them up as a check: 4 + 3 + 2 + 1 = 10, which matches the ten open tickets.
Now the two averages. The ages add up to 0 + 1 + 1 + 2 + 3 + 5 + 6 + 9 + 14 + 21 = 62 days, and 62 / 10 = 6.2, so G8 shows an average age of 6.2 days. The median works differently. With the ten ages in order, it’s the midpoint between the fifth and sixth values, which are 3 and 5, so (3 + 5) / 2 = 4.0, and G7 shows 4.0 days. That gap between 6.2 and 4.0 is the signal. One 21-day ticket drags the average up by more than two days while the typical ticket is much younger.
Show both numbers side by side, on purpose. The average on its own makes the whole queue look slow, and the median on its own hides the ticket that’s actually hurting someone. Together they tell you the queue is mostly fine and one customer isn’t. That’s a far more useful thing to walk into the room with than “average age is up”. Then ask about the oldest ticket by name. Somebody owns that 21-day ticket, and the meeting should leave knowing who and what happens next.
What gets dropped when the meeting overruns?
Decide before the meeting starts, not during it. When the clock hits 25 minutes and the charts aren’t done, cut in this order: the resolution chart discussion first (read the number, skip the debate), then response time, then volume. Backlog age and the decision block are never cut. If a chart eats its five minutes and there’s still a question, park the question in a log and give it to the owner. The log gets read out in next week’s first five minutes, so nothing parked is lost.
Roger Schwarz makes the same point in his Harvard Business Review piece on how to design an agenda for an effective meeting: a good agenda divides the time sensibly between topics and makes it clear when a discussion is finished. A cut order written down in advance does both. Nobody has to argue in the moment about what to drop, because the argument already happened when the agenda was set. That saves more time than any facilitator can.
Two other rules save more time than any agenda. Nobody gets a chart they didn’t ask for, which means a new chart has to replace an old one. And anything that needs more than two minutes of discussion leaves the room as an action for a smaller group. The cost is easy to work out. Eight people for one hour is 8 x 1 = 8 person-hours a week, and over a year that’s 8 x 52 = 416 person-hours. Eight people debating one queue’s workflow burns that time on a problem two of them could have solved over coffee.
How do you know the meeting is working?
Count decisions, not attendance. Photograph the board at the end of every meeting, and after eight weeks lay the photos side by side. If at least six of the eight show a decision with a name and a date next to it, that’s 6 / 8 = 0.75, or 75%, and the format is paying for itself. If they show charts and no writing, shrink the meeting to thirty minutes and make the decision block mandatory. A shorter meeting that decides something beats a longer one that doesn’t, every time.
Watch what happens to the 15+ bucket over the same eight weeks too. If the meeting works, that bar shrinks, because every week someone is asked about the oldest ticket by name and nobody enjoys being asked twice. The test I’d keep is simple. Take the oldest ticket in the backlog and ask who in the room would be surprised to hear its age. If the answer is nobody, the pack is doing its job.
Which of the four charts produces most of the decisions in your weekly review? Tell me in the comments.
Hutch Morzaria is a Director-level CX and Support Leadership professional with 19 years of experience building global support organizations across SaaS, Fintech, and enterprise technology. He has hired dozens of support and CX leaders across his career and holds ITIL Expert certification across V3 and V4.


