Six Sigma Roles & RACI
Key Takeaways
- Executive leadership sets strategy and portfolio priority; champions (sponsors) remove barriers and own business results for a project.
- Master Black Belts coach methods and deploy the program; Black Belts lead complex projects full-time; Green Belts lead or support projects part-time with statistical and DMAIC skill.
- Process owners sustain the improved process; team members supply process knowledge and execute work; facilitators and coaches improve how the team works and learns.
- A RACI matrix assigns Responsible, Accountable, Consulted, and Informed parties so decisions and handoffs are clear.
- BoK II.F.2 is Apply level: map vignette actors to Six Sigma roles and build or interpret a RACI for key project activities.
Six Sigma Roles & RACI (CSSGB BoK II.F.2 — Apply)
Quick Answer: Executives set direction and portfolio priority. Champions/sponsors clear barriers and own project business outcomes. Master Black Belts coach and deploy the program. Black Belts lead complex projects; Green Belts lead or support projects with DMAIC tools. Process owners sustain results; team members bring process truth. Use a RACI (Responsible, Accountable, Consulted, Informed) matrix so every critical task has one Accountable owner.
BoK II.F.2 is Apply: you must place the right role on a scenario and use RACI so work does not fall through cracks. Confusing “who facilitates” with “who owns the process forever” is a classic exam trap.
Core Six Sigma Deployment Roles
| Role | Primary focus | Typical time commitment | Green Belt exam cue |
|---|---|---|---|
| Executive | Strategy, goals, resources for the Six Sigma program | Steering / portfolio reviews | Approves program funding; selects strategic themes |
| Champion (sponsor) | Business case, priority, barriers, tollgate decisions for a project | Part-time ownership of outcomes | Removes obstacles; owns hard/soft savings story |
| Master Black Belt (MBB) | Method excellence, coaching belts, deployment standards | Full-time program technical leader | Mentors statistics and project selection quality |
| Black Belt (BB) | Lead complex or cross-functional projects; mentor GBs | Often full-time project work | Deep tools, multi-site or high-ambiguity problems |
| Green Belt (GB) | Lead mid-scope projects or key analysis on BB projects | Part-time alongside job | CSSGB role: DMAIC + basic stats on local processes |
| Process owner | Day-to-day process performance and sustainment | Ongoing operations role | Accepts control plan; owns metrics after close |
| Team member | Subject-matter expertise; executes tasks and pilots | Part-time on project | Operators, engineers, analysts on the core team |
| Coach | Develops belt or team capability (often MBB or BB) | As needed | Skill building, not replacing process ownership |
| Facilitator | Designs meetings and group process so the team works well | Session-based | Neutral on content; strong on participation and agenda |
| Sponsor | Same family as champion—funds and shields the project | Leadership touchpoints | If both words appear, treat as project-level support authority |
Executives vs champions
Executives (deployment champions at the enterprise level) choose how Six Sigma ties to strategy, which metrics matter (e.g., CoPQ, on-time delivery), and how many belts to train. A project champion is closer to one charter: they attend tollgates, free up data access, and arbitrate scope with peer leaders. One person can wear both hats in a small company; large organizations separate them.
Belts: MBB, BB, GB
- Master Black Belt: train and coach, review tool use, help with difficult statistics or change issues, keep the project pipeline healthy. MBBs are not the default “do all the analysis” resource for every Green Belt chart.
- Black Belt: project leader for larger scope, heavier analytics, or multi-stakeholder streams; often mentors Green Belts.
- Green Belt: the CSSGB role—applies DMAIC, basic hypothesis tests, MSA awareness, capability concepts, and control plans on processes they know, usually while still in an operational job.
Exam trap: Assigning sustainment to the Black Belt who is already on the next project. Sustainment belongs to the process owner (and operating system), with belts available for coaching if metrics drift.
Coach and facilitator
A coach improves a person’s or team’s capability (how to run a DOE, how to facilitate VOC). A facilitator manages group process in a meeting: agenda, equal voice, decision clarity. The Green Belt often facilitates their own workshops; for high-conflict sessions, a neutral facilitator helps. Coaching and facilitating are how work happens; they do not replace champion authority or process ownership.
Process owner and team members
The process owner is accountable for end-to-end process results after the project. Team members map the real process, collect data, pilot standard work, and often become informal trainers for peers. Without process owner engagement, Control fails. Without team members, analysis is ivory-tower and solutions do not stick on the floor.
RACI Matrix
RACI clarifies involvement for each major activity:
| Letter | Meaning | Rule of thumb |
|---|---|---|
| R | Responsible — does the work | Can be several people |
| A | Accountable — final decision / ownership | Prefer exactly one A per activity |
| C | Consulted — two-way input before decision | SMEs, adjacent owners |
| I | Informed — one-way update after decision | Broader stakeholders |
Example — claim cycle-time project (fragment)
| Activity | Green Belt | Process owner | Champion | IT analyst | Examiners (team) |
|---|---|---|---|---|---|
| Draft project charter | R | C | A | I | C |
| Collect baseline cycle-time data | A/R | C | I | C | R |
| Approve scope change adding system redesign | C | C | A | R (estimate) | I |
| Pilot new checklist | R | A | I | I | R |
| Own post-project control metrics | C | A | I | I | R (daily work) |
Notes for Apply-level thinking:
- Two As on the same row create paralysis (“I thought you owned it”).
- Putting A only on the Green Belt for sustainment metrics is wrong after Control handoff.
- C vs I: if you need their expertise before deciding, they are C; if they only need to know the outcome, they are I.
- Some organizations use RASCI (adds Support) or CAIRO; for CSSGB, master classic RACI.
Building RACI on a Green Belt Project
- List 8–15 critical activities across DMAIC (charter approval, data collection, MSA, root-cause selection, pilot, control plan sign-off).
- List roles (not only named people—roles survive reorgs).
- Assign R/A/C/I; challenge every blank and every double-A.
- Review with champion and process owner in Define; update when scope changes.
- Use the matrix in meetings: “Who is A on this decision?” ends circular debate.
Common Role Mix-Ups
| Confusion | Correct distinction |
|---|---|
| Champion vs process owner | Champion prioritizes and protects the project; process owner runs the process after |
| Facilitator vs leader | Facilitator manages discussion quality; champion/process owner still hold decisions |
| Coach vs doer | Coach develops capability; Responsible parties still execute |
| Black Belt vs Green Belt | Scope, complexity, and often time allocation—not “GB never uses stats” |
Exam Focus
Expect stems such as: who removes a resource roadblock (champion); who accepts the control plan (process owner); who mentors statistical methods across many projects (MBB); who fills most cells as R on analysis tasks (belt + team); which RACI letter is missing when two directors both think they can veto (two A’s or unclear A).
Apply role knowledge with RACI in Define, revisit it at Improve and Control, and you will protect both project speed and long-term results.
A pilot is ready, but the plant manager will not free two operators for training until a VP intervenes. Which role is primarily responsible for removing this organizational barrier?
On a RACI for ‘approve final control plan and metric ownership after project close,’ which assignment is most appropriate?