Skip to content

Lean Six Sigma, Yellow Belt level: solving a problem with DMAIC

Managers, operations teams, department heads and project managers · 2 days (14 hours) · in-house, on site or remote

At a glance

Duration
2 jours (14 heures)
Format
On site and remote
Group size
12 participants maximum
Level
Beginner
Audience
Line managers and department heads facing a recurring quality, lead-time or workload problem
Prerequisites
No background in Lean, Six Sigma or statistics required: the session starts from scratch.
Methods
Short talks, never longer than twenty minutes, each followed by a workshop on the problem each participant brings.
Assessment
Beforehand: a positioning questionnaire (problem in mind, data available, continuous improvement experience) that sets the weighting between modules.
Lead time
Scheduled during framing, to suit your availability
Pricing
On a quote basis, depending on format, duration and number of participants. The first call is free.
Accessibility and disability
See the dedicated section

A recurring problem in a department is rarely solved in a meeting: everyone has a favourite cause, the solution is chosen before anything has been measured, and the problem is back three months later. DMAIC is a simple discipline for breaking that cycle: define the problem in one measurable sentence, measure before acting, trace it back to root causes, improve what matters, then control so that the improvement holds. These two days cover the content of the Yellow Belt level of Lean Six Sigma, meaning what a team member or a manager needs to know to contribute to an improvement project and to run a small one end to end. No advanced statistics: simple data, read with method. Each participant brings a real problem from their department, and the five steps are worked through on it, from the defined problem to the written standard.

Learning objectives

  • Phrase a problem in one measurable sentence, with its scope, its indicator and its quantified target.
  • Choose what to measure and collect simple data without distorting the result.
  • Read a data series with a few basic tools: tally sheet, histogram, Pareto chart, run chart.
  • Trace back to root causes with the 5 whys and the Ishikawa diagram, then verify a cause before treating it.
  • Spot Lean wastes in a service or production process and quantify them.
  • Select and test an improvement, then write it up as a standard the team can follow.
  • Put in place a simple control that signals when the problem comes back.
  • Contribute to an improvement project led by a Green Belt or a Black Belt, knowing the vocabulary and the expected deliverables.

Programme

01Day 1 · Why problems come back, and what DMAIC changes

1 h 30
  • The usual cycle: meeting, assumed cause, quick fix, problem returns.
  • The five DMAIC steps on one page: Define, Measure, Analyse, Improve, Control. What each step produces and what it forbids.
  • Lean and Six Sigma: two origins, one question (where is value being lost?).
  • Yellow Belt, Green Belt, Black Belt: who does what in a project, and what this session covers.
  • Round table: each participant presents their problem in two minutes, the group notes what is missing to measure it.

02Day 1 · Define: the problem, the scope, the indicator

2 h 30
  • Writing a problem statement: what, where, since when, how much, and what it costs.
  • Setting the scope: the process concerned, its start, its end, what is left out.
  • Choosing the indicator that says whether the problem is solved, and the quantified target.
  • Mapping the process in a few steps (SIPOC) so that everyone talks about the same one.
  • Workshop: one-page project charter on the problem brought in, peer-reviewed across sub-groups.

03Day 1 · Measure: collecting and reading simple data

3 hours
  • Deciding what to measure, how often, by whom, with which tally sheet.
  • Measurement traps: sample too small, unrepresentative period, definition that varies from one person to the next.
  • Reading data without advanced statistics: histogram, Pareto chart, run chart.
  • Telling normal variation from a real change: the question most meetings never ask.
  • Workshop: data collection plan for the problem brought in, then reading a supplied data set with the tools covered.

04Day 2 · Analyse: tracing back to root causes

3 hours
  • The 5 whys: following the causal chain without stopping at the first culprit.
  • The Ishikawa diagram: organising possible causes by family, then selecting those to verify.
  • Verifying a cause with data before treating it: what separates an analysis from an opinion.
  • Lean wastes in a service or production process: waiting, rework, transport, overproduction, inventory, over-processing, motion.
  • Workshop: Ishikawa and 5 whys on the problem brought in, then waste hunt on the process map.

05Day 2 · Improve: test, standardise

2 h 30
  • Generating several solutions before choosing one, and sorting them on two axes: expected effect, ease of implementation.
  • Testing on a small scale before rolling out: one pilot, one period, one indicator.
  • Writing a standard the team can follow: one page, steps, an owner.
  • Getting buy-in: who has to change the way they work, and what will help them do it.
  • Workshop: improvement plan for the problem brought in, with its pilot test and its standard.

06Day 2 · Control, close out and assessment of learning

1 h 30
  • Putting in place a simple control: the indicator tracked, the frequency, the alert threshold, who reacts.
  • Closing a project: result obtained, what was learnt, what is transferable.
  • Each sub-group presents the DMAIC file produced over the two days.
  • Validation quiz covering the five steps, corrected in the room.
  • Individual action plan: the next steps of the project brought in, with dates.

Who it is for

  • Line managers and department heads facing a recurring quality, lead-time or workload problem
  • Operations, back-office, production or support teams that want to solve their problems with method
  • Project managers steering an improvement project without having the method
  • Teams working with a Green Belt or a Black Belt and having to feed their analyses
  • Small and mid-size companies starting a continuous improvement approach without a dedicated team

What you take away

  • The one-page project charter for your problem: statement, scope, indicator, target.
  • The map of the process concerned and its data collection plan.
  • The cause analysis (Ishikawa, 5 whys) and the list of wastes spotted.
  • An improvement plan with its pilot test and a one-page standard.
  • A control plan: indicator, frequency, alert threshold, owner.
  • Blank templates for the five steps, reusable on the projects that follow.
  • The full material for the two days.

Prerequisites

  • No background in Lean, Six Sigma or statistics required: the session starts from scratch.
  • Being able to use a spreadsheet to enter data and draw a simple chart.
  • Bringing a real problem from your department, with an order of magnitude of its frequency: it is the common thread of the two days.

Teaching methods

  • Short talks, never longer than twenty minutes, each followed by a workshop on the problem each participant brings.
  • A supplied data set to practise reading, before applying the tools to the participants' own data.
  • Sub-groups of three to four participants, with peer review of charters, analyses and improvement plans.
  • Tools kept at Yellow Belt level: tally sheet, Pareto chart, histogram, Ishikawa, 5 whys, process mapping. No advanced statistics.
  • Field stories from real improvement projects: what was measured, what was found, what held over time.
  • One-page templates filled in during the session, in a plain spreadsheet.

Assessment of learning

  • Beforehand: a positioning questionnaire (problem in mind, data available, continuous improvement experience) that sets the weighting between modules.
  • During the session: the project charter, the collection plan and the cause analysis are assessed against a grid handed out at the opening (measurable problem, usable data, verified cause).
  • Data reading exercise on a supplied data set, corrected in the room.
  • At the end: presentation of each sub-group's DMAIC file, assessed on the consistency between problem, measurement, causes and the improvement chosen.
  • At the end: a validation quiz covering the five steps, corrected and discussed in the room.
  • A few weeks later: a remote check-in, outside training hours, on the progress of the project brought in and the indicator tracked.

Where what I teach comes from

Adrien Bouthet, freelance IT project manager and Product Owner based in Bordeaux, eight years steering digital projects, holder of the Six Sigma Black Belt (CSSC, 2023). I do not teach DMAIC as a theory: it is the discipline I apply when a project or a process does not deliver the expected result. On the document platform migration run for La Banque Postale and Caisse des Dépôts, I took over a late project and brought it back on track in under three months; 500 million documents were migrated and licence costs were cut from 600,000 EUR to 20,000 EUR per year. It is a result from a steering assignment, not a promise made to participants. At EDF I steered a demand management application handling around 20,000 tickets a year, across an estate of 3,000 to 5,000 workstations: dealing with an incident at its cause is already root cause analysis. I have been teaching in schools since 2020.

Real example

A steering reference, not a DMAIC assignment: on the document platform migration for La Banque Postale and Caisse des Dépôts, 500 million documents migrated, a late project brought back on track in under three months, and licence costs cut from 600,000 EUR to 20,000 EUR per year. An assignment result, not a promise made to participants.

Read the case study

Frequently asked questions

Does this session award a Yellow Belt certification?+

No. This session does not award a Yellow Belt certification; it covers its content. 'Yellow Belt' here refers to the level of the tools taught: what a team member or a manager needs to know to contribute to an improvement project and to run a small one. Participants who wish to sit an exam with an awarding body do so separately, with this content as a basis.

Do I need a statistics background?+

No. Yellow Belt level stops at tools anyone can read in a spreadsheet: tally sheet, histogram, Pareto chart, run chart. Statistical tests and design of experiments belong to Green Belt and Black Belt levels and are not on the programme.

Do we work on our own problems or on a textbook case?+

On yours. Each participant brings a real problem from their department, chosen with you during the preparatory call. A supplied data set is only used to practise reading before applying the tools to your own records. The DMAIC file produced over the two days is that of your problem.

Does it apply to a service department, not just a factory?+

Yes. The examples come as much from service processes (request handling, back office, support) as from production. Lean wastes exist in a flow of files as much as on a shop floor: waiting, rework, over-processing. Mapping and measurement adapt.

On site or remote?+

Both. On site at your premises, in Bordeaux and across Nouvelle-Aquitaine, or remotely anywhere in France. The remote format keeps the sub-groups and the peer review. The two days can be consecutive or one to two weeks apart, to leave time for a first data collection in the field.

How many participants at most?+

Twelve. Beyond that, peer review of the charters and cause analyses no longer fits the stated durations, and the first day's round table becomes too long for each problem to be properly examined.

How is this different from a continuous improvement assignment?+

Training makes your team self-sufficient on the method, at the scale of problems it can handle on its own. On a continuous improvement assignment, I am the one leading the project on a broader problem, with the team. The two combine: train the team, then run the heaviest project together.

Framework and terms

Funding

These sessions are invoiced directly to the company, out of its own skills development budget. They are not eligible for pooled funding schemes (OPCO, CPF, France Travail), which require Qualiopi certification.

Certification

This session is not a certifying course. I do not deliver any Scrum.org, Scrum Alliance, Scaled Agile (SAFe) or PeopleCert (ITIL) certification, nor any qualification registered with the RNCP or the Répertoire spécifique. The goal is operational: practices you can apply, not a diploma.

Contractual framework

Each session is covered by a professional training agreement (convention de formation professionnelle) signed before the start, setting out the objectives, the programme, the duration, the delivery arrangements and the agreed fee. The internal rules applicable to the session are handed to participants at the opening.

Certificate of attendance

A certificate of completion is handed to each participant at the end of the session. It states the objectives, the nature and the duration of the training, along with the results of the assessment of learning.

Accessibility and disability

Disability referent: Adrien Bouthet, contact@adrienbouthet.fr. Any situation requiring an adjustment (access to the premises, adaptation of the materials, of the pace or of the assessment arrangements) is examined during the framing phase, within 5 working days. If the adjustment exceeds our means, we refer to specialised resources (Agefiph, Cap emploi).

A recurring problem to solve with method

Book a free first call. We list the problems in your departments, pick those that will serve as the common thread of the two days, and set the dates.