The short answer: problem solving case studies are short, realistic workplace scenarios that a team reads, discusses and decides on together, instead of sitting through a lecture about techniques. A complete set trains the five domains disciplined problem solving actually runs on: defining the problem precisely before touching solutions, digging honestly to the root cause, splitting a tangled problem into testable parts, verifying that a fix actually worked, and converting one solved problem into a pattern the whole organisation can reuse. The free Problem Solving toolkit gives you ready-to-run sample cases from a 30-case collection, with facilitator prompts, analysis worksheets and an action-plan template, so you can run your first 90-minute session this week. Download the free toolkit here.
Why case studies work better than lectures for problem solving
Problem solving is a behaviour under frustration, not a fact to memorise. Nobody improves how they define a problem, question a cause or test a fix by listening to definitions; they improve by making decisions in situations that feel real, then examining what those decisions reveal. That is exactly what a case study provides. Each case drops the group into a recognisable workplace moment - a project that stayed open forever, a flag nobody raised, a column of numbers nobody verified - and asks: what is actually wrong here, and how would you prove it?
Three practical advantages follow. First, discussion surfaces real habits: the way participants attack a fictional problem is usually the way they attack a real one, so the learning is personal without being exposing. Second, nobody has to perform. Unlike role-play, case discussion lets quieter team members contribute analysis instead of acting. Third, the format is repeatable: one case, one 90-minute session, one visible improvement theme at a time, so a manager can run a steady programme across a quarter.
The five problem solving domains, and a drill for each
The Problem Solving at Work collection organises its 30 cases into five domains, six cases per domain. Each domain names a failure pattern most teams will recognise, and each comes with a simple drill you can use immediately.
1. Define Before Solve - “the problem, printed”
Teams routinely solve the problem they wish they had. Cases such as The Ever-Open Project and The One-Lined Report show effort poured into symptoms because the real problem was never written down. Drill: before any solution talk, print the problem in one sentence - what is happening, where, since when, and how you know - and get the room to agree it.
2. Five Whys, Honestly - “dig to the root”
The five whys only work when the answers are honest rather than convenient. Cases such as The Unverified Column and The Said and Unsaid trace causes that stopped one level too shallow, at the first answer that blamed nobody in the room. Drill: keep asking why until the cause is something your team can actually change - then check it against evidence, not opinion.
3. Split the Knot - “big into testable”
A problem too big to test is a problem too big to solve. Cases such as The Oldest Ticket and The Card System show queues and backlogs that defeated whole teams until someone split them into parts with owners and measures. Drill: break the problem into strands, give each strand one owner and one number, and test the smallest strand first.
4. The Countermeasure Test - “fix and verify”
A fix that is never verified is a hope with a deadline. Cases such as The Second Line and The Friday Silence follow countermeasures that were announced, assumed and quietly abandoned. Drill: for every fix, write in advance what will be different, by how much, and when you will measure it - then hold the measurement.
5. Problems to Patterns - “learn once, reuse”
The most expensive problem is the one your organisation solves five times in five places. Cases such as The Loudest Table and The Ageing Queue show the same failure wearing different uniforms across teams. Drill: when a problem is solved, spend ten minutes writing the pattern - the early signal, the root cause, the fix - where the next team will actually find it.
How to run a 90-minute case study session
Every case in the collection is built for a 90-minute session:
- Brief (10 minutes). Introduce the domain and the question the case explores. Keep it to the theme; do not preview the ending.
- Read (15 minutes). Participants read the case individually and note the decision points as they find them.
- Analyse (25 minutes). In small groups, work through the analysis worksheet: what happened, where things broke down, and which habit would have changed the outcome.
- Decide (20 minutes). Each group commits to a course of action and defends it. Push for specifics - who does what, by when, and how everyone will know it worked.
- Debrief and plan (20 minutes). Compare decisions across groups, draw out the principle, and finish with the action-plan template: one habit each participant will change before the next session.
What's inside the free Problem Solving toolkit
The free toolkit is the fastest way to try this format with your own team. It contains sample decision cases from the Problem Solving at Work collection, the facilitator prompts that run each discussion, the analysis worksheets participants work through, and the action-plan template that turns discussion into commitments. It arrives as an instant ZIP download, it is yours to keep - the files never expire - and it needs only a free account: get the free Problem Solving toolkit.
If the format works for your team, the complete Problem Solving at Work collection holds all 30 cases - six per domain, 150 files in total - as one ready-to-run book. You can also browse the full shelf it belongs to in the Corporate Case Studies library. Every case is a fictional composite written for teaching, so groups can discuss the situation honestly without discussing real colleagues.
Free toolkit or full book? A side-by-side look
Both start in the same place — a real case, a real discussion, a decision the group has to defend. The difference is how far you can take it:
| Free Problem Solving toolkit | The complete 30-case book | |
|---|---|---|
| Cases | 3 complete cases | All 30 cases — six per domain |
| The five domains | Sample cases drawn from the collection | Every domain in full: define before solve, five whys honestly, split the knot, the countermeasure test, problems to patterns |
| Session format | 90 minutes per case | 90 minutes per case |
| Facilitator support | Prompts to run each discussion | Full facilitator guide with the answer key for every case (PDF + Word) |
| Participant materials | Analysis worksheets and an action-plan template | Participant workbook per case (PDF + Word), plus a 40-field fillable PDF per case for remote delivery |
| Files | One instant ZIP download | 150 files — print PDF, editable Word and fillable PDF |
| Price | Free — yours forever, no expiry | $27 launch price (regular $47) |
Rate yourself: how strong is your problem solving?
Before you run a case with your team, run this two-minute check on yourself. Ten statements, two for each of the five domains above. Rate how true each one is on an ordinary working week — not your best week — and you will get a score out of 100, a straight reading of where you stand, and a short action plan for the domain that needs you most.
