Reducing Equipment Request Friction Without Losing Control

Thursday, 14:05, at Oakhill Legal. Rhys leads the desk of three and is reading the history of ticket 4471, which is a request from Chloe, a paralegal, for a mouse. Raised last Thursday. Triaged Friday morning and sent to her manager for approval. Manager on leave; chased Tuesday. Approved Wednesday afternoon by the manager's deputy, who asked in the reply why he was being asked about a mouse. Issued this morning. Six working days, four people, one mouse, and the mouse was on a shelf twenty metres from Chloe's desk the entire time. Nothing in the ticket went wrong. Every step was followed. Rhys reads it twice and concludes, with some discomfort, that the process worked exactly as designed, and that this is the problem.

Friction, in an equipment request, is every step between "I need a thing" and the thing being in use that adds waiting without adding a decision anyone needed. Reducing friction means removing those steps rather than speeding them up. An approval that takes a day instead of four is still an approval nobody needed for a mouse. This article is part of our Peripherals & Equipment Requests series, and it is the last one. It assumes the workflow, the standard, the stock and the home-office policy from the earlier articles. It asks how to make the whole thing fast without making it careless.

It starts with where the days go, by reading a request's timeline. Next come the pre-approved list and self-service pickup, the honest version. Then come the new-starter kit built in the quiet hour and the renewal cycle for headsets and the like. After that: the requests that still need a decision, measuring turnaround by lane, and what not to remove. It ends with a short war story and the pre-approved equipment list to copy.

Where the Days Go: Reading a Request's Timeline

The first job is to find out where the waiting is, and the only honest way is to read the tickets. Take the last twenty or thirty equipment requests and open each. Write down how many working days it spent in each state. Those are waiting for triage, waiting for approval, waiting for stock or an order, and waiting for handover after the item was ready. Where the tool keeps a status history on the ticket, this is a read rather than a reconstruction. If you run QuerySolv, the event history carries every status change with its time, and the four numbers come off the page. Where the tool keeps less, the timestamps on the messages will do. The exercise takes an hour for thirty tickets, and the hour is the most useful one in this article.

Rhys's thirty tickets came from Oakhill, a desk of three supporting about a hundred and fifty people with roughly forty equipment requests a month. They came out like this, as a worked example and not a benchmark. Triage took under a day in nearly every case. Approval, where it was asked for, took a median of three working days and in six cases more than five. Stock was never the wait, because the cupboard was well run; orders, where needed, took the supplier's time and a day. Handover, the gap between "ready" and "in the person's hands", took a median of one day and in four cases three. The item sat on the desk waiting for a technician to walk it over. Of the thirty, nineteen had gone to an approver, and seventeen of those nineteen were for standard items the person did not already have.

Read that way, the friction has a shape. Two thirds of the requests waited for a decision that the standard had already made. The decision took three days because approvers are busy people who did not know why they were being asked. A smaller share waited a day or three for a walk across the office. Those two waits, approval and handover, were most of the elapsed time, and neither of them was a technician doing anything. Friction is rarely the desk being slow. It is usually the desk waiting, politely, for something it did not need.

The Pre-Approved List

The pre-approved list is the short list of items anyone may have, on request, with no approval from anyone. It is the single change that removes most of the waiting. It is drawn from the equipment standard. The standard keyboard, mouse, headset, laptop-to-dock cable, video cable and charger are for anyone who does not have one or whose old one has failed. The standard dock and monitor are for anyone with a desk who does not have one. The role profile's extra items are for anyone in that role. The approval these items used to get was not a decision. It was a manager being asked to confirm that a paralegal may have a mouse, and the answer was never going to be no.

The list needs two rules to stay safe. The first is one of each: the pre-approval covers the first of any item, and a second of anything goes to the non-standard lane, where the cost question is real. The second is "does not already have one", which the desk checks against the inventory sheet at triage. A request for a headset from someone recorded as holding two is a conversation, not an issue. With those two rules the list cannot be used to furnish a home office at the organisation's expense. Without them it can. So they go on the list itself, in writing, where the requester reads them.

Who signs off the list is the manager above the desk, once. That signature replaces the hundred signatures a quarter that used to be collected one mouse at a time. Take the list and the table above to that manager. Add the sentence "nineteen of thirty requests waited three days for a decision the standard had already made", and the conversation is short. The pre-approved list then lives in the knowledge base where everyone can read it, linked from the request form. The form's pick-list marks the items on it so that the requester knows before submitting that no approval will be needed. The same idea for software, with its own list, is in the software series in this library. The approval convention that handles whatever is left is in Approvals Without a Workflow Engine.

Self-Service Pickup, the Honest Version

Self-service pickup, on a small desk, is a shelf at the help desk with a sign-out sheet. The honest version admits that it is a shelf with a sheet rather than a vending machine. The requester raises the form. The technician puts the item on the shelf with the person's name and ticket number on a label. The person collects it when passing and signs the sheet. At the end of the day, the technician writes the issue note on the ticket from the sheet. The handover wait at Oakhill was a day because someone had to walk. It becomes however long it takes the person to pass the desk, which for most people is the same morning.

The honest version also admits the risks and answers them. A shelf of labelled items in a public corridor is a shelf that gets lighter. So the shelf is at the desk where a technician can see it, not by the printer. The sign-out sheet is the issue record, so an item that leaves the shelf without a signature is shrinkage. The stock sheet from the third article in this series will show it within a count. And the issue note on the ticket still gets written, from the sheet, the same day; pickup removes the walk, not the record. A desk that removes the record to save thirty seconds has removed the only thing that lets it say where its equipment is.

The limit of pickup is the item that needs setting up. A mouse goes on the shelf. A dock with two monitors does not, because the person collecting it will plug it in wrong and raise a dock ticket. That is friction of a different kind. Docks with monitors are delivered and connected by a technician, as the workflow says. The rule is that anything a person can plug in with one hand is pickup, and anything else is delivery. It is a rule that sounds flippant and is, in practice, exactly right.

The New-Starter Kit, Built in the Quiet Hour

The new-starter kit is the pre-approved list applied in advance: a box per role profile. It is built from stock during a quiet hour, labelled with the role, and counted on the stock sheet as one unit of "kit, role". When an onboarding ticket arrives, the technician takes the box for the role from the shelf, adds the laptop, and writes the tags on the ticket. The kit is ready. This turns a two-hour task on the morning of the start date into a ten-minute one the afternoon the request arrives. The profiles that decide what goes in each box are in Role Profiles and Standard Kits. The order in which the kit and everything else has to be ready is in The Day-One Checklist. This article's point is only that the box exists before anyone asks for it.

The quiet hour is real and should be scheduled. Every desk has one, often early in the morning or in the lull after lunch. Building two kits in it is a better use of the hour than most of what fills it. The stock sheet's kit row has its own minimum and reorder point, usually one or two on the shelf for the common roles. The kit is built when the row crosses the line, like any other item. A desk that builds kits only when a starter is announced has stock; it does not have kits.

Kits also fix the request the desk never sees: the starter who arrives on Monday with a laptop and nothing else. The manager raises a request for "the rest" on Tuesday, which goes to approval on Wednesday. The box for the role contains the rest. It contained the rest last month. The starter's first morning is the moment the organisation is most closely watching the desk. A kit on the shelf is the cheapest good impression the desk will ever make.

The Renewal Cycle for Headsets and the Like

Some peripherals wear out on a schedule, and the friction around them comes from asking people to prove it. A headset's ear pads compress and crack after a year or two of daily use; a mouse's switches start double-clicking; a laptop-to-dock cable's connector loosens. The request that follows is "my headset is uncomfortable", and the desk's reflex is to ask whether it is actually broken. That puts the person in the position of arguing with a technician about the state of their own ears. A renewal cycle replaces the argument with a date. A headset is replaced on request after a stated period from issue, no questions, and before that period on a fault. The period is the desk's to set from its own failure data. Oakhill chose eighteen months for headsets and a year for mice, which is one desk's figure and not a rule.

The cycle is also the hygiene answer. Headsets touch people, and a headset that has done two years on one head is not something anyone wants to argue about keeping. Replacing them on a cycle, and never reissuing a returned one, is the sentence that ends that conversation before it starts. The old headset goes to retire, not to the test bin. The issue note says "renewal" so that the stock sheet's issue rate for headsets includes the cycle and the reorder point allows for it. A desk that renews headsets without telling its stock sheet will run out of headsets in the month the cycle first comes due, and will not know why.

The Requests That Still Need a Decision

Removing friction from the standard lane does not remove the non-standard lane. The desk should be clear-eyed about what still needs a decision. That includes the second of anything, an item not on the standard, a quantity for a team, and anything that changes the standard for everyone. Those requests go to an approver, and the friction there is reduced by three things that are not "ask faster". An approver list by request type, so that nobody has to work out who decides. A deputy for each approver, so that leave does not stall the lane. And a deadline in the request, after which silence closes the ticket as no decision, which is the sentence that makes approvers reply.

The decision also gets easier when the approver is told what they are deciding. "Please approve a second monitor for Priya" asks for a signature. "Priya is in a role that gets one standard monitor; she has asked for a second for comparing drawings; cost is a standard monitor from stock; the standard says this needs your yes; answer by Friday or it closes" asks for a decision. It gives the approver everything they need to make it in a minute. Approvers who are sent the second message reply the same day far more often than approvers sent the first. The first message asks them to go and find out, and finding out is where the three days go.

Measuring Turnaround

Turnaround is measured as the median number of working days from the request being raised to the item being in the person's hands, counted by lane. Use the median rather than the average. Otherwise, one order that a supplier took a month over will make the whole desk look slow. The lanes are the ones from the workflow: standard from stock, non-standard with approval, and by order. Each has its own expected figure and its own promise. A desk that reports one number across all three is reporting the mix of requests rather than the speed of the desk. The method for counting tickets by period so that the figure is honest is in Counting Tickets Properly. It includes which date puts a request in the month. Apply it, and then cut by lane.

Beside the medians, two counts say whether the friction work is holding. The first is the share of requests that needed no approval. At Oakhill, it rose from about a third to above four in five once the pre-approved list was in force. It falls again, quietly, when a new manager starts asking for everything to come through them. The second is the stall list: every request that has waited more than the lane's promise. Read it once a week, with where each request is stuck written beside it. The stall list is short on a good desk and it is the first thing to grow when something upstream changes. Any per-technician cut of these figures, if the desk makes one, is for coaching and never for ranking. It is not read from fewer than a few dozen comparable requests. Equipment turnaround is mostly a measure of waiting on other people. A technician's number mostly measures whose approvers were on leave.

The line for the monthly report is one sentence: "Equipment requests: median one working day from stock, two with approval; forty-one requests, thirty-four needing no approval; three stalled, all on order." Where that sentence sits in the report, and what else goes with it, is in The Monthly Report They Will Read. The sentence is dull. Dull is what a well-run request lane looks like from above, and the first month it is dull is worth pointing out, because it was not dull before.

What Not to Remove

Friction reduction has a failure mode, which is removing the steps that were doing something, and three steps are not for removing. The issue note on the ticket, with the tag and the person, is the inventory. Without it the pickup shelf is a free shop and the return at offboarding is a guess. The address rule for anything shipped requires the address on the HR record, never one typed into a ticket. It lets the organisation say where its equipment is, and it costs a day at most. The monthly stock count is the only check that the sheet still describes the shelf. It takes fifteen minutes and has never once been the reason a request was slow.

The identity check belongs on that list too, in its small way. A request for a standard item from a named person on the pre-approved list needs no approval. It does need the person to be who the ticket says. For a request raised from the person's own account through the form, that is already true. For a walk-up, it is a matter of knowing the face. Where the request is for shipment to a home address, the address rule is the check. None of that is friction. It is the difference between a fast lane and an open door. A desk that cannot tell them apart will find out which it has built at the next stock count.

A Short War Story: The Approval Queue at Northgate Retail

Northgate Retail's desk of four supported a hundred and forty stores. Every equipment request from a store, down to a replacement cable for a barcode scanner, went to the store's area manager for approval. A finance rule written for laptops had been applied to everything that came through the form. Kwame, who took over the desk, read a month of tickets and found that the median store request took five working days. Nearly all of it was spent waiting for an area manager who covered twelve stores and approved cables from a car park. In one case a store ran its tills for four days with a scanner cable held in with tape. The replacement cable was in the cupboard and the approval was in someone's inbox. The store's staff spent, by the store manager's estimate, around thirty hours that week keying barcodes by hand. Kwame took the ticket, the thirty hours and a one-page pre-approved list to the finance director, who signed it in a meeting that lasted eleven minutes. The next quarter's median was one working day. The area managers, who had never wanted to approve cables, sent the desk a thank-you that Kwame has kept. A rule that asks a busy person to decide something that was never a decision is not control, he wrote on the list; it is a queue with a signature at the end.

The Pre-Approved Equipment List

The list below is the one Rhys wrote after ticket 4471. It is built to be signed once by the manager above the desk and then read by everyone else. Section A is the items, drawn from the standard sheet. The two rules that keep the list safe are stated at the top where the requester sees them. Section B is the kit and renewal lines, which are the same pre-approval applied ahead of time. Section C is what still needs a decision, so that nobody mistakes the list for "anything goes". Section D is the handover rule, pickup or delivery, so that the technician does not have to decide it per ticket. Fill in your own items and periods; the ones shown are Oakhill's and are there for shape.

PRE-APPROVED EQUIPMENT LIST — ONE PAGE
Signed off by: ______________________   On: ____________   Review with the standard sheet on: ____________

THE TWO RULES
   One of each: this list covers the FIRST of any item. A second of anything needs a decision (section C).
   Does not already have one: the desk checks the inventory sheet at triage before issuing.

A. ISSUED ON REQUEST, NO APPROVAL, FROM STOCK (standard models only; see the standard sheet)
   For anyone:              keyboard, mouse (wired or wireless), wired headset, laptop charger,
                            laptop-to-dock cable, video cable, network cable
   For anyone with a desk:  standard dock, standard monitor
   For listed roles:        the extra items in the role profile (wireless headset, second monitor, ______________)
   On a fault:              a replacement for any item above, old item returned to the desk

B. PRE-BUILT AND RENEWED (same pre-approval, applied ahead of time)
   Starter kits:   one box per role profile, built in the quiet hour, min ____ on the shelf per common role
   Renewal cycle:  headset replaced on request after ____ months from issue; mouse after ____ months;
                   earlier on a fault. Returned headsets are retired, never reissued.

C. STILL NEEDS A DECISION (non-standard lane: approver, deputy, deadline)
   A second of any item ...................... requester's manager (cost)
   An item not on the standard sheet ......... the desk (fit), then the standard's owner
   Any quantity for a team ................... the team's manager (cost)
   Anything for a home address not on record . not issued until HR holds the address
   Approver list kept at: ______________   Deadline in every request: ____ working days, then "no decision"

D. HANDOVER
   Pickup from the desk shelf, signed out:   anything the person can plug in with one hand
   Delivered and connected by a technician:  docks, monitors, starter kits, anything assessed
   Shipped to the HR address on record:      anyone remote; tracking on the ticket; reply to confirm receipt
   The issue note is written on the ticket the same day, whichever handover applies.

Chloe's next request, for a replacement headset nine months later, took the lane the list had built. It was raised at ten, on the pickup shelf by eleven, collected and signed for at lunch, with the issue note written by two. Nobody approved it, because nobody needed to. Rhys measured the quarter and found the median at one working day. Thirty-four of forty-one requests had no approval, and three were stalled, all on order from a supplier having a difficult month. He put the sentence in the report. The manager above the desk, who had signed the list in April, read it and asked why it was so short, which Rhys took as the compliment it was.

Frequently Asked Questions