Countermeasures, implementation and standardisation
Step 1 / 4·Why Toyota says 'countermeasure', not 'solution'
0/4 steps done
Learning objectives — after this module you will:
- Design countermeasures aimed at the root cause
- Plan implementation with clear owners and metrics
- Do the Check – Act steps most organisations skip
Why Toyota says 'countermeasure', not 'solution'
Understand the thinking behind how corrective actions are chosen.
Toyota deliberately uses COUNTERMEASURE rather than 'solution'. 'Solution' implies the problem is permanently done; 'countermeasure' acknowledges this is the best action we know RIGHT NOW, to be validated against actual results and possibly adjusted. It's a far more humble and realistic stance.
The rule for choosing one: every countermeasure must CONNECT to a root cause you've analysed. If you can't name which cause it targets, it's just a nice idea — not a countermeasure.
Testing a countermeasure before choosing it
| Test question | Why it matters |
|---|---|
| Which root cause does it target? | If you can't answer, you're treating a symptom |
| Can we do it with current resources? | A great but infeasible countermeasure is worthless |
| Who owns it and by when? | Without a name and a date, it won't happen |
| Which metric tells us it worked? | If you can't measure it, you can't decide to keep or drop it |
| Any side effects? | Fixing here can create a new problem elsewhere |
Favour 'cheap and fast' countermeasures first
Don't wait for the perfect solution. Pick 1–2 countermeasures you can implement in a few weeks, measure the result, then scale if it works. This gets results quickly to build confidence and carries far less risk than a six-month project.
Key takeaway: A 'countermeasure' is the best action we currently know, and must connect to a specific root cause.