We know that an SAP S/4HANA project requires forethought as well as flexibility and patience. We also know that bumps in the road are inevitable, and the best way to handle them is to be prepared.

In this three-part series, we discuss common factors that lead to failed projects. We break down the steps an organization can take to avoid failures as well as how to plan for better decision-making. ASUG News sat down with John Belden, project execution audit practical lead at UpperEdge, an organization that helps customers negotiate their deals with SAP and systems integrators (SIs).

John has more than 30 years of experience implementing SAP systems. In the first part of this series, he identified common traits that can lead to a failed project and the early first steps organizations can take to avoid them. In the second part, he discusses the critical first steps an organization should take for the implementation phase. He also covers who should be at the table and how to plan for high-level decision-making and set budget expectations. In this final article in the series, we discuss how to partner with the right SI, what role the consultant should play, and considerations for change management.

Sharon: What should customers consider when partnering with a systems integrator?