An organization finally agrees that a process needs work. Within one meeting, the project expands to include every department, three software platforms, a policy rewrite, new reporting, and a reorganization.
Six months later, the original problem is still there—now buried under an exhausted transformation program.
To heat up water for some tea, you don’t have to boil the ocean.
Scope is an operating decision. Too little scope treats a symptom and leaves the cause untouched. Too much scope creates so many dependencies that the team can’t tell which change helped, which change hurt, or which change never happened.
The answer is not thinking small. It’s choosing a meaningful unit of improvement.
Start with an outcome the organization cares about: faster customer onboarding, fewer billing corrections, a reliable approval, cleaner service handoffs, or less time spent finding information. Follow the work closely enough to identify the constraint that most directly affects that outcome.
Then define the boundary. Which part of the process will change? Who will participate? What stays outside the effort for now? What measure should move? What condition would cause the team to stop, correct, or reverse the change?
Boundaries protect the work from enthusiasm. Improvement programs often fail because every good idea earns a place in the first release. The team becomes unable to finish, the operation carries half-built changes, and employees learn that improvement means disruption without relief.
One controlled change creates better evidence. If a team simplifies one approval path and lead time improves without increasing error, leaders have learned something useful. They can stabilize the change, document it, and decide where the principle applies next.
That last step matters. A pilot isn’t success if it becomes another permanent exception. The organization needs to decide whether to adopt, adjust, expand, or retire the change. Document the decision. Update the source of truth. Train the people affected. Remove the old path when the new one is ready.
Continuous improvement also requires capacity. If employees must improve the system only after completing a full day inside the broken system, urgent work will win. Leadership has to fund attention—not merely endorse the idea.
Strategy is what you fund when nothing is on fire.
That funding may be protected time, access to data, temporary coverage, decision authority, or a modest technology investment. It doesn’t have to be extravagant. It has to be real.
The strongest improvement cultures aren’t running a permanent parade of initiatives. They’re building a repeatable habit: see the work, choose the constraint, control the change, measure the result, and preserve what was learned.
Pick one cup of water. Heat it with discipline. Then decide what deserves attention next.
Wentworth Consulting Group, LLC helps organizations choose a consequential starting point, control the change, and turn a focused improvement into durable operating capability.