Process design
from as-is to to-be with analyses, tools and methodologies
Thinking up a new way of working? You don't just arrive at that; you need a strategy. But also the necessary knowledge and insights, and the ability to adjust. A new process and an efficient way of working stands or falls with the accurate mapping of a process landscape. What options you have within designing to-be processes? We have summarized them for you.
Where are you moving towards?
An organizational change, a merger of two companies or implementing new software tools. There comes a time when your organization goes through a change, where business processes need to be revised. And before that, you need to be clear about where you want to go. What does your desired outcome look like? Who is involved? What documents need to be delivered? And what approval do you need? The to-be process in the process design phase paints a clear picture.
How do you design the to-be situation?
Your as-is processes are the starting point. From there, you start working to determine where you want to go. To future proof your organization and processes, it's important to bring the right people together. Workshops offer insight into bottlenecks and opportunities for improvement. And methodologies such as value-stream mapping or a SIPOC model, help you maintain focus and collect the correct information. But SAP's best practices, too, can help.
Ensure a smooth transition
Now that you have the basics, the key is to compare the current situation (as-is situation) with the to-be process. After all, how do you ensure that the transition is efficient? And that all stakeholders are involved and trained? You do this by involving change management in the preliminary process. In addition, you compare the as-is and to-be situation, objectively, to determine the magnitude of change compared to the current situation. This can be done manually, but Signavio also has a standard comparison model for this.
No surprises with SAP best practices
Your new process is in place. But that's mostly on paper. SAP's best practices help you go a step further. Use them to make a comparison between SAP and the as-is situation. Or just to support during implementation. Please note that the best practices show only the steps, which are performed within the application. Everything outside of that is not included. So adopting the SAP best practices directly is usually not enough.
