Reporting to Leadership
The monthly report was nine pages, produced on the first Friday, and it opened with a table of tickets by category by week. The managing director read the first paragraph on the first month, the headline on the second, and the subject line thereafter. In month four the desk had its worst backlog in two years. The report said so, on page six, in a table. Nobody noticed until a department head complained in a meeting. The report was accurate, complete and unread. A report that is not read is a diary. The desk needed a page.
This series is about the page. It covers the monthly report leadership will actually read, which is five numbers, three sentences and one ask. It covers translating tickets into business language, so that a backlog becomes people waiting and an outage becomes hours lost. It covers the numbers to show and the numbers to keep, because per-agent figures belong inside the team. Then come charts that help and charts that hide. It covers the quarterly review, which is about trends rather than months. And it covers what to do when the numbers are bad, which is to say so first and say why second. Leadership does not want to know about the desk. It wants to know whether anything needs deciding. Tell it that.
Articles in This Series
- The Monthly Report They Will Actually Read
One page, five numbers, three sentences, one ask; and what to leave out. Covers the report that takes fifteen minutes to produce, and the one-page report. - Translating Tickets Into Business Language
Time lost, people blocked, risk, cost in hours; the translation table from desk words to leadership words. - The Numbers to Show and the Numbers to Keep
What leadership needs versus what the desk needs, the per-agent numbers that stay inside the team, and the audience matrix. - Charts That Help and Charts That Hide the Answer
Created versus closed, backlog by age, a trend line; the pie chart, the dashboard screenshot, the chart with no date; one chart per question; and the chart choice table. - The Quarterly Review: Trends, Not Months
What changed over the quarter, what the desk did, what it needs, the three trends worth a page, and the quarterly review page. - When the Numbers Are Bad: Reporting a Poor Month Honestly
Honesty first, the cause, the plan, no spin, the credibility a bad month handled well earns, and the bad-month message.
Explore More Topics
This series is part of the QuerySolv helpdesk topic library. It covers the foundations, processes, communication, knowledge, tooling, metrics, classic ticket domains, people and strategy behind a support desk that works. The library pairs well with the software we build: QuerySolv. It is a self-hosted help desk that runs as one Windows service on your own network. It is licensed once per installation, not per agent per month.