The two paths: DMAIC & DMADV
Six Sigma has two major methodologies. DMAIC improves an existing process (Define · Measure · Analyze · Improve · Control). DMADV – also called DFSS – designs something new from scratch (Define · Measure · Analyze · Design · Verify). Pick a case and switch the variant: just like the car company in the video that improves its production (DMAIC) and at the same time designs a new sports car (DMADV). Then go through phase by phase – with meaning, application and the typical tools.
Which variant? DMAIC or DMADV
One question decides: does the process already exist – or are you building it from scratch? Both share D · M · A, then they part ways.
DMAIC
A product or process already exists and should get better – fewer defects, faster, more stable. The most common Six Sigma methodology.
DMADV
There is nothing yet – a new product or service is being created. Also called DFSS (Design for Six Sigma).
Click a card or use the switch below – the selected case is kept.
Phase walk-through (guided)
For each phase: what it means, what it looks like in the case and which tools are typical. Technical terms are underlined.
Define
DefineDMAIC ↔ DMADV side by side
Same start (D · M · A), different end – improve vs. design anew.
Context: Lean & Lean Six Sigma
As the video shows at the end – a second school of thought and the combination.
Reduce variation & defects
Data-driven via DMAIC / DMADV – so that the process becomes predictable.
Eliminate waste
From Japanese manufacturing (Toyota): remove everything that brings the customer no value. More with less – and better at the same time.
Lean Six Sigma
Both together: eliminate defects (Six Sigma) and remove waste (Lean) to meet customer needs better.
Video companion · Questions & answers
The methodology in plain language – with the car plant example from the video. Click a question.
Terms & tools explained +
The most important terms of both methodologies and the tools named in the tool – briefly explained:
How saving works +
This HTML file is your document. Everything you enter is saved in this very file, just like a Word document. If you share the file, all project plans are included.
Save (green button or Ctrl+S) stores the current state – without any prompt. As long as no working file of your own has been created, the state is kept in the browser and is there again the next time you open it.
Save as (under “Projects”) creates a file on your drive. This is the only time you are asked where to save. After that, every further Save writes silently into exactly that file.
The first time: open the file, click “Projects”, then Save as. From then on, just use the green button.
Autosave: once a project plan has been saved, the tool automatically saves every further change after a few seconds.
If something goes wrong: the tool continuously keeps an interim state in the browser. If the browser crashes or you close the window by accident, your work is there again the next time you open it.
Note on browsers: writing directly to the file currently works in Chrome and Edge. In Firefox and Safari everything stays saved in the browser – the file itself remains unchanged.