Runaway Treadmill

The diagnostic found an organization that is working extremely hard and moving slower than it should. The people are clearly capable, but a significant portion of their effort is going toward sustaining the activity itself rather than producing the outcome it was designed to produce.

The Runaway Treadmill has a specific origin story, and it almost always starts with success. Growth organizations develop activity patterns that work. Those patterns get repeated, systematized, and eventually institutionalized -- because the people inside them are rational, and codifying what works is rational behavior. The problem arrives when the organization changes but the activity patterns don't.

What worked at twenty people gets formalized at fifty and becomes load-bearing at a hundred, long after it stopped being the right answer. The research on organizational complexity is consistent: as organizations grow, the coordination cost of managing existing activity rises faster than the output that activity produces. The work expands to fill the structure built to contain it.

The treadmill isn't broken. It's a treadmill. The question is whether the organization is willing to get off it.

The first action is building an accurate picture of where the effort is actually going -- not the official version from the project tracker, but the real version, mapped against the outcomes each activity is producing. That audit is almost always clarifying. The activities consuming the most energy are rarely the ones producing the most value.

The instinctive response to a Runaway Treadmill is to add a prioritization initiative -- to layer a new framework on top of the existing activity and ask people to start saying no more. The organizations that try that approach discover, usually within a quarter, that they have successfully added one more thing to the treadmill. What actually works is subtraction.

From there, the work is about building the organizational permission to stop. That sounds simple. It requires more deliberate effort than most leaders expect, because the activity patterns on a Runaway Treadmill have stakeholders -- people whose roles, metrics, and identities are tied to the continuation of the thing being questioned. Navigating that requires a clear rationale, careful sequencing, and someone who knows where the resistance will come from before it arrives.

The Roadmap provides the structure for that work: a clear sequence of what gets stopped, what gets simplified, and what gets protected, with the organizational logic for each decision documented well enough that it holds without requiring the leader to re-explain it every time.

The resistance on a Runaway Treadmill is almost entirely identity-based. The people running the activities that need to stop built those activities. They've been delivering against them for years. Being told that the delivery is no longer the point requires them to reframe their own contributions in a way that feels like loss before it feels like gain.

There's also a risk-aversion pattern that's common in organizations that have been busy for a long time: the fear that stopping something will break something else. On a mature treadmill, some activities have become genuinely load-bearing, and sorting those from the ones that just feel load-bearing requires the kind of honest organizational inventory that busy organizations rarely make time for.

The Roadmap addresses both. The sequencing is designed to surface the genuine dependencies before the cuts happen, and to create a narrative for the people affected that's honest about what's changing and why.

The organizations that come out of a Runaway Treadmill engagement well don't just run leaner. They run with a clarity about what they're actually trying to accomplish that the treadmill had been obscuring for years.

That clarity is also motivating. People work harder when they can see what the work is for. The calendar that never emptied starts to have white space in it. The team that was simultaneously exhausted and behind starts making progress on things that had been stalled for quarters.

Most leaders describe the same experience six months out: they wish they had done it sooner. The activities they were afraid to stop turned out not to matter as much as the treadmill had made them feel. What mattered was getting the organization's attention pointed at the right things.