FreeNo sign-upYour notes stay on your computer

Kaizen Blitz Planner

Plan a short improvement event on one step, or record a quick fix: the measure before and after, the team, the week, the new standard with its owner, and the check 30 days later.

How will you make the change?

Point the event at the constraint and nothing else: the one step that holds the process up.

The measure

One number that shows whether the change worked, measured before and after.

Better is

The event

Narrow. Nearly every failed event can be traced to a scope nobody was willing to narrow.
Length

The team

  • The people who do the step, one person from the step before it and one from the step after.
  • Someone with the authority to change a form or a rule on the spot. Six to eight people is enough.

Your notes never leave your browser

The team, the notes and the new standard stay on your computer and in your progress file. To write the diagnosis, only the numbers and which fields are filled are sent to our server. How it works

About the tool

Why it exists

Change one step this week, and make sure it stays changed

A Kaizen Blitz is a short, focused improvement event, usually five days, in which a team from every function the step touches scopes, measures, tests and puts in place a change to one process before the week ends. Most gains from these events fade within months, so the event's real end is a check 30 days later.

This tool works on its own, and as stage 3 of our playbook for speeding up a slow business process, where it picks up the constraint and the plan from stage 2. For the method, see our guide to the Kaizen Blitz.

The method

How the tool works

An event or a quick fix. A rule, or a small and obvious fix, needs no event: write the change down, give it an owner and check it after 30 days. Anything else gets a short event with the people who do the step.

The team. The people who do the step, one person from the step before and one from the step after, and someone who can change a form or a rule on the spot. The tool flags a team without the step's own people or without that authority.

Tested, then written down. The change is tried on real items during the event and measured. By the last day it is written down as the standard, with one owner, and the 30-day check is booked.

The 30-day check. Come back with your progress file and answer two questions: is the standard still followed, and where is the measure now? The tool says whether the gain held, is slipping or has faded.

What leaves your computer. The team, the notes and the standard stay in your browser and your progress file. To write the diagnosis, the page sends our server only the numbers and which fields are filled, and the server keeps nothing.