PLATFORM
Configuration Settings
Maintain system preferences in one place as part of rollout.
Who uses it ERP administrators, implementation leads and business process owners
Why your business needs it
What goes wrong
Different teams apply different settings to the same process. Teams operating with different preferences can handle the same transaction differently. Training and support then have to account for exceptions nobody agreed to.
When to add it
You are adding a branch, onboarding a team or changing a process that staff must follow consistently.
What to measure
How many setup differences have a named business reason and owner before rollout?
Example business · Wholesale distributor
A business walkthrough
A second branch is preparing to go live. The project lead must decide which preferences should match the first branch and which differences are legitimate.
-
Review defaults
Compare current preferences with the new branch’s needs
-
Set preferences
Agree the defaults and document exceptions
-
Confirm rollout
Walk through a sample task to see whether the setup matches the agreed process
System settings
This diagram could not load. The key and walkthrough describe the same process.
- Keys
- Individual settings
- Pressed key
- The setting being changed
- Neighbouring keys
- Related settings it affects
The keys represent individual settings. Review what should be standard across the organization before rolling out to another branch.