Activity vs Progress: Why Busy Systems Stay Stuck

Activity is easy to see.

Meetings. Reports. Updates. New initiatives. Full calendars and constant communication.

And when all of that is happening, it feels like progress.

But in many systems, activity and progress are not the same thing.

In this episode, I break down the difference between motion and meaningful change, and why confusing the two can quietly keep systems stuck.

Because activity creates movement.
But progress creates change.

And a system can be very busy… without actually improving.

In this episode, I talk about:
 • why activity feels like progress, and why systems reward it
 • how effort can exist without anything actually changing
 • what progress really looks like (and why it’s harder to recognize)
 • how constant discussion and new initiatives can replace real improvement
 • why systems default to activity under pressure
 • and what leaders should actually be paying attention to instead

This isn’t about doing less.

It’s about making sure the work being done is actually moving the system forward.

Because if nothing is different… nothing has improved.

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:28

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. 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. Activity is easy to see. Meetings, reports, updates, new initiatives, emails going back and forth, calendars that are full from the beginning of the day to the end. And when all of that is happening, it feels like progress. It feels like something is moving. But a lot of systems are very active without actually improving. In this episode, I want to talk about the difference between activity and progress and why confusing the two can quietly keep systems stuck for a long time. Because the reality is activity creates motion, but progress creates change. And those are not the same thing. Activity feels like progress because it's it's it's visible. You can point to it, you can show it, you can report on it, you can say, We held this many meetings, we launched this initiative, we reviewed this data, we followed up on these items, and all of that sounds like movement, it sounds like effort, and it is effort, but effort and progress are they aren't the same thing. When something isn't working, the natural response is to do more, right? Schedule more meetings, ask for more updates, start something new, add another layer of review, increase communication because doing something feels better than sitting in uncertainty. You know, it gives you a sense of control, it gives the impression that we're responding. And in a lot of environments, visible efforts, visible effort gets rewarded. People who are busy, who are seen as engaged, as committed, and as contributing, so the system reinforces activity, not intentionally, but consistently. That never address the underlying issue. And over time, activity starts to replace progress as the thing that we measure. Because progress is harder to see, is quieter, it doesn't always show up immediately. Progress looks like consistency. It looks like fewer breakdowns, not more motion. It looks like people being able to predict what's what's gonna happen. What's gonna happen next. Progress changes the system, and progress doesn't always feel good in the moment. And that's another part people don't talk about because real progress often looks like slowing down, it looks like asking harder questions, it looks like sitting in uncertainty longer than people are comfortable with. It can look like fewer meetings, not more, fewer priorities, not more, more focus, but less visible motion, and that can feel like something is missing, especially in environments that are used to constant activity. But that's usually where the real shift starts, not when everything speeds up, but when something finally becomes clear enough to stabilize, activity fuels the time, fit it fills the time, um, and that distinction matters, right? Because if we don't separate the two, we can spend um a lot of energy moving without actually improving. One of the ways that this shows up is in constant discussion without resolution, the same topics come up again and again and again and again and again. The same issues get revisited, there's conversation, there's engagement, there's input, but nothing actually changes or decisions are made, but they're not sustained. They don't hold, they don't carry through the system in a consistent way, so the conversation comes back again and again. In another way this shows up is through new initiatives replacing unfinished work. Instead of asking what did we start that hasn't stabilized yet, the focus shifts to what's next, what's new, what's different. And over time, systems build layers, right? More processes, more expectations, more moving parts. But the foundation underneath never fully settles. Then there's reporting, more data, more dashboards, more tracking, which can be useful, but only if it's tied to something changing. Because if the reporting increases and the system stays the same, all we've done is document the problem more clearly. We haven't solved it. A busy system can still be can still be a stuck system. And what makes this harder is that activity doesn't just hide the lack of progress, it can actually protect it. Because as long as people are moving, it's harder to question whether anything is changing. If everyone is busy, if meetings are happening, if updates are being shared, then it feels like something is being managed. And once something feels managed, people stop asking deeper questions. Not intentionally, but because the surface looks stable. I've seen situations where there was constant communication, regular meetings, detailed updates, follow-ups happening exactly the way they were supposed to, and on paper, everything looked engaged, right? But when you step back and actually looked at the outcome, nothing really changed. The same issues were still there, the same delays, the same inconsistencies, the same confusion. And that's where activity becomes dangerous, not because people don't care, but because the system starts rewarding movement instead of results. That's one of the hardest things to recognize because from the outside it looks like everything is happening, but from the inside, people can feel that nothing is actually improving. So, why do systems default to activity? That's because activity is easier, it's easier to measure, it's easier to explain, it's easier to defend. You can show that something is being done. And when there's pressure, whether it's leadership pressure, external expectations, timelines, or performance concerns, doing something feels necessary. Slowing down to understand a problem can feel quite uncomfortable. It can feel like inaction. It can feel like delay. So systems move faster instead. They increase activity before they increase understanding. Not because it works better, but because it feels safer to them. When systems feel pressure, they increase activity before they increase understanding, and that's where things start to drift. Because without understanding, activity becomes disconnected from impact. You're doing more, but you're not necessarily doing what matters. Another reason systems default to activity is because activity spreads responsibility. Everyone is doing something, everyone is contributing in some sort of way, and that makes it harder to pinpoint where things are actually breaking down. But progress does the opposite. Progress concentrates responsibility, it forces clarity, it makes it clear what matters, what does it, and who owns what. And that can feel uncomfortable to a lot of people because now the system can't hide behind movement anymore. Now it has to answer to a different question. That question being, did anything actually change? Progress requires something different. It requires clarity, it requires deciding what actually needed to change, it requires staying with something long enough to see whether it works, and that's harder because it involves prioritization, right? It involves saying no to other things, it involves focus. It also requires follow-through, not just starting something, but sustaining it, reinforcing it, making sure it holds under pressure because most changes don't fail when they're introduced. When the attention shifts, when priorities move, when consistency breaks down. So if activity isn't the goal, what should leaders be paying attention to? Not how much is happening, but what is different? What is actually working differently today than it was before? Because if nothing is different, then nothing has improved. Even if everything feels busy. Because without that shift, systems stay in motion, but they don't move forward. Um what is more con what is more consistent? What is more predictable? What has stabilized? Leaders should be asking these these things. What did we change that is still holding? What have we stopped doing that used to create problems? Where were where are things breaking less often? And where is the system easier to navigate than it used to be? And just as important, what did we start that we haven't finished? What are we maintaining versus what are we just managing? And what breaks as soon as attention moves somewhere else? Because that's where the real work is. Not in starting something new, but in sustaining what matters. Progress usually comes from staying with something longer, not replacing it faster. That doesn't mean activity is bad, it has a place. Effort matters, responsiveness matters, but activity without direction can be just noise. And over time, that noise makes it harder to see what's actually working. Progress is quieter, it doesn't always get attention, it doesn't always get recognized, but it shows up in systems that function more reliably, in processes that don't need constant correction, in teams that understand what's expected and can execute consistently. Activity creates motion, progress creates change, and if we're not careful, we can spend a lot of time moving without ever getting where we're trying to go. So the next time things feel busy, it's worth asking, are we moving or are we improving? Because those are those aren't the same thing, and knowing the difference is what allows systems to actually get better. There's also something else that happens when activity replaces progress. Over time, people start to feel it, even if they can't always explain it, they start to feel like they're doing a lot without seeing results, like they're contributing but not changing anything, and that's where disengagement starts. It's not because people don't care, but because the connection between effort and impact, it's not clear anymore. And once that connection breaks, it's truly hard to rebuild because now the system is isn't just busy, it's tired. Activity has a place, effort has a place, responsiveness has a place, but movement alone doesn't create improvement. Progress comes from understanding the system, making intentional changes, and staying with them long enough for those changes to hold. Now what are we doing? Or not what not what are we doing, but what has changed. Because systems don't improve from motion, they improve from clarity, consistency, and follow-through. So the next time things feel busy, it's worth asking: are we moving or are we improving? Because those are not the same thing, and knowing a difference is what allows systems to actually get better. Next time I want to talk about why measurement can create false confidence if it's not understood correctly, and how leaders can avoid being misled by the numbers they rely on. Because the work doesn't end at the measure.