Who Does What in Lean Six Sigma: Reading the Belts Without the Myths
When a project lands on someone with a Lean Six Sigma certificate, the assumption is often that the colour of the belt tells you what they can do. It does, but only roughly, and only if the work is scoped to match. After two years of disrupted operations many teams rushed people into improvement projects to claw back the efficiency they lost. Some of those projects stalled, and the cause was rarely the method. It was a mismatch between the belt and the assignment.
The belt structure is a rough map of how much statistical depth, project scope, and coaching responsibility a person carries. Used well it gives a team a shared language. Used carelessly it becomes a hierarchy that nobody questions until a project goes sideways.
What each belt is actually for
White and Yellow Belt. These are awareness levels. A Yellow Belt understands the DMAIC cycle, can read a process map, gathers data, and supports a larger effort. They are the people who make a project real on the floor, not the people who run it alone.
Green Belt. A Green Belt leads small, well-bounded projects part time while keeping their day job. They are comfortable with the core toolkit: process mapping, basic capability analysis, hypothesis testing, and root-cause work. They are not expected to run a complex multi-site redesign.
Black Belt. A Black Belt works on improvement full time, handles harder statistics and cross-functional projects, and coaches Green Belts. This is the level where change management matters as much as the maths.
Master Black Belt. A Master Black Belt sets strategy, trains and mentors Black Belts, and aligns the improvement portfolio with the organization's goals. There are very few of them, and they should not be doing routine project work.
The mistakes that quietly sink projects
Treating belts as a career ladder. A Black Belt is not a promotion above a Green Belt; it is a different scope of work. Reward the work, not the colour.
Handing a Green Belt a Black Belt problem. A part-time improver with a part-time toolkit cannot carry a strategic, cross-departmental redesign. The project drags, and the person burns out.
Certifying without a real project. A belt earned from a classroom and a quiz, with no completed project behind it, tells you someone sat through training, not that they can deliver results.
Forgetting the sponsor. Belts run projects; they do not authorize change or free up budget. Without an executive sponsor with real authority, even a strong Black Belt stalls.
Ignoring the part-time math. A Green Belt who already has a full plate will not find ten hours a week by willpower. If the time is not protected, the project does not happen.
A useful test before you assign anyone: name the project's scope, the data complexity, and how many departments it crosses. Then match that to the belt, and confirm the person has protected time and a sponsor. If any of those three is missing, fix it before the kickoff, not at the first stalled gate review.
Getting the fit right
The strongest improvement programs treat belts as a portfolio. Yellow Belts keep small fixes moving in daily work. Green Belts take on contained projects with clear boundaries. Black Belts handle the gnarly cross-functional problems and coach the Green Belts beneath them. A Master Black Belt, where one exists, keeps the whole thing pointed at what the business actually needs. Get the match right and the method does its job; get it wrong and even good people produce slow, frustrating work.
If you are building improvement capability and want to match the right people and projects to real business priorities, XNM's strategic advisory can help you structure the program before you assign a single belt.