Where Work Actually Slows Down

Most systems think they understand where work slows down.

They look at delays, missed timelines, and backlogs and assume the problem is where the work appears to stop.

But that’s not where bottlenecks actually exist.

In this episode, I break down how bottlenecks operate beneath the surface, why they’re often misidentified, and how systems respond to symptoms instead of fixing the constraint.

Because bottlenecks don’t always look like stopped work.
They often look like busy work.

This episode explores:

•  Why bottlenecks are usually upstream from where problems show up 
•  How systems misidentify constraints and focus on the wrong areas 
•  Why pressure and urgency don’t fix flow 
•  How workarounds and “hero effort” hide real system issues 
•  The difference between activity and actual movement of work 

Because improving performance isn’t about pushing harder.

It’s about understanding how work actually flows… and fixing where it can’t.

The views and perspectives shared in this podcast are my own and do not represent the views of my employer or any organization I am affiliated with. 

Transcript

SPEAKER_00 0:04

Welcome back. This is Behind the Measures, a podcast about public sector leadership, quality, and accountability, and the work that doesn't show up in dashboards or reports. My name's Jeremy Hurley, and I work inside the system building programs, fixing what's broken, and navigating the space between compliance and real improvement. This isn't about theory, it's about the work. This is episode twelve, where work actually slows down. Work doesn't slow down where most systems think it does. It slows down where the system is least understood. Most organizations believe they know where their bottlenecks are. They look at delays, they look at missed timelines, and then they look at where work appears to stop moving. And then they assume that that's the problem. But bottlenecks don't always look like stopped work, they often look like busy work. You know, work is moving, people are active, tasks are getting completed, but underneath that activity, something isn't flowing. Because bottlenecks aren't defined by where work stops, they're defined by where work struggles to move. And most systems don't see that clearly. Most systems don't just miss bottlenecks, they a lot of times misidentify them. They assume the problem is the step where work is visible, the step where timelines are tracked, and sometimes the step where someone is accountable on paper. So that's where the pressure goes. That's where the questions go, that's where the attention stays.

SPEAKER_01 2:25

But that step is usually not the constraint, it's just where the impact shows up.

SPEAKER_00 2:35

And when the system focuses there, it ends up managing the symptom instead of fixing the cause. Instead, systems respond to what they can see. You know, a delay shows up, so they push for a faster turnaround, a backlog build, so they ask people to work harder. And then deadlines are missed, so they increase the pressure. But pressure doesn't fix flow, it just hides the problem for a little while. Because when work starts to slow down, the system adjusts. You know, people step in, they fix things manually, they find workarounds, they do whatever it takes to keep things moving. And from the outside, it looks like the system is working. But what's actually happening is the system is being held together by effort, and over time that effort becomes expected. The people who fix things become the ones everyone relies on. You know, they step in, they catch issues early, they keep things moving. And the system starts to depend on them instead of fixing what they're compensating for. Then, or that's when a bottleneck becomes invisible. Because as long as someone is holding it together, it doesn't look like a problem, right? That's where bottlenecks live. They don't live in the obvious breakdowns, but in the places where the system quietly struggles, and a lot of people compensate for it. Most of the time, the actual bottleneck isn't where work is piling up, it's a lot of times it's upstream. You know, work builds before the constraint, not at it. So by the time the system notices a problem, it's already looking in the wrong place. And that leads to the wrong response. More pressure, more urgency, more focus on output. Instead of asking a different question, where is the system actually struggling? Because bottlenecks aren't just about volume, they're about capacity. They're about how work moves from one step to the next step, and what happens when that movement breaks down. A process can look efficient on paper, but if one step can't keep up with the rest, everything behind it starts to slow down. And the system doesn't always recognize that because it's still seeing activity. People are working, tasks are being completed, reports are being submitted. So, from a measurement standpoint, things are things look fine. But flow tells a different story. You could feel a bottleneck before you can measure it. It shows up when work keeps coming, but decisions don't. When things are technically in progress, but nothing is actually moving forward when the same items keep getting revisited because they couldn't move the first time. You know, it feels like constant motion without progress. Work is waiting, and handoffs are delayed, decisions take longer than they should, and none of that always shows up clearly in a in a metric. So the system keeps pushing, keeps pushing more output, it keeps pushing more speed and more urgency. But when when you push work through a through a constraint, you don't fix it, you overload it. Priorities start shifting, people start reacting instead of operating, and now the system isn't just slow, it's really unpredictable. That's where things start to break down, and the thing is, is it's not all at once, but it happens gradually because bottlenecks don't create immediate failure, they create friction. Friction slows everything down, it forces rework and it increases variation, it also makes outcomes less predictable, and over time that friction becomes normal. People adjust to it, they expect delays, they build in extra time, and they rely on the same workarounds over and over again, and eventually the system stops seeing it as a problem. It just becomes how the work gets done. That's why most systems don't see bottlenecks clearly. It's not because they aren't looking, but because they're looking at the wrong signals, they're looking at outcomes instead of flow, they're measuring completion instead of movement, and as long as the work gets done, the system assumes everything is working. But getting work done and having a system that works are definitely not the same thing. So, what does this require? It requires shifting attention away from just outcomes and toward the how the work actually moves. Where does the work wait? Where does it slow down? Where does it rely on the same people to fix the same problems? Because those are the signals that we're looking for, not the final number, not the completed task, but the points in the system where flow breaks down, and that's where leadership matters. Because if you're only looking at outcomes, you're always reacting late, you're seeing the result, not the condition that created it, and by the time a number changes, the system has already been struggling for a long while. Leadership is not about pushing for more output, it's about understanding the system well enough to see where it can't keep up. Because once you see the bottleneck clearly, the response changes. You stop pushing the system harder and you start fixing the constraint. Because improving flow is what actually improves performance, not effort, not pressure, not urgency, flow. And if the system can't move work consistently, it doesn't matter how hard people are working. It will always feel like it's catching up. Now, next time I want to do something a little different. In the next episode, it's not about the system, but about the person inside it. Because behind every process, behind every metric, behind every decision, there's someone carrying it.

SPEAKER_01 13:19

And most of the time, that part doesn't get talked about. Because the work doesn't end at the measure.