The 5 whys is a root cause analysis technique: starting from a problem, you ask why it happened, then ask why about that answer, repeating roughly five times until you reach a cause worth fixing. Sakichi Toyoda developed it, and it spread through the Toyota Production System into lean manufacturing and software practice. Its strength is its simplicity; no training or categories needed.

Five is a guideline, not a rule. The real stop condition is reaching a systemic cause your team can act on; sometimes that's three whys, sometimes seven. Two failure smells: stopping early because an answer feels satisfying ('the server crashed'), and stopping at a person ('Sam misconfigured it'), where the next why, about why the process allowed it, is the one that matters.

The famous one is the Jefferson Memorial: the marble was crumbling (why?) from heavy cleaning (why?) because of bird droppings (why?) because birds ate the spiders (why?) which ate the insects (why?) drawn by the lights at dusk. Root cause: lighting schedule. Counter-measure: turn the lights on later. Five whys turned a masonry problem into a lighting fix.

The 5 whys goes deep down one chain; the fishbone goes broad across categories. Use the 5 whys when the problem looks linear and singular: one symptom, probably one cause-path. Use a fishbone when causes could live anywhere: process, people, tools, environment. They combine well: fishbone first to map the candidates, then a 5 whys chain down the branch worth digging.

A counter-measure is the action attached to the root cause, and lean practice picked the word deliberately: it counters the cause you found, while 'solution' overpromises. In the Toyota machine example the counter-measure was adding a strainer to the pump intake, not 'be more careful with lubrication'. Good counter-measures change the system; if yours reads like a reminder to humans, ask another why.