Smaller Changes Create Smaller Risks

A companywide remake can concentrate risk. You change many things at once. If the week gets worse, you cannot tell which change did it. If something breaks, reversing course means undoing a web of decisions, trainings, and tool settings that were sold as inseparable. Focused changes work the other way.

When the intervention is one process, the impact of getting it wrong is more contained. You can test the change against the actual work. You can adjust without rewriting every department's week. You can reverse it if the evidence says you guessed wrong. That is not caution for its own sake. It is how you keep learning while the business keeps running.

Small here means the scope of the intervention, not the importance of the issue. The Cotomic idea is not an easy tweak that leaves the real gap untouched. It is the smallest change capable of meaningfully improving the problem being investigated. Fixing how a job moves from request to schedule can still touch customers, cash timing, and employee stress. The change is contained. The stakes do not have to be trivial. Contained scope is what keeps the risk manageable.

In a service business, swapping every tool at once might feel decisive. It also multiplies failure modes: intake, scheduling, field updates, and invoicing all move together. If status calls rise and invoices slow, you are left arguing about the whole package. Change the intake field that was creating the missing code, and you can watch that week. If it helps, keep it. If it does not, you have not disrupted the rest of the operation to find out.

Karl Weick's small win idea fits here in a practical way: a concrete, complete outcome of moderate importance is finishable. Finishable changes are also easier to judge. For COT, that matters because you can get evidence before you expand the change.

Large programs sometimes are necessary. When they are not, using them as the default raises the cost of being wrong. You spend political capital, money, and attention on a remake that may not address the cause you never isolated. A focused change asks less of the organization up front and returns a clearer answer: did this process get better?

Risk does not disappear when scope shrinks. A bad change in a critical process still hurts. What shrinks is the uncertainty about cause and effect, and the cost of correcting course. That is why smaller changes create smaller risks: not because the problems are unimportant, but because the intervention stays in a size you can test, adjust, and, if needed, reverse—without turning the whole company into the experiment.