How many times have you seen SAP projects generating disappointing feedback in the user community after months of those successes "Go Lives"?
Once the first invoice is issued and the first picture is shared and thousands of emails are sent full of congrats for everyone, the real business problems appear.
Don't we have to change how we consider success in our implementations?
Where key concepts as sustainability, Business benefits, Savings, etc… are?
Should we only consider a success if an invoice can be printed or if the first production order can be confirmed or if the first purchase order is received?
Implementing an SAP (ERP system) does not mean that process are being redefined or even yet improved. The redefinition of the business processes should be one more item of our implementations project. This is the key step that will ensure the company is using SAP in all its potential following the best practices. By redefining processes we will be ensuring real benefits, sustainability and savings that will let the companies see in SAP a good way to make process improvements getting operational excellence.
Does it mean that there is an opportunity to enhance the ASAP Methodology in order to add this business re-engineering as a pre-preparation?
- SAP Managed Tags:
2 Comments
