Reading time: ~5 min
If we ask the textbook what is the first step in problem solving, the answer comes back fast: define the problem. Every business school, every certification slide deck, every well-meaning LinkedIn post repeats it. And it’s wrong — or at least, dangerously incomplete.
The real first step in problem solving is not defining the problem. It’s observing the problem in its physical reality, before any interpretation. Lean coaches call that the 3G principle: Genba, Genbutsu, Genjitsu — real place, real thing, real facts. Skip 3G and we end up defining a problem that doesn’t exist, then solving it, then wondering why the metric didn’t move.
This article is the short version of why. For the full 3-step working approach (3G → 5W2H Meta Probe → Define), see our pillar guide on problem solving methodology.
The textbook answer (and why it fails on the floor)
The textbook first step in problem solving is Define the Problem. The classic five-step model goes: define → analyse → generate solutions → choose → implement. The classic seven-step model adds gather information, evaluate, and follow up. Both start in the same place: define.
On paper, that’s logical. In a real plant, it falls apart for three reasons:
- At the moment we say “define,” we don’t yet know the problem. We have a symptom — a number that dropped, a customer that complained, a machine that stopped. The symptom isn’t the problem; it’s the visible end of a chain of causes.
- Definition is interpretation. When a team gathers in a meeting room and “defines the problem,” they’re each defining a different problem — shaped by their role, their assumptions, their fear of being blamed. The room aligns on a sentence, but the sentence describes a fiction.
- Definition without observation is theatre. We’ve watched teams write a clean problem statement on a whiteboard, run a 5-Whys against it, and produce a beautifully formatted root-cause document — for a problem that, on the floor, didn’t actually exist.
That’s the cost of treating define as the first step. The Lean answer is to put one step before it.
The actual first step in problem solving: 3G — Anchor to Reality
Before we define anything, we go to the work and observe it. That’s the 3G principle:
- Genba (現場 — real place). Walk to the place where the gap shows up. Production line? Office? The meeting room is not a real place. Spreadsheets are not a real place.
- Genbutsu (現物 — real thing). Touch the object involved. If a report is late, look at the report. If a machine is down, put a hand on the machine. If there’s a defect, hold the defective part.
- Genjitsu (現実 — real facts). Remove the drama. What are the raw, measurable, verifiable data? Time-stamped logs, photos, samples, numbers — anything that survives in a courtroom.
3G builds the reality dossier. It is the only ground truth we have before interpretation kicks in. Without it, define is fiction.
A short first step in problem solving example: a manager says, “throughput on Line 4 is down.” That’s the symptom statement. We walk the line. We see operators waiting between cycles. We time a few cycles. We pull the shift log. We discover the slow point is a single jig that’s been mis-aligned for two weeks. The “problem” was never throughput — it was a misaligned jig hiding behind a metric. Without 3G, we’d have spent a week on capacity planning instead of fixing the jig.
This is the framework Mario Mason describes in detail in Are You Working on the Wrong Problem? — the canonical reference for this approach.
Why most “5-step” and “7-step” models skip 3G (and what to do)
Look at any popular 5 step problem solving or 7 steps of problem solving model and 3G isn’t there. The textbook framework assumes the observer has already done their homework before the meeting starts. In a real workplace, they haven’t — and the framework doesn’t tell them they need to.
The fix is not complicated. Insert 3G as Step 0 before define. The full sequence becomes:
| # | Step | Tool | Purpose |
|---|---|---|---|
| 0 | Anchor to reality | 3G | Observe physically before interpreting |
| 1 | Align meaning | 5W2H Meta Probe | Surface the team’s interpretation map |
| 2 | Define the real problem | Synthesis of Steps 0 + 1 | Write the problem statement everyone agrees on |
| 3 | Analyse causes | 5 Whys, Fishbone, Pareto | Trace from problem to root |
| 4 | Generate solutions | Brainstorming, A3 | Decide what to do |
| 5 | Implement + verify | PDCA cycle | Run the experiment, measure, lock in |
Step 0 looks small. It’s the step that decides whether the next five do anything useful. Skip it and we get a tidy diagram for the wrong problem.
In short
- The textbook says the first step in problem solving is Define the Problem. That’s incomplete.
- The real first step is 3G — Genba (real place), Genbutsu (real thing), Genjitsu (real facts). Observe before you interpret.
- 3G builds the reality dossier that lets define describe an actual problem instead of a symptom.
- Most 5-step and 7-step models skip 3G. Insert it as Step 0.
- For the full 3-step working methodology (3G → 5W2H → Define), the Kobetsu Kaizen pillar guide is the next read.
FAQ
Q1: What is the first step in problem solving? A1: The first step is not defining the problem. It’s the 3G principle — Genba (real place), Genbutsu (real thing), Genjitsu (real facts). Observe the problem physically, before any interpretation. Most textbook models start at “define,” but defining a problem we haven’t observed produces a clean root-cause analysis for a problem that may not exist.
Q2: Why do most models say the first step is “Define the Problem”? A2: Because the textbook framework assumes the observer has already gathered objective facts before the meeting starts. In a real workplace, they usually haven’t. Define-first works in classroom case studies; on the shop floor, it produces tidy analysis for the wrong problem. The Lean answer is to insert 3G observation as Step 0.
Q3: What does 3G stand for in problem solving? A3: 3G stands for three Japanese terms used in Lean and Kobetsu Kaizen: Genba (現場 — go to the real place where the problem occurs), Genbutsu (現物 — observe the real thing or object involved), Genjitsu (現実 — work from the real, verifiable facts). Together they form the reality-anchoring step that precedes any problem definition.
Q4: What is the difference between a problem and a symptom? A4: A symptom is the visible end of a chain of causes — throughput dropped, the customer complained, the machine stopped. The problem is the underlying mechanism producing the symptom. Without 3G observation, we tend to treat the symptom as the problem and solve the wrong issue. With 3G, the symptom becomes a starting point, not a destination.
Q5: How long does the 3G step actually take? A5: Anywhere from 30 minutes to a full day, depending on the complexity. A misaligned jig might take 20 minutes to spot once we walk the line. A cross-shift quality drift might take a full shift to observe. The rule is: take less time than 3G needs and we pay for it later, in week three or four, when the corrective action doesn’t move the metric.
The next time someone asks what is the first step in problem solving, we either repeat the textbook answer — or we walk the line, hold the part, read the data, and then define the problem. The free Ronin Problem Solving course on Lean Trainings walks through 3G and the full Kobetsu Kaizen approach in three short modules. The $5 certification on the certifications page is the verifiable credential. Start the free Ronin Problem Solving course →
