One of the things you don’t want to do when you convert manual processes to an automated system is keep inefficiencies or redundant steps in a process, so it’s important to take your “as is” processes and change them to “to be” before you begin the new system design.
It sounds simple, right? Just look at the “as is” map, move a few boxes here and there, scratch out stuff that’s not needed and you’re done.
Well, not quite. Remember you’re dealing with people here.
If you just start whacking steps in the process map, you are taking away work that people perform. And before you know it, you’ll have a whole bunch of irate people worried that their jobs are going away.
Now that may end up being the case in the long run or it may just be a change to someone’s job, but you need these people to help you get the “to be” process right. It’s their job and they know why a certain step is done. You’ll have much greater success if you involve them in the creation of the new process map.
Hopefully you took the time to conduct a business process assessment at the outset of your project. Make sure you thoroughly review that assessment report and take note of issues that will impact the area you are targeting. This will provide you with good background on areas needing improvement.
If possible, get the key sponsors of the project to communicate the purpose behind changing processes and implementing a new system to the people who will be affected. Absence of communication tends to drive the rumor mill when it comes to changes in an organization, so do your best to get everyone on board.
It’s also helpful to be informed about the internal politics of the organization as this can single handedly derail even the best process change strategy.
The best way to get to the new map is to gather the same people together who created the “as is” process maps in a meeting room. If you’ve worked with them before, you should have a good foundation of trust that will help make this session go smoothly.
1) Start with the current “as is” process map displayed for all to see. One of the easiest ways to do this is to use a projector connected to a laptop.
2) Walk through the process with the group to verify nothing has changed and confirm the map is accurate with the current process.
3) Proceed through the “as is” map step-by-step, making changes as you go along. Ask questions to determine whether a step can be modified or deleted. Make notes of any significant actions that will happen behind the scenes to ensure a process is completed (these will be part of your system requirements) and any changes to procedures that must be implemented.
When you’re done with the “to be” version of your process map, it’s likely to look radically different than the “as is” version.
Here’s what’s happening in the “to be”:
This process requires a procedure change that makes it mandatory for all Employees to use automatic deposit for their paycheck.
As you move through the definition of your “to be” processes, it’s most important to remember that change isn’t easy. Most people will resist even if they hate the way things are done now. Make sure you have an active change management process in place to help smooth the transition.
Enhance your business process improvement initiatives with Quick Base business process management software.