Hal Cranmer teaches 5 Whys

1/ Hal Cranmer resurfaced a simple manufacturing habit with a finance use case: ask “why?” repeatedly—up to five times—until you get past the symptom and into the cause chain. The 5 Whys is a standard root-cause method in manufacturing and lean operations. (augmentir.com) 2/ The core idea is straightforward. You start with a specific problem, take the first answer, then ask why that condition existed, and keep going until you reach a correctable underlying cause rather than a visible effect. “Five” is usually a guide, not a hard rule. (flowfuse.com) 3/ In plant settings, that matters because teams often stop at the first observable failure: the line stopped, the defect rate rose, the shipment was late. The 5 Whys is meant to push beyond that into process gaps, training issues, maintenance lapses, documentation failures, or system design problems. (augmentir.com) 4/ A manufacturing example looks like this: a packaging line stops; why? a sensor fault shut it down; why? contamination blocked the sensor; why? cleaning frequency slipped; why? the standard work was unclear; why? ownership of the task was never assigned. That is the shift from event to root cause. (augmentir.com) 5/ Cranmer’s useful twist is that the same logic fits FP&A work, especially in consumer packaged goods. Variance analysis often stops too early: “margin missed because volume was weak” or “costs were up because materials inflated.” The 5 Whys forces a second, third, and fourth layer. The social briefing tied his post directly to variance decomposition in manufacturing and CPG operations. (learnleansigma.com) 6/ In finance, the chain might run like this: gross margin missed plan; why? promo spend was higher; why? sell-through slowed in a key channel; why? price-pack architecture lost competitiveness; why? input-cost inflation pushed list prices up unevenly; why? the category response lagged a rival move. That is a management story, not just a bridge chart. 7/ The method is useful because it changes the output. Instead of ending with “unfavorable mix” or “higher conversion cost,” a team can end with something actionable: a maintenance schedule, a training fix, a customer-specific pricing review, a forecast assumption, or a handoff problem between sales and supply chain. Root-cause work is only valuable if it points to a fix. (reliability.com) 8/ It also has limits. Lean and reliability guides warn that the technique can fail if the starting problem is vague, the team guesses instead of using evidence, or the exercise turns into blame assignment. The answers have to be grounded in facts from the line, the ledger, or the process—not instinct alone. (learnleansigma.com) 9/ That is why the best use case is narrow and concrete. Pick one defect, one downtime event, one customer miss, one price-volume-mix variance, one working-capital surprise. Then document each answer, test whether it is true, and stop only when the team reaches a cause it can actually change. (flowfuse.com) 10/ For finance leaders, Cranmer’s post lands at a moment when FP&A is being pushed toward better driver explanation, not just faster reporting. The 5 Whys is old, but the reminder is current: if a team cannot explain why a number moved beyond the first layer, it probably has not finished the analysis.