Stacy Kiebler The Unlikely Architect Of Modern Process Optimization

So You Want To Actually Fix Your Processes Instead of Just Talking About Them

I spent years watching companies throw lean terminology around like confetti at a parade. Value stream maps hanging on walls that nobody updates. Kaizen events that produced action items gathering dust. Then I started paying attention to what Stacy Kiebler The Unlikely Architect Of Modern Process Optimization actually did differently, and it was not glamorous. It was mostly just stubborn consistency applied to boring fundamentals. Most people approach process optimization backwards. They start by automating things. They buy software, they layer in dashboards, they get fancy with Six Sigma belts and DMAIC frameworks. What Stacy figured out early was that automation on a broken process just gets you broken at machine speed. The real work happens before any tool touches the floor. Here is how the method actually looks when you strip away the consulting gloss. You pick one process. Not ten. One. Then you document it exactly as it runs today, including all the undocumented workarounds people use because the official process does not account for reality. This part always surprises people. The documented SOP is almost never the actual process. There is always a shadow process running underneath it. You find it by talking to the people doing the work, not by looking at policy documents.

Once you have the real process mapped, you identify the constraints. Not the bottlenecks that operations management theory loves to obsess over. The actual constraints. Things that cause delay, rework, or quality escapes. You measure them in hours lost per week, not percentages on a slide deck. A process step that takes four minutes sounds fast until you multiply it by four hundred transactions per week. That is twenty-six hours you are silently burning. I remember a specific case at a mid-size manufacturing facility where the problem was not what anyone thought it was. Everyone blamed the shipping department for delays. The reality was that the billing validation step was sitting in an email queue waiting for three different approvers who all had different access levels to the ERP system. The fix was not more training for shippers. It was restructuring the approval workflow so one person with the right credentials could handle routine cases, and escalations were automated to ping the appropriate manager instead of landing in a shared inbox that nobody checked regularly. Cut the average validation time from fourteen hours to under three. That is the kind of thing nobody catches unless they trace the actual handoffs.

What Stacy Kiebler The Unlikely Architect Of Modern Process Optimization Actually Teaches

The framework is not complicated. It is just unglamorous enough that most organizations skip the hard parts. The core approach revolves around five operating principles that sound simple and stay simple if you actually apply them. First, you observe the work. Not from a spreadsheet. Physically or virtually, however the work happens. You watch how information flows, where it piles up, where people workaround the system. The second principle is measurement, but only on things that matter to the actual outcome. Lead time. Throughput. Error rate. Things you can act on, not vanity metrics that look good in reports. Third is standardization of the current best practice, not the theoretical best practice from a textbook. Fourth is iteration. You make a change, you measure the result, you decide whether to keep it or move on. This loop is where most people fail. They make one improvement and declare victory. The process degrades within sixty days because nobody reinforced the change or tracked whether it actually stuck. Fifth is scaling what works. You do not roll out a fix across the organization until it has been validated multiple times on the same type of process. Repetition beats ambition every time.

There is a counter-intuitive insight here that beginners miss consistently. The biggest gains rarely come from the obviously broken parts of a process. They come from the smooth-running sections. This is because smooth processes accumulate small frictions invisibly. A document that is sent manually between departments because someone decided it needed a signature. A meeting that happens weekly because it always has, not because anyone recently determined it added value. These micro-frictions compound quietly. They do not trigger alarm bells. By the time you notice them, they represent massive cumulative waste. The places that look fine are where you should be looking most carefully.

The Practical How-To

If you want to apply this yourself, start with a process you touch directly. Something you understand well enough to spot anomalies. It could be a customer onboarding sequence, an invoice approval flow, a procurement request pipeline, whatever. Write down every single step from start to finish as it currently exists. Include the steps that are not in any official documentation. Include the email chains, the verbal handoffs, the spreadsheets that exist only in one person's head. Next, timestamp each step. How long does it actually sit before someone acts on it? You will be surprised how much time lives in the waiting, not the doing. Then map the decision points. Where does the process branch? How often does each branch get taken? What triggers a return or rework loop? These decision points are usually where the real delays hide. After that, calculate the total cycle time and identify which single step or handoff consumes the most calendar time. Pick one. Do not try to fix everything at once. For that one constraint, draft a change. It should eliminate a step, reduce a handoff, or automate a decision that requires human judgment only because nobody built a rule to handle it. Implement the change on a small scale first. Three weeks of observation. Measure the same metrics you measured before. If the numbers moved in the right direction, document the new standard. If they did not, revert and try a different approach. Do not attach your ego to any particular solution. The process will tell you what works if you actually listen to the data instead of defending your idea.

One thing I learned the hard way: the people doing the work know exactly where the friction is. They also know ways to reduce it that will never appear in any formal analysis. I once spent two weeks designing an improved workflow on paper before an operator pointed out that the whole redesign would break because a downstream system they relied on had a hardcoded cutoff time at 3 PM that nobody documented. A ten-minute conversation saved us two weeks of wasted effort. Budget time for those conversations. They are more valuable than any analytical model.

Where This Approach Breaks Down

Process optimization of this type does not work everywhere. It fails in organizations where leadership treats it as a cost-cutting exercise rather than a value-creation exercise. When people hear "optimization," they hear "layoffs." Morale drops. People hide problems instead of surfacing them. The whole method collapses because you cannot improve a process when the people running it are afraid to admit what is actually wrong with it. Be honest about that. If your culture punishes visibility into failures, this approach will not work until you fix the culture first. It also breaks down when you try to optimize interconnected processes in isolation. Change one piece and watch it destabilize another. I have seen teams optimize a purchasing approval process so aggressively that it caused inventory shortages upstream because the procurement timeline no longer aligned with demand forecasting. You need at least a basic understanding of how your process connects to adjacent ones. A narrow optimization that creates a wider problem is not an optimization. It is a trade-off dressed up as an improvement. For organizations that need something more structural than incremental process tweaks, looking into supply chain orchestration tools or enterprise workflow platforms might be more appropriate. Those sit at a higher abstraction level and can handle cross-functional complexity that manual optimization methods struggle with. But even those tools require clean underlying processes to be effective. Garbage in, garbage out applies here just as much as anywhere else.

If you want practical resources on this methodology, searching for Stacy Kiebler The Unlikely Architect Of Modern Process Optimization will surface articles, case studies, and speaking recordings that go deeper into the operational techniques. The core idea is not proprietary. It is discipline applied to boring work. The payoff comes from doing it consistently across multiple processes rather than treating it as a one-time initiative. That is the part most organizations never figure out. They run a single lean event and move on to the next shiny problem. The optimization was never the event. It was the habit.