Lean Bronze common mistakes
Lean Bronze · Understand the traps and how to avoid them.
Treating Lean as a toolbox of standalone techniques (5S, kanban, poka-yoke) and answering items as if each tool were the goal, rather than recognising the underlying purpose of eliminating waste and creating flow.
Most candidates come from tool-implementation backgrounds where success was measured by deploying a method; the exam instead tests whether you can connect a tool to the principle it serves and to the expected business result.
What to do instead
For every tool you study, write three lines: the waste or problem it addresses, the condition that must exist for it to work, and the metric that should move. Drill questions by asking 'what principle is this testing?' before looking at the options.
Confusing the two pillars of the house of Lean - just-in-time and jidoka - and attributing flow, takt, and pull to jidoka or stop-the-line and error-proofing to just-in-time.
The pillars are usually memorised as a diagram without functional meaning, so the labels blur under time pressure; the exam deliberately places both pillars' tools in the same item.
What to do instead
Anchor each pillar with a one-sentence definition: JIT delivers the right item at the right time in the right quantity; jidoka gives equipment and people the ability to detect abnormality and stop. Sort every tool you know into one of the two columns and review the sort until it is automatic.
Choosing the fastest-sounding countermeasure (automate, add inspection, add a second shift) instead of the one that removes the root cause, and missing that added inspection is waste, not quality improvement.
Candidates answer from a project-management reflex of mitigating symptoms, and inspection feels responsible; the exam tests whether you can distinguish containment from countermeasure.
What to do instead
Practise classifying each proposed action as containment, detection, or prevention. Eliminate detection-only answers unless the question explicitly asks how to protect the customer while the root cause is investigated.
Describing PDCA as a linear four-step checklist and failing items that test the iteration, the study phase as the place where the hypothesis is tested, or the need to standardise before the next cycle.
The cycle is learned as a mnemonic, so candidates cannot reason about what happens when a check fails or why act precedes the next plan.
What to do instead
Walk a real improvement you have seen through PDCA and name what evidence existed at each gate. Memorise that without a predicted outcome there is nothing to check, and that standardisation is the output of act.
Treating standard work as a rigid rule imposed on operators, or as a document written once by an engineer, and rejecting answers that describe it as the current best method owned and improved by the team.
Everyday use of the word 'standard' suggests bureaucracy, so candidates pick answers emphasising compliance and discipline over the baseline-for-improvement meaning.
What to do instead
Learn the three elements of standard work (takt time, work sequence, standard in-process stock) and the rule that a standard is provisional until a better method is proven. Answer items by asking whether the option makes the standard easier or harder for the team to improve.
Confusing a value stream map with a process map or a layout diagram, and answering questions about lead time, information flow, or the future-state plan with process-level detail.
Candidates have drawn flowcharts and floor plans at work and assume the labels are interchangeable; the exam tests scope (door-to-door, material and information) and purpose (a plan, not a picture).
What to do instead
Be able to state what a value stream map must contain: customer demand, information flow, process boxes with data boxes, inventory triangles with days, timeline with value-added and non-value-added time, and a future-state with a loop plan. Reject any answer that stops at one department.
Calculating takt time as available time divided by units produced, or confusing takt with cycle time, and then selecting answers about line balancing based on the wrong figure.
The formulas look similar and both use time per unit; candidates who have not worked the numbers default to the definition that matches their plant's output reporting.
What to do instead
Fix the definitions: takt = available work time / customer demand; cycle time = time one unit actually takes at a step. Work five numeric examples, including one where cycle time exceeds takt and one where demand changes mid-shift, and check which way the ratio moves.
Answering culture questions with slogans - 'get leadership buy-in', 'empower employees', 'build a culture of continuous improvement' - when the item asks for a specific mechanism such as leader standard work, a daily tiered accountability process, or a defined suggestion-response time.
Culture is the least technical domain, so candidates fall back on motivational language; the exam rewards observable leader behaviours and management systems over intentions.
What to do instead
Convert each cultural principle into a visible routine: leader standard work, gemba walks on a schedule, tiered huddles with escalation rules, andon response commitments, idea response within a stated time. When two options sound equally positive, choose the one describing a repeatable behaviour with an owner and a cadence.
Assuming Lean applies only to the shop floor and selecting answers that exclude office, engineering, healthcare, or service processes, or that treat administrative waste as exempt.
The origin story in manufacturing dominates study material, so candidates generalise from the factory setting and miss items about transactional value streams.
What to do instead
Learn the eight wastes with a service example for each (waiting for approvals, defects in order entry, motion in a clinic layout, unused engineering talent). Practise mapping a hiring or invoicing process end to end.
Reading an item that describes a symptom and answering with the tool named in the symptom rather than diagnosing the system condition, for example prescribing kanban where the real problem is unstable process or uneven demand.
Keyword matching is a fast strategy under exam time pressure, and the scenario often names a tool to make that shortcut tempting; the exam is written to punish it.
What to do instead
Before reading the options, write one line naming the constraint (variation, overburden, waste, or flow). Then eliminate any option that does not address that constraint, even if it is a valid Lean tool. Heijunka before pull, stability before flow.