Proving Self-Service ROI to Management in One Page

Monday, 17:40, at Meridian Parts. Hana has three worksheets on her desk: a cost per ticket, a deflection ledger for eleven articles and a technician-time sum. She has a calendar entry for Thursday that says "Budget review: IT support, 10 min". The operations director, Callum, has told her, kindly and without apology, that he will read one page before the meeting and no more. If the one page does not say what she wants, he will assume she does not want anything. She has about forty pages of honest working and a strong urge to attach all of it. The forty pages are the reason the one page will be believed. They are not the one page.

A one-pager is a single page that tells a decision-maker what something cost, what it returned and what you want next. It follows the order they will ask, with the evidence summarised and the working kept behind it. For a self-service programme, a knowledge base, a portal, or a password reset users do themselves, the page has a fixed shape. It contains a sentence, a before-and-after table, three lines of hours, the ask, and one line about how the counting was done. How to write any technical brief for a manager is the subject of Explaining Technical Things to Management. That covers the two-minute read, the plain words, and the decision first, and this article assumes it. This one is about what goes on the page when the subject is self-service ROI. It is part of our Measuring Self-Service ROI series, with every number a worked example from the same fictional desk.

It covers who reads the page and for how long, then the before-and-after table it is built on. Next come the hours as three lines rather than thirty, and the ask. We cover what to leave off, then the shape of the page from top to bottom. Next come the four questions to expect and the answers to have ready. We finish with presenting it, a short war story, and the ROI one-pager to copy, in that order.

Who Reads It, and for How Long

The reader is a manager with a decision to make and about two minutes to make it in. They want three things in a fixed order: what did this cost, what did we get, and what do you want from me. Everything else on the page is there to make those three answers believable. Anything that does not do that is taking up space a manager will not give it. A manager reads a one-pager the way a technician reads an error message: the first line, then the part in bold, then who sent it. Write for that reading. If the first line and the bold parts carry the case, the rest of the page is confirmation. If they do not, the rest of the page is unread.

The reader also brings a history, and for self-service it is a history of being promised too much. Vendors have shown them slides in which a knowledge base pays for itself by Tuesday. A previous desk may have reported view counts as savings. They have sat in a meeting where "productivity gains" turned out to mean nothing anyone could point at. So the page is read with a discount already applied. The way to remove the discount is to show the counting before being asked. That means ranges rather than points, a control type named, the effort on the cost side, and views nowhere. The one sentence that does the most work on the page is the one that says how you counted. And it is the sentence most desks leave off.

Finally, the reader will forward it. A one-pager that persuades the operations director will be sent to the finance director with "see attached" and no commentary. And the second reader has no context at all. So the page must stand alone: no "as discussed", no reference to the meeting, no figure that depends on a conversation. If a stranger in another department could read it and understand what was spent, what came back and what is being asked, it is finished. If they would need to phone you, it is not.

Before and After: The Table the Page Is Built On

The spine of the page is a small table with the same measures in two columns. They cover three ordinary months before the self-service work and three ordinary months after. The table is the first thing the reader's eye will settle on. The measures are counts the ticket system produces, not interpretations. They include tickets per month in total, and tickets per month for the two or three types the programme targeted. They include hands-on minutes for the one ticket type that improved most, reopens on the documented types, and the senior's hours per new starter. Five or six rows. Every row must be a thing a sceptic could re-count from the ticket list. And every row's before and after must be measured the same way, which is the discipline the deflection article spends most of its length on.

Meridian's table had six rows. Tickets per month fell from about three hundred and eighty to about two hundred and ninety. Password reset tickets fell from around a hundred and ten to around forty after the self-service reset was switched on in the directory and the desk ran the enrolment campaign. VPN tickets fell from forty-six to nineteen. Hands-on minutes on a mapped-drive ticket fell from thirty-eight to seven. Reopens on the documented types fell from five a month to one. Senior hours per new starter fell from about forty to about twelve. There are six lines, every one of them checkable, and together they say more than any paragraph could. A before-and-after table is the one form of evidence a manager has learned to trust from every other department.

Resist adding rows. The temptation is to show every ticket type that moved. And the result is a table that runs to twenty lines and is read as a list rather than as a story. Pick the rows that carry the case and put the rest on the sheets behind the page. The same restraint applies to the columns: before and after, nothing else. A third column for "target" or "industry typical" invites a conversation about where the target came from. The honest answer, that it came from nowhere in particular, costs more than the column was worth. The ticket system may produce the rows directly, as the volume and resolution-time reports in QuerySolv and most tools can. In that case, the table takes a few minutes to update each quarter. That matters, because this page will be asked for again.

The Hours: Three Lines, Not Thirty

Below the table come the hours, and there are three lines of return, one of cost, and one net, each a range. The first return line is tickets avoided, the net of every deflection ledger added together with no ticket type counted twice, by the method in Deflection Math Without Fooling Yourself. The second is faster and more consistent resolution, from The Time Saved by Technicians. The third is onboarding, per new starter, shown beside the monthly figures and not added to them. The cost line is the one-off effort in hours and the monthly upkeep. The net line is return minus upkeep, with the one-off effort stated and its payback given in months.

Meridian's tickets-avoided line read thirty-five to a hundred and twenty hours a month. Faster and more consistent resolution returned twenty-five to forty-four hours a month. Onboarding returned about twenty-eight senior hours per new starter. Effort was about a hundred and ninety hours once across the year and about six hours a month of upkeep. The net was roughly fifty-five to a hundred and sixty hours a month. The one-off effort was paid back inside the first quarter on the low figure. The wide range on the first line is honest. It runs from the hands-on figure for quick ticket types up to the loaded figure, and the page says so in the honesty line. A manager who sees "fifty-five to a hundred and sixty" and asks why it is so wide has asked the right question. The answer is that the low end is what you could defend under oath and the high end is what it is probably worth. That is an answer they will accept and remember.

Keep every figure in hours, and offer the conversion as one line only if the reader's role needs it. The reasons are in What ROI Means for a Help Desk. And the short version is that hours are the desk's evidence and currency is somebody else's. If the finance director wants currency, the line reads "at the technician rate finance uses, multiply the net line by it". The finance director, who knows the rate better than you do, will. A desk that does the multiplication itself has picked a rate, and the conversation becomes about the rate.

The Ask

The ask is one thing, stated in the units the page has been using, with a date and the return you expect from it. One thing, because a page with three asks gets none of them: the reader chooses the cheapest, or defers all three to a meeting that will not be scheduled. Hours, because the page has just spent its credibility establishing hours as the currency and the ask should spend that credibility, not change the subject. A date, because an ask without one is a wish. And include an expected return, as a range, because the reader has just been shown that this desk counts. An ask that comes with its own expected return is an ask from someone who has already thought about whether it is worth it.

Meridian's ask was for protected time: half a day a week of one technician, for a year. It was for knowledge base upkeep and the next twenty articles, chosen from the failed-search list and the hands-on table. That is about seventeen hours a month, and the page said what it expected back. Upkeep was expected to hold the current fifty-five to a hundred and sixty. The new articles were expected to add somewhere between ten and thirty hours a month by the year's end. The returns would be measured the same way and reported on this page next quarter. Not a new hire, not a tool, not a budget line in currency. The thing the desk actually needed was for the time it was already spending to stop being the time it apologised for.

Tie the ask to what the freed hours have gone on, in one line, because a manager's silent question about any saving is "so what did you do with it". Meridian's line said that the hours had gone into clearing the tickets older than two weeks, which had fallen from thirty-one to twelve. The hours had also gone into the mapped-drive runbooks that produced the second return line. That closes the loop: the saving was spent on things the manager can see, and the ask is for the means to keep producing it. A saving that went nowhere visible is a number; a saving that paid for the backlog clearance is a result. The method for showing a backlog honestly on a page is in Explaining the Backlog to Management, and the two pages pair well.

What to Leave Off

Leave off article views, however large. A view count on the page tells the reader you are counting attention as results, and undoes the honesty line in the time it takes to read a number. If the knowledge base's reach matters to the case, say "the top ten articles are read several hundred times a month" in the appendix and keep it off the page. Leave off percentages that are not beside their counts; "deflection rate 58 percent" means nothing without the forty-six and the nineteen, and with them it is redundant. Leave off currency unless the reader's role requires it, and then as one line with the rate named.

Leave off the list of articles. A hundred and forty titles is a document, not evidence, and the three that matter are already in the table. Leave off the methodology, which goes behind the page as the worksheets themselves; the honesty line names the method and the appendix proves it. Leave off anything that explains how the knowledge base works, how the portal was built, or what the team learned. The reader is deciding, not studying. And leave off adjectives. "Significant", "substantial" and "dramatic" are words a reader has learned to read as "we did not count", and a page that has counted does not need them. The methodology appendix is where rigour goes to be respected and unread, and that is exactly where it belongs.

Leave off the parts that did not work only if they are small; otherwise put them on, briefly, because they are the most persuasive thing on the page. "Two articles cost more to maintain than they save and have been retired" is a sentence that tells the reader every other number was counted the same way. A page with nothing on it but good news is read as advertising; a page with one honest line of bad news is read as a report. Meridian's page carried that line, and the operations director underlined it, which Hana took, correctly, as a compliment.

The Shape of the Page

From the top, the page starts with a heading that says what the page is and the period it compares. Next is one sentence that gives the net range and the payback, which is the whole case for a reader who stops there. Then come the before-and-after table, and the three lines of hours with the cost and the net. Next come a line on what the freed hours went on, and the ask with its date and expected return. The honesty line comes last. It says the baseline length, the control type, what the low and high ends mean, that views were not counted, and that the working is attached. Seven elements, in that order, and the order is the order the reader's questions arrive in. The template at the end of this article is that shape as a form.

The one sentence at the top deserves more drafting than the rest of the page together, because for some readers it is the page. Meridian's read: "Over the past year the self-service work, the knowledge base, the portal and the self-service password reset, is returning between fifty-five and a hundred and sixty technician hours a month after upkeep, for a one-off effort of about a hundred and ninety hours that paid back inside the first quarter." Forty-eight words, no adjectives, two ranges, one payback. A reader who stops there knows what happened. A reader who continues finds the table that proves it.

Keep it to one page by cutting, not by shrinking the font. Shrinking the font is the oldest trick in the building and fools nobody who has ever received a one-pager in nine-point type. If the page will not fit, something on it belongs in the appendix, and the usual culprit is a second table. The appendix is the worksheets from this series, stapled behind, in the order the page refers to them. That order is cost per ticket, the deflection ledgers, the technician-time sheet, and the usage report. Nobody will read them in the meeting. Someone will read them afterwards, and that reading is where the page's credibility is confirmed or lost. So the sheets must be the real ones, with the oddities noted and the ranges intact.

The Four Questions to Expect

The first question is "how do you know it was the knowledge base?", and the answer is the control type and the counting rule, in two sentences: "We watched a ticket type we did not write about over the same months and it did not move, so the drop in the documented types is not the desk getting quieter; and the low end of every range counts only the tickets we can tie to an article, so even if the rest is coincidence the low figure stands." Have the control type's name and numbers ready. A manager who hears "control type" from a help desk will usually stop asking, because the phrase tells them the counting was done by someone who expected to be asked.

The second question is "what would it have cost to do nothing?", and the answer is the before column, projected forward. That means the tickets that would still be arriving at the before rate, times the hours each one took. That is the high end of the return line and should be said as such. The third is "why is the range so wide?" The answer is the one above: low is defensible and high is likely. Note that a narrower range would be a less honest one. The fourth is "what happens if we stop?", and the answer is the upkeep line. The articles drift out of date within two or three quarters, the busy-but-failing box fills, and the tickets come back with "I followed the article" in the first line. That is worse than before because the requester has been let down once already.

Prepare a fifth answer for the question that is not asked, which is "how do I know you are not just good at this now?" The answer is that the page will be produced again next quarter, measured the same way. The sheets are attached so that anyone can re-count. A one-pager that commits to its own repeat is one a manager can approve without feeling they have been sold something, because the check is built in. Meridian's page ended with the words "next report: end of the following quarter", and Hana meant it, which is the part that cannot be templated.

Presenting It

Send the page two working days before the meeting, with the sheets attached and a two-line covering note. The note says what the ask is and when you need the decision. The meeting then begins with the reader having read. And the ten minutes are for questions rather than for walking through the page, which no manager wants walked through. Speak for two minutes at most: the one sentence from the top, the ask, and an offer to take questions. Then stop. The silence that follows feels long and is where the decision is made. A desk lead who fills it with more evidence has turned a report into a pitch.

Answer the questions with the numbers on the page and the sheets behind it, and never with a number that is on neither. If a question needs a figure you do not have, say so and name the day you will have it. A manager who hears "I don't know, I'll have it by Thursday" from someone whose page said "control type" believes both statements. A manager who hears a confident number that is not on the page starts to wonder about the ones that are. The page's whole value is that every figure on it was counted before anyone asked, and an improvised figure spends that value in one breath.

Follow up the same day with one line confirming what was decided, in writing, to everyone who was in the room. If the ask was approved, the line says so and names the date the next page is due. If it was deferred, the line says what was asked for and when it will be provided. If it was declined, the line says the desk will keep measuring and report again in a quarter. That is both true and the thing most likely to reopen the question. The page is a quarterly instrument. The first one establishes that the desk counts. The third one, with three quarters of the same table and the ranges holding, is the one that gets the second technician.

A Short War Story: The Fourteen-Slide Deck at Stonebridge Insurance

At Stonebridge Insurance, the desk lead, Priyanka, had a year of honest measurement behind her knowledge base. She built the case for protected upkeep time as a fourteen-slide deck. It had a view-count chart on slide three, a deflection rate on slide six, and a "productivity gains" estimate on slide nine. The ask, for one afternoon a week across the team, was on slide fourteen. The IT director asked "so what do you actually want?" at slide nine and was told it was coming. The meeting ended at slide eleven when his next one started. The decision was deferred to the following quarter, by which time the budget round had closed. And the upkeep time stayed unprotected for seven more months. During those months the three most-read articles drifted out of date after a software change. The "I followed the article" tickets started arriving at about forty a month. The next version of the case had to open by explaining why the knowledge base appeared to be generating tickets. Priyanka's second attempt was one page, with the ask in the second paragraph and the before-and-after table under it. It was approved in the meeting it was presented in. The deck had been described afterwards as thorough. A case that puts the ask on the last page has made a bet that the meeting will reach the last page, and meetings do not.

The ROI One-Pager

The template below is the page, as a form, in the order the reader's questions arrive. Section one is the sentence, and it is written last, after the rest is filled in, because it summarises the rest. Section two is the before-and-after table, with no more than six rows and a column saying where each number came from. That way, the page carries its own audit trail. Section three is the hours as ranges, with the cost and the net. Sections four and five are what the hours went on and the ask. Section six is the honesty line, which is the sentence that removes the reader's discount. Everything in it comes from the worksheets in this series, which are attached behind it and are never summarised twice.

SELF-SERVICE ROI — ONE PAGE
For: ______________________   From: ______________________   Date: ____________
Period compared: three months ending ________ (before) vs three months ending ________ (after)

1. IN ONE SENTENCE
   The self-service work (______________________________) is returning between
   ____ and ____ technician hours a month after upkeep, for a one-off effort of
   ____ hours that paid back in ____ months.

2. BEFORE AND AFTER (same measures, same method, three ordinary months each)
   Measure                                        Before     After     Source
   Tickets per month, all types ................ ____       ____      ticket system, closed per month
   ______________ tickets per month ............ ____       ____      ticket system, by type
   ______________ tickets per month ............ ____       ____      ticket system, by type
   Hands-on minutes, ______________ (median) ... ____       ____      timestamps, twenty sampled
   Reopens per month, documented types ......... ____       ____      ticket system reopen count
   Senior hours per new technician ............. ____       ____      calendar (reconstructed: yes / no)

3. THE HOURS (ranges; low = tied to tickets that can be pointed at; high = the loaded figure)
   Tickets avoided ................................. ____ to ____ hours a month
   Faster and more consistent resolution ........... ____ to ____ hours a month
   Onboarding (per new starter; not in the total) .. ____ senior hours per starter
   Effort: one-off ____ hours; upkeep ____ hours a month
   NET ............................................. ____ to ____ hours a month
   Did not pay: ______________________________ (retired / stopped)

4. WHAT THE FREED HOURS WENT ON
   ______________________________________________________________ (one line, checkable)

5. THE ASK (one thing)
   ______________________________________________________________
   Decision needed by: ____________   Expected return: ____ to ____ hours a month, measured as above
   Next report: ____________

6. HOW WE COUNTED
   Three-month baseline; control type ______________; views not counted as tickets;
   effort recorded when spent; working attached (cost per ticket, deflection ledgers,
   technician time sheet, usage report).

Hana's page went to Callum on the Tuesday, with four worksheets behind it, and the Thursday meeting lasted six of its ten minutes. He asked what the control type was, what would happen if they stopped, and whether the half-day a week was in addition to the time Lena already spent. The answers were on the page, on the page, and "yes, that is the point". The half-day was approved, with the next report due at the end of the following quarter. On the walk back to the desk Hana noticed that she had not once, in a year of this, said the words "a lot". The forty pages had done their work by staying in the folder.

Frequently Asked Questions