How to Run a 30-Day Continuous Improvement Pilot

Why 30 days, and why one problem

Thirty days is long enough to run several real PDCA experiment cycles and see a metric actually move, and short enough that the team stays focused and the pilot doesn't quietly turn into an open-ended initiative. Picking exactly one operational problem, not a portfolio of them, is what makes that possible — it's the same “work one obstacle at a time” discipline that Toyota Kata applies at the daily level, scaled to a pilot.

Week 1: Define and baseline

Pick a problem that's real, measurable, and already matters to someone with the authority to act on it — late shipments, picking errors, changeover time, whatever is actually costing the team time or money right now. Write the direction/challenge in one sentence. Then pull the actual current-condition number from real data, not a guess: today's on-time percentage, today's error rate, today's cycle time. Set one specific, dated target condition for day 30 — ambitious enough that you don't yet know exactly how you'll get there.

Week 2: Name the obstacle and run the first experiment

Brainstorm every obstacle standing between the current condition and the target, and park all but one. Choosing the single most limiting obstacle right now — not the easiest one, not the whole list — is the step most pilots skip, and it's the one that keeps the team from spreading effort too thin. Log a hypothesis for a small experiment against that obstacle: what you'll change, what you predict will happen, and exactly how you'll measure the result. Run it before the week is out.

Week 3: Check, decide, and run a second cycle

Compare the actual result against the prediction, honestly — a result that doesn't match the hypothesis is not a failed pilot, it's data. Decide: adopt the change, adapt it and try again, or abandon it and move to the next obstacle. Either way, run a second PDCA cycle this week. A 30-day pilot that only completes one experiment hasn't really tested the habit yet — the value comes from repeating the loop.

Week 4: Third cycle, and an honest look at the target

Run a third experiment cycle against whichever obstacle is currently active. By now the current-condition trend line should be visible, even if the target condition isn't fully hit yet — that's normal and expected. Close the pilot with a real summary: what the current condition actually is now versus day 1, which experiments were adopted, adapted, or abandoned, and what the next target condition should be if the team keeps running the loop.

Common ways pilots quietly stall

• Picking a problem too broad to measure weekly, instead of one specific metric.
• Working the whole obstacle list at once instead of exactly one at a time.
• Skipping the “Check” step — running the experiment but never honestly comparing the result to the prediction.
• Letting week 1's energy be the only cycle that actually happens.