Article

Effort Is Not Momentum

By Jeff Harding · 4 min read · Adapted from Designing Momentum
← All insights

Most organizations do not fail because people stop working. They fail because effort gets mistaken for progress.

If effort alone produced durable success, exhaustion would be a competitive advantage. The longest hours would win. In practice the opposite is often true. Some of the hardest-working teams are in constant motion while nothing compounds.

Early in my consulting work, I sat with an owner who ran the same process every month. His data team handed him a raw revenue file. He blocked three hours, closed his door, and worked it in Excel: sorting, cross-referencing, surfacing the numbers his leadership team needed. The work was careful. The output was accurate. His leaders relied on it.

No one had asked the obvious question. Why did it never get easier?

Every month reset to zero. Three hours in, three hours out. Nothing carried forward. The effort produced the report and left nothing behind. The system never learned from its own success.

When I watched him work through it once, I did not see a skill problem or a discipline problem. I saw a design problem. The process had been built to produce a result, not to compound one.

I asked for the raw file and his finished version. A day later I sent back a macro that did the whole thing at the press of a button. Three hours became twenty minutes, most of it his own thinking.

His reaction was not excitement. It was relief. For the first time the process gave back what it had quietly been taking: the space to do the work only he could do, to tell the story behind the numbers and drive decisions instead of formatting them.

The macro did not make him work harder. It made his effort count differently.

Why effort feels like enough

Effort is visible. It fills calendars, justifies budgets, and gives instant feedback. You can point to initiatives and say things are happening. Momentum is quieter. Early on it rarely looks impressive. It shows up as small improvements that make the next thing easier. One decision lowers the cost of the next. One investment reduces future friction. Over time those effects accumulate.

That is the real difference. Effort produces linear results: push harder, get more; stop pushing, and the gains decay. Momentum exists when today's output becomes tomorrow's input, when success reduces the effort required for the next success. Customer trust lowers the cost of the next sale. Operational clarity shortens the next decision. Capability built in one person reduces how much the business depends on that person being in the room.

These effects only compound when they are connected on purpose. Most organizations never get there because their wins stay isolated. Projects succeed, but success in one place does not make anything else easier. Each effort carries its own weight. Energy dissipates instead of accumulating.

The shift that matters

When work stops compounding, leaders usually diagnose the wrong problem. They assume it is execution, motivation, or talent. It rarely is. It is design.

The most important shift in leadership is not from contributor to manager, or manager to executive. It is the shift from rewarding effort to designing momentum. That shift takes restraint. It means saying no to work that feels productive but does not compound, and staying patient while systems develop and early results look modest.

The payoff is a different kind of business. Decisions get cleaner. Tradeoffs get clearer. Effort starts to earn interest.

Effort can start movement. Only momentum sustains it.

Where in your work is effort producing output but leaving nothing behind?
From the book

This piece is adapted from Designing Momentum.

How leaders build progress that compounds. The book lays out the full model for building, scaling, and governing momentum over time.

See the book