Learning objectives
- Map a repeatable service and its handoffs.
- Balance workload and quality without treating people as unlimited capacity.
Make the flow of work visible
Start at the customer request and follow one real item to completion. Record the inputs, owner, queue, decision and output at each step. Waiting between teams may matter more than the processing time. Define what “ready to start” and “complete” mean so an incomplete request is not repeatedly passed downstream. A simple shared checklist can be more useful than a complex diagram that nobody follows.
Estimate demand and usable capacity
Count arrivals over a defined period and sample the time needed for different types of work. Include checking, coordination, breaks and predictable interruptions when estimating usable capacity. An average can hide an afternoon peak or a small number of difficult cases. Keep a buffer appropriate to variability and consequence; scheduling every minute leaves no room for an urgent exception.
Place checks where errors can be corrected
Define the few quality conditions that protect the customer and the business. Check essential information before irreversible work, and review a sample after completion. Record the cause of rework separately from the person who noticed it. Repeated missing information may require a better intake form rather than another reminder to work faster.
Improve one constraint and review the whole service
Choose a visible bottleneck, agree a small change and compare the outcome with an appropriate baseline. Monitor both flow and quality: faster closure is not progress if customers must contact the team again. Give staff a way to flag unsafe or unrealistic work and escalate exceptions. Document the updated method, train the team and check that another stage has not become overloaded.
A repeatable operating loop
Use the loop to learn from ordinary work as well as unusual failures.
Receive
Check the request and define the next owner.
Perform
Use a clear method and suitable capacity.
Verify
Check essential quality conditions and exceptions.
Improve
Review delays and rework, then update the method.
Comparison
| Stage | Completion rule | Useful evidence |
|---|---|---|
| Intake | Required details confirmed | Share returned for missing information |
| Processing | Task completed to the agreed scope | Time in queue and work time separately |
| Review | Critical checks passed | Rework reason and repeat contacts |
| Closure | Customer informed and record retained appropriately | Resolution quality and remaining exceptions |
Finding a capacity gap
A hypothetical team receives 120 similar requests weekly. Sampled work takes 15 minutes per request, before other duties.
- Direct request work is 120 × 15 minutes = 1,800 minutes, or 30 hours.
- The team adds six hours of scheduled checking and coordination, giving 36 hours of demand.
- Only 28 hours of usable capacity are available. It investigates avoidable rework and response commitments before deciding how to cover the eight-hour gap.
The estimate makes the gap discussable. It is a planning example, not proof that every request takes the average time or that staffing is the only solution.
Practical checklist
- Map one request end to end.
- Define ready, complete and exception rules.
- Estimate demand and usable capacity separately.
- Review quality alongside speed.
Common pitfalls
An invisible queue
Work waiting in private messages makes priorities and capacity difficult to understand.
Speed without resolution
Closing an item early can improve a dashboard while creating repeat work for customers and colleagues.
Questions and answers
Does every process need automation?
No. Clarify the work, exceptions and owner first. Automate a stable, suitable step when the benefit justifies setup and maintenance.
Is average handling time enough for staffing?
No. Consider arrival patterns, task variation, other duties, service expectations and the consequences of delay.
Sources and further reading
- Capacity and capability planningCIPD
Further reading on connecting organizational demand with people and skills.
- Business operationsU.S. Small Business Administration
Official management guidance provides context for connecting delivery, finances and people.
