For teams
Operations needs the Monday morning version of the plan
Operations leaders are judged on what happens after the memo: on Monday morning, on the night shift, in the week the most capable person is on leave. A process change that reads well in a meeting can still fail in the hands of the people who run it.
Queues obey simple arithmetic
Little's Law, a result from queueing theory, says the average amount of work in a system equals the rate it arrives times the average time it spends there. When work arrives faster than the team clears it, the backlog grows every hour, however hard people try.
Most operating decisions are, underneath, decisions about that arithmetic. Get the arrival rate and the handling time from your own records before debating anything else.
Find the real constraint
Every process has one step that sets the pace for the whole. Improving any other step only makes work pile up faster in front of it. Before choosing a redesign, ask which step limits output today, and whether the proposal touches that step at all.
Written down is not the same as practiced
A new process often works in the pilot because the best people ran it. Ask what happens on a night when the strongest operator is absent, and score that version.
The messy current process has known failure modes, while a redesign has unknown ones. That difference deserves weight of its own.
An operating change in a Decision Room
Each option gets its own Champion, the current process included. The Challenger presses on handovers, where most process errors are born. Craftsman checks whether the people, shifts, and tools exist to run the plan as written. Red Teamer runs the bad night: a surge, a sick call, and a system outage at once.
The room works the staffing sums from your own volumes and handling times, so the comparison rests on your figures rather than a benchmark.
Night cover for a support desk
A support desk receives about 140 tickets overnight across ten hours, or 14 an hour. Each takes about 12 minutes, so one person clears five an hour, and three people are needed just to keep pace. A second local night shift of three, at $38 an hour with the night premium, costs about $416,000 a year. A partner team in another time zone quotes $290,000, with a handover at each end of the night. Keeping one person on call with better tools costs least, but the backlog grows by about nine tickets an hour and reaches roughly ninety by morning. The Verdict favors the partner team, on the condition that a two-week trial shows fewer than one ticket in fifty mishandled at handover; above that rate, the local shift leads.
Questions
- Can the room use our own volume data?
- Yes. Add ticket counts, cycle times, or error rates to the record, and the sums are worked from them. Figures without a source stay marked as claims.
- Who decides the change?
- The operations leader who will answer for it. The Human Decision sits beside the Verdict, and the Outcome can be recorded after the first month on the new process.
Further reading
Bring Argumont a Decision worth challenging.
Start with a paid 60 day pilot on your own real Decisions.