In upcoming years, the world's largest enterprises are upgrading their current SAP version into S/4 HANA if they haven’t yet done it. This kind of massive core system renewal requires years of planning and selection of optimal renewal strategy to succeed.


ERP renewals are crucial projects, which happen once every 5-8 years and success can give a company a competitive edge over the competition. Failing, on the other hand, can cause a significant spiral of losses as the company is unable to perform at the desired level. There have been plenty of these unfortunate failures of ERP renewal lately, even though there have been the best IT consulting houses supporting the initiatives.

Typical pitfalls of ERP renewal
  • Business leadership commitment to the implementation

  • Not gathering requirements carefully

  • Ignoring change management

  • Implementing the whole system at once

  • Focusing on too many details instead of a smaller number of more probable causes

  • Not investing enough in/supporting implementation team 

  • After-implementation review and checks

Transformation increases many diverse expectations

There are different kinds of companies with special characteristics and old historical decisions, which make each ERP renewal a special one. This also creates more uncertainty for implementation and deployment even though best practices with best advisors would be followed. 


One of the most important factors of each project is the actual employees, their expectations, wishes, doubts and fears. They have worked 5-8 years with existing systems, defined practices and learned their digital habits. And now, it will change. This will, for sure, cause all kinds of feelings when a new system implementation is starting. The majority of employees will be involved when the renewal will start, and that will be a crucial moment to have everybody on the same boat and ensure that deployment and post-care will go smoothly, and doubts and fears are addressed.

Make change-oriented data-driven decisions

Whenever new systems are widely rolled out, it creates noise in an organization mostly during the deployment phase.

How to determine which noise is accurate and in place, while which is non-urgent? 


Implementation managers need to make hundreds of small decisions on a daily basis during the implementation and deployment phase. Most likely managers need to do this without transactional and operational data about bottlenecks, accumulated manual work or manual gaps caused by new system release in operational work. It’s not that these problems are accumulating to the new system - they are everywhere else: other systems, other stakeholders’ work, other units and teams.

With existing solutions, you cannot get a clear picture of what is happening in the organization during the deployment in regards to how to work, thus cannot lead the change. For companies to successfully deploy new systems, you need to understand in real-time if there are issues, what is causing those, what is the priority level of the issues and what is the right tool to solve the issues, e.g. where does manual work pile up, where should integration or robots be implemented or do employees really use tools? 

Workfellow allows companies to follow how the company’s work is done during the deployment phase. Workfellow looks at knowledge work from people's point of view. It includes all the business systems and processes that people use across the organization - regardless of the process name and system - so you can find real bottlenecks, issues and manual gaps and prioritize those with data-driven decision making. This way, you can ensure on-time delivery and change management. 

Read more about Workfellow for Process Mining and Excellence Initiatives here.

Understand your way of working on the go

Most important thing is that when you deploy a new system, you get people onboarded and using the system, adopting the new way of working and methods from day one. This seldom happens.

A common problem with addressing issues and solving those is that companies do not have visibility on who is adopting new ways of working e.g., who is using old file staches, who is struggling with new systems, who do not follow instructions, how do workflow and timing change, how does it affect related teams or does the new system generate new kinds of unexpected work. 


Workfellow creates the needed data on the go without integrations. This enables you to get results while deploying new systems so you can lead to change. 

In short: Workfellow gives you a comprehensive view of knowledge work during your system deployment so you can lead the change with data on the go.

Clips by Icons8

Follow us for the latest insights:

©2020 by