Lean Silver Certification common mistakes
Lean Silver Certification · Understand the traps and how to avoid them.
Treating the seven (or eight) wastes as a memorized list and labelling an example with the wrong waste - for example calling excess work-in-process inventory 'overproduction' or calling waiting time 'inventory'.
Candidates memorize the mnemonic but never learn the discriminating test for each waste, so on scenario questions they pick whichever waste sounds most wasteful rather than the one that actually describes the observed condition.
What to do instead
For each waste, write a one-line decision test and apply it to every scenario. Overproduction is making more, earlier, or faster than the next process needs. Inventory is material or information sitting between processes. Waiting is an operator or machine idle because flow is blocked. Use the test on practice scenarios where two wastes overlap, and justify in writing why the second-best answer fails.
Confusing value-added, non-value-added-but-required (business value-added), and pure non-value-added steps when calculating value-added ratio or lead time on a value stream map.
Candidates apply the strict customer test inconsistently - sometimes counting regulatory inspection or legal sign-off as value-added, sometimes excluding it - so the ratio and improvement targets come out wrong.
What to do instead
Fix one rule and apply it everywhere: a step is value-added only if the customer would pay for it, it is done right the first time, and it physically or informationally transforms the product. Everything else is non-value-added; split it into required (regulatory, safety, contractual) and pure waste. Recompute value-added ratio on two or three maps using the same rule until the classification is automatic.
Reading a current-state value stream map as a snapshot of the process steps only, ignoring information flow, inventory triangles with days-of-supply, and the timeline ladder at the bottom.
Candidates trained on process flowcharts map boxes and arrows but skip the information-flow arrows from production control and the lead-time ladder, so they cannot answer questions about total lead time, takt, or where the biggest delay sits.
What to do instead
Practice drawing complete maps from a written scenario: customer and supplier, production control, information arrows, process boxes with cycle time and changeover, inventory triangles with quantity and days of supply, truck shipments, and the sawtooth timeline. Always compute total lead time and value-added time from the ladder, and identify the pacemaker before proposing a future state.
Choosing a countermeasure before establishing a verified root cause - jumping from a problem statement straight to a solution, or using a fishbone diagram as the end of analysis rather than the start.
Exam scenarios describe familiar symptoms, and candidates pattern-match to a known tool. Fishbone diagrams also feel like analysis is complete once the diagram is full, so no hypothesis is tested.
What to do instead
Follow the A3 or DMAIC discipline explicitly in every answer: state the problem with data, contain it, stratify, form a testable root-cause hypothesis, verify it against evidence, then select a countermeasure that addresses the verified cause. When a question offers a solution as an answer choice, check whether a cause-verification step is offered first and prefer it.
Treating 5 Whys as a fixed number of questions and stopping at 'operator error' or 'needs more training' instead of reaching a systemic cause.
Candidates learn 5 Whys as a ritual with a count, so they stop when they hit five iterations or when the answer sounds plausible, and they accept human-error endpoints that are really symptoms of a process design problem.
What to do instead
Continue until the cause is something the organization can change systemically (standard work, poka-yoke, scheduling rule, supplier requirement) and can be verified by evidence. Reject 'operator error' and 'lack of training' as terminal causes unless you can show the process made the error possible and training is the verified countermeasure. Practice on a written case and check each why against the previous answer's logic.
Confusing the roles of standard work, standardized work, and work standards, or treating standard work as a rigid document rather than the current best method owned by the team.
The terms sound interchangeable and many candidates have only seen work instructions, so they select 'documented procedure approved by engineering' as the definition of standard work.
What to do instead
Learn standard work as the combination of takt time, work sequence, and standard in-process stock, defined by the people doing the work and improved through kaizen. Distinguish it from a work standard or instruction sheet (a specification). On questions, look for the elements of takt, sequence, and in-process stock together; an answer that mentions only documentation is usually wrong.
Answering leadership and culture questions with tool-based answers - proposing a new dashboard, a training program, or a kaizen event when the scenario calls for leader standard work, gemba presence, or coaching behaviour.
Candidates study tools intensively and have limited exposure to leader behaviours, so they reach for the familiar technical intervention when the question is testing whether leaders model and sustain the change.
What to do instead
For culture questions, ask what the leader personally does daily: goes to the gemba, asks questions rather than gives answers, follows leader standard work, responds to abnormalities, and develops problem-solvers. Prefer answers describing recurring leader behaviour and coaching over one-off events or new documentation.
Treating Lean deployment as a series of isolated tool events (a 5S week, a kaizen blitz) rather than a management system with value-stream selection, policy deployment, and daily management.
Tool events are visible and easy to describe, so candidates select them as the correct deployment approach, missing that the exam tests sequencing, governance, and sustainment.
What to do instead
Learn a deployment sequence: identify the value stream and customer value, map current and future state, set breakthrough objectives through policy deployment (hoshin), build daily management and standard work, then use kaizen to close gaps. When a question asks how to deploy, prefer answers that connect strategy to the value stream to daily management over standalone events.
Misapplying takt time, cycle time, and lead time interchangeably, or computing takt from working hours without subtracting breaks and planned downtime.
The three terms are used loosely in practice, and candidates compute takt as available time divided by demand using total shift hours, producing an inflated takt and wrong staffing conclusions.
What to do instead
Memorize the definitions and units: takt time = net available operating time per shift divided by customer demand per shift; cycle time = time one unit takes at a process; lead time = elapsed time for a unit to traverse the value stream. Always subtract breaks, lunches, planned maintenance, and meetings from available time before dividing. Work three numeric problems with different shift patterns until the arithmetic is reliable.
Ignoring the sustainment and response part of a Lean implementation answer - describing how to install a system but not how abnormalities are detected, escalated, and learned from.
Candidates focus on the change itself and treat sustainment as an afterthought, so they miss answer choices involving andon response, daily tiered accountability, audit cadence, or leader standard work.
What to do instead
For every implementation scenario, add the sustainment layer explicitly: what the standard is, how deviation becomes visible, who responds and within what time, and how the standard gets revised. Practice writing a one-paragraph sustainment plan for each tool you study (5S, standard work, kanban, SMED) so the response and escalation elements become automatic.