Process Confirmation is a leadership routine used to verify that important process conditions and standards are present where the work actually happens.

The purpose is not to audit everything.

It is to confirm the few conditions that are essential to safe, stable, and predictable performance.

Confirm the process, not the person

A weak confirmation asks:

Is the operator following the rule?

A stronger confirmation asks:

  • Is the current standard clear?
  • Is the required tool available?
  • Is the process condition within the approved range?
  • Is the reaction plan understood?
  • Is the visual control current?
  • Is the work environment supporting the standard?

The focus should remain on the process.

Go to the Gemba

Gemba is essential because the real operating condition cannot be confirmed from a report.

The leader should observe:

  • actual work;
  • actual equipment;
  • actual material;
  • current abnormalities;
  • workarounds.

This helps identify gaps between documented expectations and real conditions.

Use Standard Work as the reference

Standard Work defines the best-known method for performing the work.

Process Confirmation tests whether the supporting system makes that standard practical and visible.

If the standard is repeatedly not followed, the leader should ask why.

Possible reasons include:

  • poor layout;
  • missing tools;
  • conflicting priorities;
  • outdated instructions;
  • unrealistic cycle requirements;
  • weak training.

Connect to Leader Standard Work

Leader Standard Work can define when leaders perform Process Confirmation and how findings are followed up.

This prevents confirmation from depending only on personal habit.

Process Confirmation vs Layered Process Audit

Layered Process Audits typically use structured audit questions across multiple leadership levels to verify critical controls.

Process Confirmation can be broader and more coaching-oriented.

The methods can complement each other.

Respond to abnormalities

When the leader finds a gap:

  1. protect safety or quality immediately if needed;
  2. understand the current condition;
  3. restore the standard where practical;
  4. identify why the gap exists;
  5. assign follow-up;
  6. verify closure.

Repeated gaps should move into problem solving rather than become recurring audit findings.

Common mistakes

Using Process Confirmation as policing, checking too many items, focusing on paperwork, accepting repeated findings, and failing to close the loop with employees are common mistakes.

Practical sequence

  1. select critical process conditions.
  2. define observable confirmation questions.
  3. integrate checks into leader routines.
  4. go to the Gemba.
  5. compare actual and standard.
  6. discuss abnormalities with the team.
  7. correct immediate risk.
  8. assign systemic follow-up.
  9. review recurring gaps.
  10. update the standard when learning justifies change.

The practical lesson

Process Confirmation keeps standards connected to reality.

The leader’s job is not simply to ask whether people complied, but to verify that the process is capable of supporting the expected work.