EMERGENT FrameworkMomentum through WorkCultivating conditions
Dimension M - Momentum through Work

Cultivating conditions

You cannot manufacture momentum. It is an emergent property. But certain patterns keep showing up in organisations where work genuinely flows.

You can't manufacture momentum. It's an emergent property - it arises from conditions, not from acceleration. But in our work with organisations, certain patterns keep showing up in the ones where work genuinely flows. Not as a formula, but as observations about what seems to matter.

Busyness and momentum are not the same thing. This is perhaps the most important distinction in this whole dimension. Busy organisations are everywhere. Organisations with genuine momentum are rare. The difference is whether energy is moving toward outcomes or just being spent. We've worked with organisations where people worked incredibly hard and very little moved. And organisations where things flowed with an ease that belied how much was actually being accomplished. The busy ones always felt stressed. The ones with momentum felt alive. When we looked at what separated them, it was almost never about effort. It was about friction. The busy organisations had accumulated layers of process, approval, reporting and coordination that absorbed enormous energy without producing forward movement. The ones with momentum had somehow kept those layers thin. Not by being careless, but by being intentional about what was genuinely necessary.

The people closest to the work know where the friction is. Almost without exception. Ask anyone doing frontline or operational work where things get stuck and they'll tell you in precise detail. The handoff that loses information. The approval that adds three days and no value. The report nobody reads. The meeting that could be an email. This knowledge is everywhere in organisations and almost never reaches the people who could act on it. Not because anyone is hiding it, but because there's no mechanism for it to travel. One of the most powerful interventions we've seen is simply creating the conditions for that knowledge to surface. One organisation asked every team to identify the three biggest sources of friction in their daily work. The list was painful to read and transformative to act on. Most of the friction had been invisible to leadership. All of it had been visible to the people living with it.

Momentum is lost at the transitions. Work tends to flow reasonably well within teams. The problems accumulate at the boundaries - where one team hands off to another, where a process crosses departmental lines, where responsibility shifts. These transition points are where information gets lost, where things sit waiting, where nobody quite owns what happens next. If you want to understand an organisation's momentum, don't look at how work moves within teams. Look at how it moves between them. One organisation mapped the journey of a single piece of work from initiation to completion and found it crossed seven team boundaries. At each one, it paused. The total transit time was four months. The total time anyone was actively working on it was about three weeks. The rest was waiting. Nobody had designed that delay. It had just accumulated at every boundary, invisible until someone traced the whole journey.

Removing friction is more powerful than adding speed. There's a common instinct when work isn't flowing: work harder, go faster, add urgency. But momentum isn't about speed. It's about the ratio of effort to movement. Adding speed to a system full of friction just burns people out faster. Removing friction from a system where people are already motivated creates movement that sustains itself. The distinction matters because the interventions are completely different. Speed requires pressure. Momentum requires clearing the path. One organisation we worked with had tried everything to move faster - tighter deadlines, more oversight, escalation processes. All it did was increase stress. When they shifted to removing friction instead - simplifying approvals, reducing handoffs, eliminating duplicate work - they achieved more speed than any amount of urgency had produced. And it felt entirely different.

The system creates the behaviour, not the other way round. When work doesn't flow, it's tempting to look at people. Why aren't they more efficient? Why don't they manage their time better? Why do things always take so long? But in almost every case we've seen, the behaviour is a rational response to the system. People work around obstacles because the obstacles exist. They duplicate effort because the system doesn't share information well. They escalate because the system doesn't give them confidence to decide. Fix the system and the behaviour changes. We've watched this happen so many times it's become one of our most reliable predictions. Change the conditions and the people will move. They were always ready to.