Contents
A municipal team finds where faster work stops helping
Starting point
Residents report damaged public benches by phone, email and an online form. Reports may omit the precise location or describe the same bench more than once. Office staff must create a usable job record before a field crew can inspect and repair it. The goal is a safe repair and a reliable update to the resident.
An officer reads each message, asks for missing locations, checks for duplicates, creates a job record and sends it to the crew scheduler. The scheduler checks urgency, location, materials and available crew time. The field crew is already fully booked.
Three ways to arrange the work
Same starting situation and goal in each. Switch at any point; the labels describe arrangements, not a ranking.
Use released time to improve the handoff
Test a redesigned workflow · authored illustration- The person
- Maps waiting time and confirms that field capacity, rather than intake, currently limits completed repairs.
- AI
- Summarizes queue records and highlights where information is missing.
- Result or handoff
- The team separates an office time saving from an overall service improvement.
- The person
- Uses local knowledge to confirm access, likely material needs, urgency and which jobs could sensibly be grouped.
- AI
- Groups candidate jobs by location, flags missing details and prepares proposed job packs from verified records.
- Result or handoff
- Staff approve the packs and priorities; extra AI output is not treated as a scheduling decision.
- The person
- The scheduler and crew assess whether packs reduce avoidable trips, missing materials or repeat visits.
- AI
- Compares recorded preparation, travel, rework and completion times.
- Result or handoff
- The team keeps, changes or stops the added preparation based on actual service results.
Outcome
Local gain assumed · service outcome unresolvedSuppose office handling time falls substantially, but the same number of benches is repaired and residents wait just as long. That is a local improvement, not evidence of a matching service gain. Better job preparation may help the crew, but this remains a hypothesis. If the added preparation does not reduce wasted work, the team should simplify or stop it. A could qualify as at its stated boundary if its magnitude, quality and full resource accounting support that claim; this scenario supplies no measured multiplier.
What would need to be measured
Measure office effort and data quality separately from queue age, field hours, completed repairs, repeat visits and resident outcomes. Include time spent checking the AI’s grouping, correcting locations and maintaining records. Compare similar workloads and seasonal conditions. A faster acknowledgement is a distinct service benefit if measured, but it is not a faster repair.
Office handling becomes much faster, but completed repairs and resident waiting times stay the same. Is it fair to say the repair service is several times more productive?
Write your answer in the conversation. You'll get live feedback on your reasoning — no score, and you don't have to agree with the policy.
How this connects to the policy
These policy sections explain the ideas in this example. They do not substantiate its invented outcome.
- 4.5 Bottlenecks migrate (Policy framework)
- 8.3 Evidence proportional to the decision (Policy framework)
- 6.4 System throughput (Measurement companion)
- 6.5 Capacity reinvestment and quality under constrained throughput (Measurement companion)
- 10.2 Reinvesting released capacity to reduce downstream review demand (Theory companion)