Lean Gold common mistakes
Lean Gold · Understand the traps and how to avoid them.
Treating 'lean' as a synonym for cost-cutting or headcount reduction, and picking the answer that removes people whenever a scenario asks how to improve a process.
Many candidates come from cost-reduction programmes where lean was used as a euphemism for layoffs, so the association is automatic. Exam scenarios deliberately describe a process with idle time and excess staffing to bait this answer.
What to do instead
Anchor on the definition: lean maximises customer value by removing non-value-adding activity, and the standard remedy is to redeploy freed capacity to flow, quality, or growth rather than to cut. When two answers both reduce cost, prefer the one that removes the activity (waste) over the one that removes the person. Drill the distinction between muda elimination and labour reduction until the waste-based answer feels default.
Confusing the five lean principles with the eight wastes, or with the PDCA cycle, when a question asks for the correct ordering or for the next step after a given principle.
The lists are short, memorised together, and often taught in the same introductory session, so they blur under time pressure. Ordering questions punish any blur because only one sequence is correct.
What to do instead
Build a single mental scaffold: specify value, map the value stream, create flow, establish pull, pursue perfection. Attach one concrete artefact to each step (value = voice of customer; map = current-state VSM; flow = cell layout; pull = kanban; perfection = kaizen). Rehearse the sequence aloud until it is automatic, then practise distinguishing it from PDCA and from the waste list.
Selecting 'value stream mapping' as the answer for any question about analysing a process, even when the question is about a single workstation, a quick changeover, or a standard work problem.
VSM is the most famous lean tool, so it becomes a default. Candidates do not check the scope of the scenario, which may be one operation rather than an end-to-end stream.
What to do instead
Before answering, identify the boundary in the question: end-to-end across departments means VSM; one machine or cell means standard work, SMED, or 5S; a flow or layout problem means cell design or spaghetti diagram. Match tool to scope explicitly, and reject VSM answers whenever the scenario sits inside a single process box.
Reading a current-state map and reporting total lead time as the sum of all activity times, including value-adding and non-value-adding steps, then computing the value-added ratio incorrectly.
Candidates add every number on the timeline because it looks like a total. The ratio then comes out far too high, and percentage answers in the options are built to catch exactly this arithmetic slip.
What to do instead
Separate the two timelines on the map: process time (sum of value-adding step times) and lead time (sum of all inventory waits plus process times). Value-added ratio = value-adding time divided by total lead time, expressed as a percentage. Work three or four numeric examples by hand until the distinction between the two sums is reflexive.
Labelling every delay as 'waiting waste' and missing the specific waste the scenario is testing, such as overproduction, over-processing, or unused talent.
Waiting is the easiest waste to spot, so it absorbs ambiguous cases. Scenarios about extra approvals, redundant signatures, or rework are actually over-processing, and scenarios about making ahead of demand are overproduction, the worst waste because it creates the others.
What to do instead
Learn a decision test for each waste. Does the step change the form, fit, or function for the customer? If not, it is over-processing. Is work being done before the next step needs it? Overproduction. Are people's skills unused? Unused talent. Waiting is only when a part or person is idle between steps. Apply the test to each option rather than pattern-matching keywords.
Confusing the tools of 5S with their correct order, or treating 5S as housekeeping rather than as a standardisation and sustainment system.
The five Japanese terms are similar and the English translations vary between sources, so candidates memorise the words without the logic. Questions that ask what follows sort or what sustain actually requires then defeat recall alone.
What to do instead
Memorise the logic, not just the list: seiri (sort, remove what is not needed), seiton (set in order, a place for everything), seiso (shine, clean and inspect), seiketsu (standardise, make the first three the norm), shitsuke (sustain, audit and discipline). Note that shine doubles as inspection and that sustain is the step most programmes fail. Practise ordering questions and questions asking which step a described action belongs to.
Treating kaizen, kaikaku, and the PDCA cycle as interchangeable, or describing a kaizen event as a one-off project with no follow-up standard.
All three appear in improvement-tool questions with similar wording. Candidates also forget that improvement is only complete when the new method is standardised and the cycle restarts.
What to do instead
Fix the distinctions: kaizen is continuous incremental improvement by the people doing the work; kaikaku is radical transformation; PDCA is the improvement cycle (plan the change, do it on a small scale, check the result, act to standardise or adjust). In scenario questions, prefer answers that include standardisation and a check step over answers that stop at implementation.
Choosing 'train everyone in lean tools' or 'run more kaizen events' as the answer to a question about why a lean programme stalled, instead of diagnosing leadership behaviour and management system.
Tool-centred answers feel concrete and actionable, and many candidates have seen tool-heavy deployments. Exam scenarios on sustainment usually hinge on leaders not going to the gemba, not asking the right questions, or not changing performance measures.
What to do instead
When a scenario describes a programme that faded, look for the management-system gap: no daily management, measures that reward batch output, leaders absent from the floor, no standard work for leaders. Prefer the answer that changes leader behaviour and the measurement system over the one that adds training or events. Learn the standard leader routines (gemba walks, tiered accountability, A3 problem solving) as the sustainment answer.
Answering culture questions with 'communicate more' or 'get buy-in' rather than naming the specific mechanism, such as respect for people, leader standard work, or a structured suggestion system.
These phrases are true but too vague to be the keyed answer. Candidates default to them because they sound safe, while the exam expects a named practice that makes the culture operational.
What to do instead
Replace vague answers with mechanisms. Respect for people shows up as psychological safety to stop the line, problem surfacing without blame, and ideas acted on. Culture change shows up as leader standard work, visible gemba presence, and measures that reward flow and quality. When two options sound similar, pick the one that names a repeatable routine rather than an intention.
Ignoring the question stem's qualifier, such as 'first step', 'next action', or 'most likely root cause', and choosing the most comprehensive-sounding improvement instead of the one the stem asks for.
Long stems and plausible options create time pressure, and candidates answer the question they expected rather than the one written. Sequence questions are especially vulnerable because the best long-term fix is rarely the correct first step.
What to do instead
Underline the qualifier before reading the options, then test each option against it. For 'first step' questions, prefer stabilise-then-improve answers such as standard work, 5S, or data collection over capital projects. For root-cause questions, prefer the systemic cause over the human-error symptom. Do a final pass on flagged items checking only the qualifier, not the whole stem.