Operational change.
WHAT TO ESTABLISH BEFORE CHANGING A PROCESS
What it currently is, actually Why each step exists Where the problem is What the change addresses
WHY THE ACTUAL PROCESS
The documented process and the real one differ, and the real one is what changes.
HOW TO ESTABLISH IT
Observe it, and follow a transaction through.
WHAT THAT REVEALS
Steps nobody mentions Workarounds Checks that are skipped Who really decides
WHAT TO INVOLVE
The people performing it.
WHY
They know where the problems are and they will be operating the new way.
WHAT TO AVOID
Designing a process without those who perform it.
WHY
It produces something impractical that is quietly ignored.
WHAT TO TEST
The new process, on real work, in a limited way.
WHAT TO ESTABLISH DURING THE TEST
What does not work What was not anticipated Whether it is actually better
WHAT TO ADJUST
The process, before wider implementation.
WHAT TO DOCUMENT
The new process, clearly.
WHAT TO REMOVE
The old documentation and the old forms.
WHY
Their availability perpetuates the old way.
WHAT TO ESTABLISH
That the change is expected, and that it is checked.
WHAT TO CHECK
Whether it is being followed, weeks later.
WHAT TO DO ABOUT DEVIATION
Establish why.
WHY
It usually indicates a genuine problem with the new process.
