Process Confirmation
The discipline of checking whether the expected standard is being followed and whether the expected result is being achieved. This guide covers what to check, how to respond to what you find, and how to connect confirmation to your management system.
A standard that nobody checks is not a standard. It is a suggestion.
Process Confirmation is the discipline of going to where the work is done, checking whether the expected method is being followed, and checking whether the expected result is being achieved. It is not an inspection. It is not a performance review. It is a structured check of the management system, to find out whether the system is producing the behaviour and the results it was designed to produce.
Done well, Process Confirmation catches drift before it becomes a problem. It tells you whether your standards are realistic, whether your people have what they need, and whether the process design is actually working. Done poorly, or not at all, it leaves you managing results you cannot explain, with no reliable way to understand why.
What it is
Process Confirmation checks two things
Did we do what we said we would do? Is the work being done the way it was designed to be done? Is the method, sequence, timing, or condition as specified?
Did we get what we expected to get? Is the output, measure, or outcome what the process was designed to produce?
These two questions are asked together, every time. The relationship between them is where the learning is.
A process that is followed correctly and produces the right result is a stable process. A process that is followed correctly but produces the wrong result has a design problem, an input problem, or a condition problem, not a people problem. A process that is not being followed but still produces the right result is a process where the standard may be wrong, unnecessary, or poorly understood. A process that is not being followed and is not producing the right result needs the standard to be restored before anything else is attempted.
Process Confirmation is not about catching people out. It is about understanding the relationship between the method and the result, and using that understanding to improve the system.
Why it matters
Most operations manage results. They measure output, yield, downtime, and cost. When the result is wrong, they investigate. When the result is right, they move on.
The problem with managing results alone is that by the time the result is wrong, the process has already drifted. The standard has been quietly abandoned, adapted, or forgotten. The investigation finds a symptom, not a cause. A countermeasure is applied. The result improves. The standard is still not followed. The result drifts again.
Process Confirmation breaks that cycle. It checks the method before the result deteriorates. It finds the drift while it is still small. It gives the leader something to act on, not a number that is already wrong, but a process that is moving in the wrong direction.
It also does something that result management cannot do: it tells you whether your standards are right. If the standard is being followed and the result is still wrong, the standard needs to change. That is not a failure. That is the management system working as it should.
Potential outcomes
Every Process Confirmation produces one of four outcomes. Each one tells you something different, and each one requires a different response.
Standard followed? | Result achieved? | What it tells you | What to do |
|---|---|---|---|
Yes | Yes | The process is stable and performing as designed. | Confirm and record. If improvement is needed, ask whether there is a simpler, more robust, or quicker way to achieve the same result. Do not change a stable process without a reason. |
Yes | No | The method is correct but the result is wrong. The problem is in the process design, the inputs, the conditions, or the measures — not the people. | Investigate why the expected result is not being achieved. Check inputs, conditions, equipment, and process design. Raise in the next Tiered Accountability Meeting with a named owner. |
No | Yes | The standard is not being followed, but the result is acceptable. This is a signal, not a success. | Understand why the work is deviating. Is the standard wrong? Unnecessary? Poorly understood? Being bypassed for a valid reason? Decide whether the standard or the method needs to change. Do not ignore this outcome. |
No | No | The standard is not being followed and the result is wrong. | Return to the expected standard at the next opportunity. Make the standard clear and available. Confirm again. If the result remains wrong after the standard is restored, escalate and problem-solve. |
The most important outcome to understand is the third one: standard not followed, result acceptable. It is tempting to treat this as a non-issue. The result is fine. Move on.
Do not move on. A result that is achieved without following the standard is a result that cannot be relied upon. You do not know why it worked. You cannot replicate it. You cannot improve it. And when it eventually fails, which it will, you will have no baseline to return to.
The standard exists for a reason. If the reason is no longer valid, change the standard. If the reason is still valid, restore the standard. Either way, the deviation needs a response.
Confirmation checklist
A Process Confirmation is only as good as the list behind it. A general walkthrough is not a confirmation. A structured check with a defined standard is.
For each process you confirm, define the following before you go to the floor:
Field | What to record |
|---|---|
Process | The name of the process or standard being checked |
Standard | What the expected condition, method, or behaviour looks like |
Check method | How you will verify it — observation, measurement, conversation, visual check |
Frequency | How often this confirmation is scheduled — daily, weekly, or at a defined trigger |
Expected condition | What you expect to find if the standard is being followed |
Actual condition | What you actually find |
Result expected | The output or measure the process should be producing |
Result actual | The output or measure you observe or record |
Outcome | Which of the four outcomes applies |
Action | What needs to happen next, if anything |
Owner | Who is responsible for the action |
Follow-up | When the action will be reviewed |
Not every process needs every field completed every time. A stable process that consistently produces the right result needs a brief confirmation and a record. A process showing deviation needs the full set.
Start with the processes that are most critical to your strategic objectives. If a process failure would directly affect a key measure, safety, quality, output, cost, that process belongs on your confirmation list. Build from there.
How to confirm a process
A Process Confirmation is a structured observation, not a conversation about results. Go to where the work is done. Observe the process against the standard. Record what you find. Ask questions that help you understand the process, not questions that put the person on the spot.
Useful questions during a confirmation:
- Can you show me how this step is done?
- What does the standard say should happen here?
- What would tell you that this process is not working correctly?
- What would you do if you found it out of condition?
These questions confirm understanding and capability. They are not a test. They are a way of finding out whether the standard is clear, available, and understood, and whether the person has what they need to follow it.
If you find a deviation, record it. Do not correct it in the moment unless there is an immediate safety or quality risk. The purpose of the confirmation is to understand the system, not to fix individual instances. The fix comes through the action and follow-up process.
If you find that the standard itself is the problem, unclear, unrealistic, or no longer relevant, that is a process improvement task, not a disciplinary one. Raise it, own it, and change it.
Leader Standard Work connection
Process Confirmation does not happen by chance. It happens because it is scheduled.
Leader Standard Work (LSW) is the mechanism that makes confirmation visible and consistent. Your LSW schedule defines which processes you confirm, when you confirm them, and how often. Without that schedule, confirmation is reactive, it happens when something goes wrong, not before.
When building your LSW, identify the processes that are most critical to your area's performance and your strategic objectives. Schedule confirmations for those processes at a frequency that matches their risk. A high-risk process in a new or recently changed state may need daily confirmation. A stable, well-understood process may need weekly or monthly confirmation.
Your LSW also creates the Plan, Do, Check, Act (PDCA) cycle for confirmation itself. At the end of each week, review what you confirmed, what you found, and what you did about it. If you are consistently finding the same deviation, the standard or the system needs to change. If you are consistently finding everything in order, ask whether the confirmation frequency is still right, or whether there is a higher-risk process that needs more attention.
The principle from the Leader Standard Work guide applies here directly: the leader who does not have a standard cannot confirm that anyone else is following one. Your confirmation list is your standard for how you lead.
Strategic Objectives connection
Process Confirmation is not a general management activity. It is a targeted one. The processes you confirm should be the processes that most directly affect the results your strategic objectives require.
If your strategic objective is to improve first-pass quality, your confirmation list should include the processes most likely to produce defects. If your objective is to reduce unplanned downtime, your list should include the maintenance and changeover standards most likely to affect equipment availability. The confirmation list is how strategic direction becomes daily discipline.
This connection also works in reverse. When a confirmation consistently finds a gap between the expected result and the actual result, that gap is data. It tells you whether your strategic objective is achievable with the current process design. If the standard is being followed and the result is still not meeting the target, the target may be right but the process needs to change. That is a process improvement task, and it belongs in the improvement programme.
Tiered Accountability Meeting connection
What Process Confirmation finds, Tiered Accountability Meetings act on.
When a confirmation identifies a gap, a deviation from the standard, a result that is not being achieved, an action that has not been closed, that gap is raised in the next Tiered Accountability Meeting. It is given a named owner and a close-out date. It is reviewed at the next meeting. If it cannot be resolved at that tier, it moves up the same day.
This is the mechanism that prevents confirmation from becoming a recording exercise. The confirmation finds the gap. The meeting assigns the owner. The follow-up closes it out. Without the meeting, the confirmation list fills with open actions that nobody is accountable for. Without the confirmation, the meeting has no reliable source of what is actually happening in the process.
The two processes are designed to work together. Process Confirmation is the input. Tiered Accountability Meetings are the response.
Higher-tier leaders attending lower-tier meetings are also performing a form of Process Confirmation, confirming that the meeting system itself is working as designed, that the right information is being reviewed, that actions are being closed, and that the tier below has what it needs to function. This is Process Confirmation applied to the management system, not just the production process.
Sustainment
Process Confirmation is easy to start and easy to stop. The first few weeks tend to go well. The confirmations are scheduled, the list is fresh, and the findings are interesting. Then a crisis arrives. The confirmation is skipped. Then another crisis. Then the confirmation is no longer scheduled, it is aspirational.
This is the pattern that Leader Standard Work exists to prevent. When confirmation is in your LSW, it is protected. It happens unless there is a genuine emergency, not unless something more urgent arrives. And in a well-run operation, genuine emergencies are rare.
A few practical disciplines that sustain confirmation over time:
What this gives you
Common pitfalls
Process Confirmation is not a management add-on. It is the mechanism that tells you whether the management system is working.
Without it, you are managing results you cannot explain. With it, you are managing the processes that produce those results, and you have the information you need to improve them.
Key Links
This guide depends on:
Leader Standard Work is the mechanism that makes confirmation happen consistently. Without a scheduled confirmation in your LSW, it will be reactive rather than routine.
This guide connects to:
What confirmation finds, Tiered Accountability Meetings act on. The two processes are designed to work together.
The processes you confirm need a defined standard. Process improvement is how those standards are set and maintained.