We are planning our first big Lean rollout and I want to make sure we pick the right area to start. I've heard that picking the most broken process is a recipe for disaster, but picking the easiest one doesn't get enough attention. What is the sweet spot? Are there specific criteria I should use to ensure our pilot project generates enough momentum to win over the rest of the company?
The ideal pilot project for a Lean rollout is a high-visibility, medium-difficulty process with accessible data, supportive local leadership, and the potential for measurable operational improvements within a short timeframe.
5 answers
To select an appropriate pilot project, you should prioritize areas that satisfy the following criteria to ensure scalability and buy-in.
- Choose a process with readily available, accurate performance data.
- Select a team or manager who is enthusiastic about the change rather than resistant to it.
- Pick a problem that produces a measurable financial or operational gain within 30 to 60 days.
- Identify a high-visibility process where stakeholders outside the pilot can see the transformation.
The sweet spot for a pilot is a process that has visible pain, willing stakeholders, and measurable data, but isn't so broken that it requires a total structural overhaul to see a win. Aim for a high-impact, medium-difficulty project where your team can actually prove value without spending months fighting fires or legacy technology.
I recall a startup phase where we targeted an entire assembly line for a Lean pilot, thinking that breadth would demonstrate commitment. It was a disaster because the scope was too wide to manage effectively, and we lost the attention of the front-line workers within two weeks.
We pivoted to a single, critical sub-assembly station that was frequently bottlenecked. By focusing on that one point, we were able to document clear improvements in cycle time and error reduction, which served as the evidence we needed to sell the methodology to the rest of the facility later.
Choosing between a broken process and an easy one is a classic false dichotomy. A deeply broken process is a graveyard for momentum because the systemic issues usually exceed the scope of a pilot, leading to fatigue. Conversely, an easy win provides no real insight into whether your Operational Excellence framework can actually handle complexity. The ideal candidate is a process that is stable enough to be measured, but frustrating enough that people are actively seeking a better way to do things.
Stay away from the most broken areas. If the house is burning down, don't try to reorganize the furniture. You want a process that is important enough for leadership to notice but simple enough that you can finish it before people get bored. Focus on getting a quick, documented win to build credibility.
Todd Matthews, your advice on picking small wins is noted, though I worry about selecting the wrong process and failing. I suppose focusing on documentation is the best way to stay safe.


I appreciate your transparency, Arin Bhardwaj. It is quite daunting to consider the scope of these pilots, but focusing on a single bottleneck seems like a much safer, more manageable approach.