Not every SAP project leads to success, so maybe you would like to learn from others how to avoid common pitfalls?There are many pitfalls project teams commonly run into. We’ve decided to pull together those common pitfalls and best practices, based on Software AG’s long-time experience in SAP projects.
- Envision your digital future. The so-called blueprint phase sets the groundwork for the success of your SAP solution. No matter what your goals are, whether you intend to manage your transformation to an SAP-based digital business or just to integrate your processes with SAP, you’ll need to design your SAP processes.
- Document your strategy and gain C-level sponsorship
- Define and match business requirements with SAP offerings
- Include business AND IT from the beginning
- Starting from scratch with implementation
- Thinking that digital business design is a one-time exercise
- Forgetting to link the strategy to your business processes
- Ignoring running SAP solutions
Once the original set up is done, do not forget that in today’s digital world, your business needs to adapt constantly - leveraging the information modeled in ARIS will save you valuable time throughout the different phases of your SAP project and help you realize the full benefit of your SAP solutions.
- Test for success. Testing is an extremely important milestone for a best-in-class SAP solution and a smooth and successful go-live.
- Define strategic end-to-end processes early
- Include business in the test definition
- Select a standard testing tool
- Focusing on functional testing only
- Underestimating the time needed for testing
- Ignoring business feedback
- Empower your business. Even if training and communication are considered as different project phases, they go hand-in-hand based on the same tools. Spreading the word and delivering the right training for your new SAP solution is another big task for the project team. A process-driven approach helps to assure the whole company understands the new SAP-based processes.
- Create process documentation as the single point of truth
- Set up governance processes to manage process design
- Clearly define responsibilities for the interface
- Set on ARIS for process-driven training with reuse of process information
- Forgetting about the documentation after the project start
- Focusing only on the technical integration
- Using only SAP standard reference processes
- Solely training on SAP features and functions
- Ignoring user feedback and comments
- Secure your digital future. Once your system is up and running, your project will profit from the numerous analytical capabilities in ARIS by reusing all pieces of information available in the repository. Analyze every piece of information, from organizational reports and process efficiency analysis to what-if analyses, number of cost counting.
- Extract and analyze SAP system information
- Use analytics to create value and to compare plan vs. as-is.
- Consider and mix different KPIs and dimensions to plan your scenarios
- Ensure the quality of your source data
- Forget to focus on solving the current issue
- Believing analytics is just for management.
- Assume KPIs don’t create any value.
- Believing your existing analytics tools are sufficient, ARIS is more than measuring or designing a process. It is the combination of both!
Take the next step
Read more on how ARIS helps you manage your business and achieve a best-in-class SAP solution to help secure your success in the digital world. And stay tuned; in our next post, we’ll give you hints for achieving a successful S/4 HANA project.