The signs you need a service desk show up as small recurring failures rather than as one obvious problem. Each is a symptom of requests having no state. The symptoms They are easy to recognize once named. * Requests answered twice, because two people picked up the same one * Requests never
The signs your spreadsheet has outgrown its purpose are not about size. A large spreadsheet one person owns is often fine. The signals are about dependency and control. Signals that matter Each one indicates a structural limit rather than an inconvenience. * Multiple versions circulating, because more than one person needs
The signs you need an approval workflow are specific rather than general. Informal approval works genuinely well at small scale, and the failures when it stops working are recognizable. The five signs Any two of these together usually mean the informal version has run out. * One person approves everything, and
When request volume rises suddenly, the instinct is to add people. Learning to keep a queue moving when volume spikes means using the levers that work faster than hiring. Why queues degrade non-linearly A small increase in arrivals produces a large increase in waiting once capacity is approached. * Response
A controlled process in a regulated environment needs three things beyond a normal workflow: evidence that each control was applied, restriction of who could have acted, and an exportable record of both. What regulators typically test The questions are about evidence rather than intention. * Whether a required check was actually
To adapt a process for seasonal changes, the adjustments should be reversible. A process modified permanently for a three-month peak carries that complexity all year. What usually changes in a season The process is the same; the parameters are not. * Approval thresholds relaxed to keep volume moving * Additional people
To build a dashboard readable on a phone, you accept that it cannot show what the desktop version does. The mobile panel should answer one question, not five. Why desktop panels fail on mobile A wide layout becomes a long scroll, with the important figures at the bottom. * Thirty indicators
Handling a process with parallel steps is where boards show their limit. A card sits in one column at a time, so genuinely simultaneous work needs a different structure. Where sequence breaks down Some processes are simply not linear. * Legal and finance reviewing the same contract at once * Several departments
To reduce time to first response, you have to know what it currently is — per channel, per phase, and per type of request. Improvement efforts without that number usually target the wrong step. Where the delay actually is It is rarely the writing of the reply. * Requests arriving somewhere nobody
To build a process that survives turnover, the knowledge has to live in the system rather than in the person. Most processes fail this test without anyone realizing until someone resigns. What leaves with a person It is rarely the steps. It is everything around them. * Why the process is
Deciding what happens when an approver is unavailable is a question most approval processes answer only after the first time it causes a problem. The three bad options Each one appears when nothing was planned. * Everything waits until they return * Someone else approves informally, with no record * The rule is
To structure recurring monthly work, the repetition should be a property of the process rather than a habit someone maintains. Work that recurs predictably should not be created manually each time. What recurring work costs when unmanaged The creation is trivial; the forgetting is not. * The same tasks recreated by