When a Permit Office Stopped Blaming Its People: A Lean Story from the Public Sector
A mid-sized municipality — call it the District of Harrow — ran a development permit office that everyone agreed was slow. Residents waited eleven weeks for a routine renovation permit. Staff worked overtime. Council fielded complaints at every meeting. The instinct, repeated for years, was that the team needed to try harder or that more people had to be hired. This is a composite of situations we see often, and the lesson holds: when service feels slow, the problem is almost always the process, not the people inside it.
By late 2021 the pressure had a new edge. Construction was rebounding after the early pandemic stall, applications were climbing, and half the office was still working hybrid. Backlogs that used to be irritating were now visible to the whole community. Harrow agreed to map what actually happened to a permit, end to end, before changing anything.
What the value stream revealed
The team walked one ordinary application through every step and timed each one honestly. The result was the classic Lean surprise: of those eleven weeks, the file was actively being worked on for roughly four hours. Everything else was waiting — sitting in an inbox, queued for a second review, parked while one reviewer asked another a question by email and waited two days for a reply.
Lean gives names to what the team was seeing. Most of the elapsed time was pure waste in the technical sense — the eight wastes, of which waiting, handoffs, and rework were doing the real damage here:
Waiting: files idle between desks far longer than they were ever touched.
Handoffs and motion: a single permit changed hands five times, and twice it crossed buildings.
Rework: about a third of applications bounced back to the resident for missing information that a simple intake checklist would have caught on day one.
Over-processing: low-risk fence and deck permits went through the same heavyweight review as a multi-unit build.
Fixing flow instead of pushing harder
Harrow did not buy software or add headcount first. It changed how work moved, using ordinary Lean moves that any service operation can copy:
Triage at the front door. A short intake screen sorted applications into simple, standard, and complex. Simple permits got a fast lane with a single reviewer, so they stopped queuing behind complicated files.
A complete-application checklist. Residents saw exactly what was required up front, which cut the back-and-forth rework dramatically and shortened the painful first wait.
Limit work in progress. Reviewers stopped starting ten files and finishing none. Capping active files exposed where the real bottleneck was and pulled total cycle time down.
Daily fifteen-minute huddle. Hybrid staff met briefly to flag stuck files and unblock each other in minutes instead of letting an email sit for two days.
Within a quarter the routine-permit wait fell from eleven weeks to under three, with no new hires and no overtime. Just as important, the tone changed. Staff had spent years feeling personally blamed for delays they did not cause. Once leaders looked at the value stream, it was obvious the people were competent and the system was the problem.
What public-sector leaders should take from this
Three lessons travel well beyond one permit office. First, measure elapsed time, not effort — a backlog is usually a waiting problem, and you cannot manage what you only feel. Second, separate simple work from complex work so the easy majority is not held hostage by the hard minority. Third, treat slow service as a defect in the process, which is fixable, rather than a failing in the staff, which only breeds turnover. Lean in government is not about doing more with less; it is about removing the waiting that quietly eats most of a citizen's wait.
If your public-sector service is slow and the instinct is to add people, a value-stream view often finds the answer first — XNM's strategic advisory helps governments and agencies map the work and fix the flow.