An honest look at what didn't work. Not the polished version.
Hansei is one of the least translated lean practices because no English word quite captures it. The closest is "reflection," but reflection in American business culture is usually polished and forward-looking. Hansei is the opposite. It is the deliberate, sometimes uncomfortable, honest accounting of what went wrong and why. The discipline matters because most teams cannot learn from failures they refuse to name, and most organizations are built to gloss over the naming.
"The retrospective tells you what happened. Hansei tells you what you did about it."
A hansei session is held after a milestone: a finished project, the end of a quarter, the end of a year. The format is usually structured around three questions: what did we set out to do, what did we actually achieve, and where did we fall short. The third question is where most of the time goes. The team discusses specific shortfalls, the decisions that contributed, and what should be done differently going forward.
What makes hansei different from a standard lessons-learned exercise is the expectation of personal accountability. A lessons-learned write-up tends to attribute failures to abstract causes: communication, resources, scope. Hansei asks each person to name a specific decision or behavior of their own that contributed to the outcome. "I prioritized the wrong customer in week three." "I did not push back on the supplier promise in November." "I left the new operator without a clear standard for too long." The honesty is uncomfortable, which is why hansei only works in cultures where senior people go first.
The output of a useful hansei is small and specific: usually two to four commitments for what will change in the next cycle, each with a named owner. The commitments are not improvement projects; they are behavioral changes the team is agreeing to. The session itself takes one to three hours. If it takes much longer, the team is performing rather than reflecting.
Imagine the owner of a 30-person plastics injection shop that just finished a large rush order for a regional grocery chain. The order shipped two weeks late and quality on the first run was rough enough that the customer asked for a credit. The instinct of most owners is to focus on the recovery (we held the customer, we made it work) and move on.
Hansei would slow that down. The owner blocks 90 minutes the week after the order ships. They sit with the production lead, the shift supervisor, the QC lead, and the planner. Two questions: what specific decisions of mine contributed to this missing, and what would I do differently next time. The owner goes first and is specific: I accepted the rush order without checking the maintenance schedule on press three, and the unplanned shutdown in week two was foreseeable. The QC lead names their own miss: I signed off on the first run despite the color variation because I did not want to delay shipping. By the end of the session there are three commitments, each with an owner. The next rush order misses different things, which is the point.
Hansei is the backward-looking reflection that fuels forward-looking kaizen, the daily improvement habit. It often happens after a kaizen event or other defined project. The structured cycle most teams use to act on hansei findings is plan-do-check-act, which gives the commitments a place to live. The mechanism that takes a single team's hansei lessons and spreads them to other areas is yokoten, horizontal sharing of improvements across the organization.
The questions we hear most about this term.
Long-form guides that pick up where this definition leaves off, written for manufacturers running Arda today.
Same-day setup. No distributor lock-in. Zero stockouts. Top teams double revenue in 9 months.
.svg)
.svg)
%201.svg){kind=logo}
.png)
.svg)
.svg)
