APMG LSS Yellow Belt common mistakes
APMG LSS Yellow Belt · Understand the traps and how to avoid them.
Classifying a non-value-adding but currently necessary activity (such as regulatory inspection or legal sign-off) as pure waste and proposing to eliminate it outright, rather than treating it as necessary non-value-adding work to be reduced.
Candidates learn 'value = what the customer pays for' and then apply a binary value/waste rule to every step, forgetting the third category of necessary non-value-adding activity that the customer does not pay for but which cannot be removed today.
What to do instead
Before answering, run each step through three questions: does the customer value it, is it required by law/safety/contract, and can it be removed now? Practise sorting a short process list into value-adding, necessary non-value-adding, and pure waste, and note that the necessary category is optimised, not eliminated.
Confusing the types of waste when two overlap, for example labelling waiting time caused by an unbalanced line as 'motion', or calling excess inventory 'overproduction'.
The waste categories are learned as a memorised list of eight words without a discriminating test, so candidates pick the label that sounds closest to the scenario rather than the one defined by the cause.
What to do instead
Memorise a one-line discriminator for each waste (motion = people moving; transportation = product moving; waiting = idle time for the next step; inventory = stock beyond need; overproduction = making more/earlier than the next step needs). For each practice scenario, state the waste and the evidence that rules out the nearest rival category.
Treating lean as a set of tools (5S, kanban, value stream mapping) and answering questions about purpose or sequence by naming a tool instead of the underlying principle.
Tool names are memorable and appear frequently in study material, so candidates reach for a familiar tool when the question asks why an activity is done or what should happen first.
What to do instead
For any 'why' or 'what first' question, answer at the principle level (specify value, identify the value stream, create flow, let the customer pull, pursue perfection) and only name a tool when the question asks how. Rehearse the five principles in order until the sequence is automatic.
Describing DMAIC phases by their deliverables alone, so the Measure and Analyse phases are swapped, or improvement activity is placed in Control.
The phases share vocabulary (data, charts, causes), and candidates who memorise 'Measure = data' and 'Analyse = root cause' without a phase-boundary rule cannot place activities that involve both.
What to do instead
Anchor each phase to its question: Define = what problem and for whom; Measure = how big and how capable is the current process; Analyse = why does the variation/defect occur; Improve = what change removes the cause and does it work; Control = how do we hold the gain. Test each option against the phase question before choosing.
Selecting the Analyse-phase answer when the scenario is still establishing baseline performance, or proposing a solution before a verified root cause has been identified.
Candidates want to be helpful and jump to the remedy, especially when the scenario describes an obvious-sounding problem, skipping the discipline the methodology requires.
What to do instead
Apply a gate rule: no solution until a root cause is verified with data; no root cause until the baseline and measurement system are established. When an option proposes a fix, check whether the scenario has already supplied evidence of cause.
Treating Six Sigma's goal as reducing the average or the range of a process rather than reducing variation relative to specification, and misreading a capability figure as a defect count.
Everyday language equates 'improvement' with 'better average', and sigma-level tables are memorised as numbers without the link to specification limits and process spread.
What to do instead
State the definition in your own words each time: Six Sigma is about variation small enough relative to the specification that defects are extremely rare. Practise reading capability statements as 'spread versus tolerance' and convert a sigma level to defects per million only when the question asks for it.
Choosing the wrong basic quality tool for the data type, for example using a Pareto chart to find a relationship between two variables, or a histogram to show a trend over time.
The seven basic tools are learned as a list of names and pictures, and the selection rule (what question am I asking, and is the data attribute or variable, ordered or not) is not practised.
What to do instead
Build a selection table: cause brainstorming = fishbone/check sheet; prioritising causes = Pareto; distribution of a variable = histogram; relationship between two variables = scatter; behaviour over time = run/control chart; process steps = flowchart. Match the question's purpose to the row before looking at the options.
Reading a control chart as a simple trend line and missing an out-of-control signal, or conversely calling normal variation a special cause.
Candidates look for dramatic spikes and ignore pattern rules such as a run of points on one side of the centre line, and they have not internalised the distinction between common and special cause variation.
What to do instead
Learn the standard signal rules (a point beyond the limits; a run of consecutive points on one side; a systematic pattern) and, for each chart shown in a question, check the rules explicitly rather than eyeballing. Tie the answer back to whether the response should be to adjust the process (special cause) or change the process (common cause).
Confusing the roles in an improvement project, for example expecting the Yellow Belt to lead a complex cross-functional project, or attributing sponsorship and resource authority to the team rather than the champion.
Belt colours and role titles are memorised as a hierarchy without their boundaries, and candidates over- or under-state what a Yellow Belt is expected to do.
What to do instead
Learn each role by its decision rights: champion/sponsor authorises and removes barriers; Black Belt leads complex cross-functional projects and coaches; Green Belt leads projects within their area; Yellow Belt contributes as a team member and applies tools in own work. Answer role questions by asking who holds the authority described.
Describing teamwork or change support in generic terms (communication is important, get buy-in) when the question asks for a specific behaviour or the correct stage of team development.
Soft-skill content feels like common sense, so candidates do not prepare concrete behaviours and cannot distinguish between forming, storming, norming and performing descriptions, or between the sponsor's and team leader's actions.
What to do instead
Prepare short, specific behaviour statements for each team stage and for stakeholder engagement (identify stakeholders, assess influence and interest, plan communication, act, review). When a scenario asks what to do next, choose the concrete action that matches the stage described rather than a general virtue.