Every operational process in your organization was designed for a previous era. Some were designed for paper-based workflows and never fully adapted to digital. Some were designed for lower volumes and don’t scale efficiently. Some were designed around specific people and don’t work when those people leave. Yet you can’t stop operations to redesign them, and you can’t afford the risk of transformation projects that disrupt service delivery.
I’ve rarely met an operational leader who believes their processes are perfect. Most workflows were designed for a different scale, a different set of tools, or a different team structure. They’ve been patched and adapted over time. Everyone can see the friction. What’s harder is deciding how to improve them without disrupting the business that depends on them.
In my experience, the instinct is often toward big transformation — a clean redesign, a new system, a visible “before and after.” There’s something reassuring about that narrative. It feels decisive. But it’s also risky. Large, coordinated change introduces uncertainty at exactly the moment service continuity matters most. So organizations either attempt sweeping transformation and struggle, or postpone it and live with the inefficiencies.
What I’ve found more interesting is the tension around incremental change. Operationally, it’s safer. You pilot a new workflow with one team. You instrument the current process before changing it. You test a small adjustment, measure the impact, and scale what works. But psychologically, it’s harder. There’s no grand finale. Instead, it’s a steady rhythm of improvement — slightly faster cycle times, slightly lower error rates, slightly higher customer satisfaction. It requires admitting that the system will never be “done.”
The teams that seem to make progress don’t just change processes; they make progress visible. They connect a 10% reduction in resolution time to customer retention. They show how fewer handoffs translate into lower cost-to-serve. They measure behavior change — not just whether a new workflow exists, but whether people are actually using it. And they create feedback loops so teams can see the results of adjustments within weeks, not quarters.
I’m not convinced there’s a universal formula for this. But I do think the question shifts from “How do we transform operations?” to something more practical: where is the friction highest, and what’s the smallest safe experiment we could run to reduce it? Over time, those experiments accumulate. The business keeps running. And the process evolves — not through a single dramatic overhaul, but through many visible, accountable steps forward.
Leave a Reply