Use this SOP to reengineer your business processes to stop wasting time and money on inefficient ways of working.
1
Identify the process to be reengineered
2
Assign the task of reengineering to team members
3
Read the current process documents
4
Create a process map
5
Draft a new process map and SOP
6
Test the process
Identify the process to be reengineered
If you're deciding to reengineer, it might be obvious which process needs changing. If not, you need to keep some things in mind when selecting.
When deciding on a process to change, ask yourself if the process is:
1
Dysfunctional
2
Important
3
Feasible to alter
Note below which process will be changed:
Assign the task of reengineering to team members
It's best to assign the task of reengineering a specific process to a team member who knows that process intimately. This might be the person who first made it, or the person who runs it regularly.
Assign the task of reengineering to the right person, and use the 'Assignees' feature to assign the rest of the checklist tasks to that person.
Read the current process documents
Assuming the process is documented, now you need to refresh and familiarize yourself with the ins and outs of the process.
Create a process map
Follow this process to create a process map before moving onto the next task.
Draft a new process map and SOP
After analyzing the process and mapping it, it should be clear where the areas of inefficiency are.
Can part of it be automated? Is data being passed manually between departments? Are you still using paper?
The idea of BPR isn't just to slightly tweak a bad process like you would do when optimizing. If it's bad, it may need rebuilding from the ground up with no semblance of its original self.
Test the process
In line with Agile testing and workflow improvement, which share many similarities with BPR, now it's time to test the first draft of the process. It doesn't have to be perfect because battle-testing the process will be the only real way to get close to a final version.
After testing, more analysis and iteration follows.
