Reading time: ~7 min
If we run problem solving training for our team, we already know the trap. The room expects clarity. We have 60 minutes — sometimes two hours. Half the participants are sceptical, the other half have heard the 5 Whys / Fishbone / PDCA lecture three times and are waiting to see if we’ll add anything new. By slide three, we either earn the room or we lose it.
This article is the facilitator’s blueprint we run when delivering Kobetsu Kaizen problem solving training to clients: the run-of-show, the four objections we always hear, the daily routine the training has to leave behind, and the deck-and-handout pack itself. The pre-built deck and handout live inside the Samurai Problem Solving course — the Samurai-tier course is purpose-built to make problem solving survive the trainer. For the foundational definitions, the pillar guide on problem solving methodology feeds the slides straight in.
What “problem solving training” actually has to deliver
Most problem solving training decks fail because they teach techniques (5 Whys, Fishbone, A3, PDCA) as five neat boxes, then send people back to a workplace that proves none of it sticks. The deck looks complete; the team’s wrong-problem rate stays at 60%. We’ve watched this enough times to know the failure mode is structural.
A working problem solving skills training for employees — or training for problem solving in any operational context — has to deliver three things, in this order:
- Why problem-solving methodology exists. Not the techniques. The order of operations — observe before interpreting — that prevents solving the wrong problem.
- The 3-step working approach with the cost of getting the order wrong. 3G observation → 5W2H Meta Probe → Define the real problem. Skip 3G and the rest is theatre.
- What changes Monday morning. The daily 15-minute 3G drill, the weekly Meta Probe, the metrics. Without these, the training is a slide deck.
If our deck doesn’t cover all three, we’re delivering theatre. We’ve watched well-designed corporate sessions fail because they skip step three.
The 60-minute facilitator run-of-show
This is the part most problem solving training content skips. Here’s the run-of-show for the 60-minute session, beat by beat:
| Time | Beat | What we say / do |
|---|---|---|
| 0:00–0:05 | Opening hook | “Someone in this room has run a 5 Whys against the wrong problem. That’s the cost of solving fast instead of solving right.” Establish the stakes. |
| 0:05–0:15 | Why most training fails | The wrong-problem rate. Skip 3G and the analysis is fiction. Use a real workplace photo. |
| 0:15–0:35 | The 3-step working approach | 3G → 5W2H Meta Probe → Define. One concrete example per step, pulled from the room’s industry. |
| 0:35–0:45 | The daily 15-min routine | The 3G drill. Walk the slide. Make the timing concrete. |
| 0:45–0:55 | Three patterns that make it stick | Daily 3G, weekly Meta Probe, monthly mentor review. Get the room to commit to who owns each. |
| 0:55–1:00 | Close | One real problem per attendee, scoped, written down, before they leave. |
For a 2-hour session, double the time on the 3G + Meta Probe and add a problem solving training course segment — pull two real problems from the room and run a live Meta Probe on them. The room will object the first time. That’s the data.
The four objections we always hear (and what we answer)
Every problem solving training session has the same four objections. We answer them ahead of time:
- “We already do 5 Whys.” Yes — and your wrong-problem rate is probably 50–70%. 5 Whys is a technique, not a methodology. We’re going to install the order that decides when to use it.
- “This is too theoretical for our floor.” It’s the opposite. Theory is the textbook ‘define the problem first’ framework. The 3G drill is concrete: 15 minutes at the Genba, every shift. The textbook is the abstract version.
- “We don’t have time for a 15-minute daily check.” We don’t have time NOT to. The wrong-problem rate burns weeks. Fifteen minutes a shift buys back days.
- “Our problems aren’t on a shop floor.” The five steps don’t care about the surface. An office incident, a service-desk ticket, a software defect — same logic. Different room, same observation discipline.
Have these answers ready. The room will ask.
What separates a problem solving training session that works from one that doesn’t
After running problem-solving sessions for fifteen years, three patterns separate the deliveries that stick from the ones that don’t:
- A real problem from the room — theirs, not ours. Pull a current incident, a complaint, a metric drop. Run 3G + Meta Probe live. Watching their own problem reframed is what installs the method.
- A 30-day follow-up date in the calendar before everyone leaves. Without it, the training is forgotten by Friday. The follow-up is a 60-minute review of three real problems the team ran through the method since session one.
- The deck-and-handout pack in the room’s hands at the start, not the end. People who hold the page during the session retain more. The handout is a working surface, not a takeaway.
If we don’t deliver these three, we’re not training anyone. We’re running a slide deck. Different products.
The deck and handout we use (and where to access them)
The problem solving training ppt we deliver — the one that lives inside the Samurai Problem Solving course — is twelve slides. The structure mirrors the working logic above:
- Slides 1–2 — the wrong-problem hook (why most teams solve fast instead of solving right)
- Slides 3–4 — the 3-step working approach overview
- Slides 5–7 — Step 1 (3G) with one micro-example each from factory, office, service
- Slides 8–9 — Step 2 (5W2H Meta Probe) with the form
- Slide 10 — Step 3 (Define the real problem)
- Slide 11 — the daily 15-min drill + weekly Meta Probe + monthly review
- Slide 12 — first-week action plan
The deck is editable. Swap our examples for your operation. Replace logos. Cut slides that don’t apply. Reading this article is enough to build a working version of the deck from scratch; if we want ours — already designed and tested across hundreds of sessions — it lives inside the Samurai Problem Solving course at a price that’s effectively a coffee.
The accompanying problem solving training pdf handout is two pages:
- Page 1 — the 3-step working approach with the visible-standard test
- Page 2 — the first-week action checklist (10 items, scoped to one real problem)
Distributed at the start of the session, not the end. People retain more when the handout is a working surface during the session, not a memento after.
In short
- Working problem solving training delivers three things: why methodology exists, the 3-step working approach, and what changes Monday morning.
- The 60-minute facilitator run-of-show is timed beat by beat — opening hook, why most training fails, the 3-step approach, the daily routine, the three sticky patterns, close.
- Anticipate the four standard objections; have one-line answers ready.
- The session sticks only if (a) we use a real problem from the room, (b) we book a 30-day follow-up before everyone leaves, (c) the handout is in their hands during the session, not after.
- The pre-built deck and handout live inside the Samurai-level Kobetsu Kaizen course. Reading this article is enough to build them yourself; the Samurai pack is the editable, tested version.
FAQ
Q1: What is problem solving training and how is it different from a generic course? A1: Problem solving training teaches an order of operations — observe before interpreting, align meaning, define the real problem — before drilling techniques. A generic course teaches techniques (5 Whys, Fishbone, A3) without the order. The order is what decides whether the techniques work. Generic courses produce certified people who still solve the wrong problem.
Q2: How long should a problem solving training session be? A2: A focused first session runs 60 minutes. A deeper session — with industry-specific examples and a live Meta Probe on a real problem from the room — runs 2 hours. One session alone won’t change behaviour. Schedule a 30-day follow-up before the room leaves; that’s the session that turns information into routine.
Q3: Where can I get a free problem solving training PPT and PDF? A3: The Ronin-level Kobetsu Kaizen course on Lean Trainings is free and walks through the working version of problem solving in three short modules. The editable deck and the two-page handout used to deliver client sessions live inside the paid Samurai course at a low one-time price. Reading the pillar article on problem solving methodology gives enough structure to build your own deck from scratch.
Q4: What are the most common objections in problem solving training? A4: Four show up every time: “We already do 5 Whys” (technique vs methodology); “This is too theoretical for our floor” (the textbook is the abstract; 3G is the concrete); “We don’t have time for a daily check” (the wrong-problem rate burns weeks); “Our problems aren’t on a shop floor” (same logic, different room). The session stands or falls on whether we can defend the method against scepticism.
Q5: Can a single training session change behaviour? A5: No. One session is information. Two sessions, separated by 30 days, with a live review of real problems the team ran through the method between them — that’s behaviour change. Book the 30-day follow-up before the first session ends. Without it, the wrong-problem rate stays where it was.
The blueprint above is enough to run a credible problem solving training session next week. If we want the deck and handout we actually use — already designed and tested across hundreds of sessions — they live inside the Samurai Problem Solving course, purpose-built to make Kobetsu Kaizen survive the trainer. The free Ronin Problem Solving course is the natural starting point if we want the method first, the assets second. Start the free Ronin Problem Solving course → · See the Samurai Problem Solving course →
