EXIN LSSA Lean Six Sigma Yellow Belt common mistakes
EXIN LSSA Lean Six Sigma Yellow Belt · Understand the traps and how to avoid them.
Treating Lean and Six Sigma as competing philosophies and picking one label for every scenario, instead of recognising that Lean attacks flow and waste while Six Sigma attacks variation with data.
Candidates memorise two separate definition lists and never build a comparison, so exam items that describe a situation (long queues and waiting versus inconsistent output measurements) get answered with whichever term was read most recently.
What to do instead
Build a two-column comparison covering primary target, typical metrics, core tools and typical project triggers. Practise classifying short scenarios by asking 'is the pain delay/waste or is it variation/defects?' before choosing the label.
Confusing the DMAIC phases by assigning a tool to the wrong phase, for example placing a fishbone diagram in Define or a control chart in Improve.
Candidates learn tools as a flat list and never anchor each tool to the question it answers in the cycle, so sequencing questions feel arbitrary.
What to do instead
Create a phase-by-phase sheet where each tool is written next to the question it answers (Define: what problem and for whom; Measure: how big and how well measured; Analyze: why; Improve: what change; Control: how do we hold it). Re-sort a shuffled tool list into phases weekly until it is automatic.
Writing or selecting problem statements that embed a cause or a solution, such as 'the line stops because the feeder jams, so we need a new feeder'.
Real workplace discussions jump straight to solutions, and candidates copy that habit into exam answers without testing the statement against the charter criteria.
What to do instead
Apply a three-part test to every problem statement: does it state a gap with magnitude, location and time frame; is it free of cause language; is it free of solution language. Rewrite five cause-laden statements into neutral ones as practice.
Treating Voice of the Customer as a single opinion gathered from one internal stakeholder rather than translating customer needs into measurable requirements.
Candidates equate 'customer feedback' with 'customer requirements' and skip the translation step from stated need to critical-to-quality characteristic.
What to do instead
Practise the chain: collect customer statements, group them into needs, convert each need into a measurable CTQ with a unit and target, then check which data source could measure it. Be able to explain why internal opinion is not VOC.
Skipping the charter elements that constrain the project, especially scope boundaries, team roles and success metrics, and answering charter questions with only a goal statement.
Goal statements feel like the essence of a project, so the other boxes are read once and forgotten, yet exam items often target out-of-scope statements or the sponsor's role.
What to do instead
Memorise the charter as a fixed checklist: problem, goal, scope in and out, business case, team and roles, milestones, metrics. For each element write one sentence on what goes wrong if it is missing, then answer practice items from that list.
Ignoring measurement system capability and data type when planning data collection, for example proposing an attribute check sheet where a continuous gauge study is needed, or trusting data without checking repeatability.
Candidates focus on the process being measured and not on the instrument or definition collecting the data, so measurement-system items feel like a separate topic.
What to do instead
Before any data plan, answer four questions: what is the operational definition, is the data continuous or attribute, who and how will it be recorded, and how do we know the measurement is repeatable and reproducible. Drill the distinction between precision, accuracy and agreement.
Reading a process map as a diagram to describe rather than a diagnostic, so waste, handoffs and rework loops drawn in the map are not identified in the answer.
Candidates reproduce the shape of a flowchart instead of interrogating each step, and they confuse a value stream map's data boxes with a simple sequence map.
What to do instead
Annotate every map you draw with three markers: decision points, handoffs between owners, and loops back to an earlier step. Then state one waste or delay risk per marker. Practise spotting non-value-adding steps in a short written process description.
Stopping root cause analysis at the first plausible cause, or listing symptoms as causes, instead of verifying causes against data before moving to solutions.
Fishbone diagrams generate many candidate causes and candidates treat the diagram itself as the conclusion, skipping the verification step that separates correlation from causation.
What to do instead
Always pair a cause-and-effect diagram with a verification method (stratified data, five-whys to a controllable cause, or a small test). For each candidate cause, write how you would prove or disprove it with data before accepting it.
Choosing an improvement tool by familiarity rather than by the type of waste or variation present, such as applying 5S to a scheduling delay or kaizen events to a problem needing data analysis.
Tool lists are memorised as definitions without a matching rule, so candidates default to the tool they know best regardless of the diagnosed problem.
What to do instead
Build a matching table linking each waste type and problem pattern to candidate tools (5S for workplace organisation, standard work for variation in method, poka-yoke for human error, flow and pull for waiting and inventory). Justify each tool choice in one sentence referencing the diagnosis.
Treating the Control phase as documentation only, omitting monitoring ownership, response plans and reaction to out-of-control signals, and misunderstanding the Yellow Belt's support role versus the Green or Black Belt's lead role.
Control feels like an administrative ending, and role questions are answered from job titles rather than from defined responsibilities within a project team.
What to do instead
For every control answer, name the metric, the chart or check, the owner, the frequency and the action if the signal triggers. Separately write a one-line description of what a Yellow Belt does, what a Green Belt does and what a sponsor does, and test role questions against those lines.