Deciding how work will happen.
WHAT TO RESIST
Reproducing current processes exactly.
WHY
Current processes were shaped by the current system's limitations.
WHAT TO ASK OF EACH PROCESS
Why is it done this way?
WHAT THE ANSWER FREQUENTLY IS
Nobody remembers.
WHAT TO DO ABOUT SUCH PROCESSES
Adopt the system's standard approach.
WHAT TO PRESERVE
Process that is a genuine competitive advantage Process required by regulation Process serving a real need
WHAT CONFIGURATION COVERS
Organisational structure Chart of accounts Document numbering Approval workflows User roles and permissions Defaults and rules
WHY THE CHART OF ACCOUNTS MATTERS ENORMOUSLY
It determines reporting, and changing it after go-live is disruptive.
WHAT TO DOCUMENT
Every configuration decision, and why.
WHY
The reason is forgotten, and it is asked about for years.
WHAT TO TEST DURING CONFIGURATION
Each process, as it is configured.
WHAT TO AVOID
Configuring everything before testing anything.
WHAT TO INVOLVE
The people who perform the process.
WHY
They identify exceptions nobody else knows about.
