ERP implementations can be quite disruptive to business and can cause a change management battle for months afterwards.
The usual approach for processes is to capture current state processes as part of the requirements phase, to build an understanding of the ‘gap’ to your future state. This is normally captured on a combo of Visio charts and Word documents, all signed off as part of the project. This approach works fine for projects, but hasn’t really got a good track record of helping the business afterwards. If you’ve been involved with these sort of projects before, you’ll know the process stuff is largely ignored after the project. It’s pretty technical and project focussed – not easy or useful to refer to later. There’s usually a lot of good training and user guide material floating around after the implementation, again varying usefulness after the project. Overall – a lot of hugely valuable information (developed at great expense) is essentially discarded after the project.
We coach our clients on taking an ERP implementation (be it SAP, MS Dynamics, Oracle etc) as an opportunity to build a useful base of process knowledge. You’re forced to develop this detailed understanding of your processes as part of the project, so why not do it properly? A simple, central process repository with links to system guides is great for bedding in new processes, fixing teething issues in a systematic way (there’s a lot of that) and an information base that gives a real opportunity to change your process culture.
- For example, the new Account Payable processes are now on Promapp. Guidance is clear, easy to follow, and you can click through to the nice user ERP guides.
- You can find the process quickly because it’s also embedded in the ERP menu, directly below the appropriate screen.
- It’s also on the Accounts team SharePoint portal (if you use it)
- It’s also on Promapp, the place people go for processes…
So in short:
- When is Promapp used as part of an ERP implementation?
We recommend capturing future state processes on Promapp, after using Visio or Word to capture a light version of current state processes as part of requirements phase.
Please note that the other alternative sometimes considered is to move your new processes (once they’ve stabilised) onto Promapp. But in our experience, once you’re through an ERP implementation, not many teams have the stomach to look at the same processes again for a looong time…
- How does Promapp support the implementation – before / during / after?
Before and during - similar to old approach, helps build a picture of requirements.
After - it’s actually useful information. A knowledge base that teams actually refer to, own, improve…