Hansei is a Japanese concept commonly associated with reflection and self-examination.

In Continuous Improvement, it means reviewing what happened, identifying gaps, and learning how the next cycle can be better.

The important point is that reflection is useful even when the result was successful.

Success can hide weaknesses

Teams naturally investigate failures.

Success is less likely to receive the same attention.

But a successful result may still contain:

  • unnecessary effort;
  • hidden rework;
  • last-minute firefighting;
  • fragile controls;
  • excessive overtime;
  • dependence on one expert.

Hansei asks the team to learn from the process, not only the final result.

Reflection without blame

Hansei should not become self-criticism or a search for someone to fault.

Useful reflection asks:

  • What did we expect?
  • What actually happened?
  • What went well?
  • What was difficult?
  • Where did we deviate?
  • What should we change next time?

This supports a healthy Continuous Improvement Culture.

Hansei and PDCA

PDCA includes checking results and acting on what was learned.

Hansei strengthens that learning behavior.

The reflection creates information that should influence the next Plan phase.

Without reflection, PDCA can become a mechanical sequence rather than a learning cycle.

Connect reflection to Kaizen

Kaizen depends on repeated small improvements.

Hansei provides one source of those improvements.

After completing work, a project, or an operating cycle, the team can identify what should be standardized and what should be improved.

Useful reflection moments

Hansei can be used after:

  • a project;
  • a product launch;
  • a shutdown;
  • a major repair;
  • a customer complaint;
  • an improvement event;
  • a successful production run;
  • a missed target.

The review does not need to be long.

Consistency matters more than ceremony.

Capture lessons in the system

Reflection has little value if the same lesson is rediscovered repeatedly.

Important learning should update:

  • Standard Work;
  • training;
  • maintenance plans;
  • design standards;
  • checklists;
  • Control Plans;
  • project methods.

The objective is organizational learning.

Common mistakes

Reflecting only after failure, turning reflection into blame, collecting lessons without applying them, writing generic statements, and failing to assign follow-up are common problems.

Practical sequence

  1. Compare expected and actual results.
  2. Identify what went well.
  3. Identify gaps and unexpected conditions.
  4. Separate facts from opinions.
  5. Identify lessons.
  6. Decide what should change.
  7. Update standards or plans.
  8. assign ownership.
  9. Review whether the learning was applied.

The practical lesson

Hansei creates a habit of learning before the next problem forces the organization to learn.

Reflection turns experience into improvement.

This topic also connects with Yokoten. Use that method when the improvement requires the related operating or management discipline.

This topic also connects with After Action Review. Use that method when the improvement requires the related operating or management discipline.