Yellow Belt roles, teamwork and project support
This domain covers how a Yellow Belt fits into a Lean Six Sigma organisation: what you are expected to do, what you hand to a Green or Black Belt, and how to behave inside a project team. Exam questions are scenario-based: "what is the most appropriate action for the Yellow Belt?"
What a Yellow Belt does
- Serves as a team member: supplies process knowledge, collects and checks data, helps build maps and fishbone diagrams, supports pilots and control activities.
- Leads small, contained improvements in their own work area with a Green Belt coach - narrow scope, one team, weeks rather than months.
- Uses the basic toolkit: Pareto, 5 Whys, fishbone, flowchart, check sheet, 5S, standard work.
- Escalates rather than guesses: problems crossing departments, needing statistical tests or capital spend go to a Green or Black Belt.
Team roles in a project
- Sponsor/Champion: authorises the project, removes barriers, reviews at gates.
- Process Owner: knows the work, approves changes, inherits the control plan.
- Green/Black Belt: leads, applies advanced statistics, mentors.
- Yellow Belt/team member: contributes data and process expertise; may act as facilitator or scribe.
- Finance or subject matter expert: validates benefits, supplies specialist knowledge.
Working as a team
Tuckman's stages - forming, storming, norming, performing, adjourning - predict that early disagreement is normal, not failure. Ground rules, an agenda, a parking lot for off-topic items and documented actions keep meetings short. Decisions are logged with a RACI so accountability is explicit; consensus is preferred, but the process owner or sponsor breaks deadlock.
Worked example
A Green Belt asks you to "grab some cycle-time numbers from the team by Friday." The best response is not to start counting. Ask what the operational definition of cycle time is (start and stop points), which stratification factors matter, how many observations are needed and who will verify the measurement system. Then write a one-page data collection plan and get it agreed. Reasoning: data collected without definitions and a plan usually has to be discarded, and Measure-phase credibility depends on it.
Traps that cost marks
- Accepting work beyond Yellow Belt scope instead of escalating with a clear reason.
- Collecting data with no operational definition or sampling plan.
- Reporting brainstorm opinions as verified causes.
- Excluding the process owner until handover, then finding the change rejected.
- Recording decisions with no named owner or due date.