Prepare a Kaizen Event That Actually Changes the Work

The workshop that goes nowhere

A team can spend days naming a problem and leave with no change to test. Dr. Tom DePaoli’s Kaizen Kreativity presentation argues for a more useful kind of event: focused, engaging, and connected to work people actually do. Preparation begins before the meeting. Choose a process narrow enough to observe, and invite the people who perform it. Ask what a customer needs from that process and what employees encounter while trying to provide it. A broad ambition such as improve communication is hard to examine. A specific task, such as handling a request that routinely comes back incomplete, gives the team something it can follow from start to finish. The event should begin with a real case, not only a diagram.

Bring evidence into the room

Tom describes tools such as SIPOC and process maps, along with the voice of the customer and the voice of the employee. Use them to make the present process visible without letting the preparation become a second project. Walk a few examples beforehand. Record where the work changes hands, what information is missing, and which approvals repeat a decision someone already made. Check the map with people at both ends of the process. An employee may know an exception the official procedure ignores; a customer may experience the delay differently from the team producing the work. Those differences are worth bringing into the room. A useful map is a shared question about reality, not a decorative answer.

Leave with one test

During the event, ask which step adds no value to the result and which obstacle the team can address now. It may be possible to simplify a form, clarify a handoff, or remove an unnecessary approval. Choose an owner and a date for testing the change. Tom’s presentation uses familiar examples to make improvement tools approachable, but the event must still produce an action someone can carry into the next working day. Do not let a long list of aspirations substitute for one implemented change. If a proposed fix affects another group, include them before declaring the process improved. Their work is part of the same chain, even if it was not visible on the first map.

Check what changed

Return to the process after the test. Did employees spend less time repeating a task? Did the customer receive what was needed? Were there new delays or confusing exceptions? Share the result with everyone who contributed, including a finding that the first idea did not work. That honesty helps make improvement a habit rather than an occasional event. Tom’s book offers a fuller field manual; the presentation introduces his practical and creative approach. Use it to ask a team what they would change if fear of making a foolish suggestion were removed. Then give one suggestion a fair test and review it together. The event earns its place in the calendar when the people doing the work can point to what changed afterward.

If the first test succeeds, document it in language a new employee can use. A better process should not depend on the memory of the people who attended one workshop. If the test fails, keep the evidence and ask what the team learned about the original problem. The second attempt may need a different handoff or a smaller scope. Improvement remains creative when the team is allowed to learn in public.

Hear Dr. Tom explain the idea in the book presentation, then explore the book for the full account.