2
 ERP Implementati on: The Why vs The What Author: Kevin Mulcaire – Solution Architect I hope the reader will indulge me for a moment, I have experienced many system implementations and this experience has led me to the following conclusion: “Most ERP implementations are dominated in their ethos by !he "hat#$% &o, is this important' In short( yes% !he above is a provocative statement but I am using this to highlight the case where the focus of an implementation is about what is being replaced or improved with insu)cient weight being given to !he "hy# of an ERP implementation% It is my experience that if the balance between these *uestions is incorrect( it is di)cult to get anything but a substandard implementation% "hat is worse( it is often not noticed that this imbalance occurred, so in pro+ect washup meetings, the lessons learnt do not include this basic mista-e and therefore future systems replacements are doomed to ma-e the same basic error % It is a common and simple trap to fall into% !he ERP &alesmen and &aleswomen turn up and promise enhanced .ser interfaces, streamlined processes and a whole host of other bene/ts that will accrue from purchasing 0cme ERP#% 0 sale is made and an implementation team arrives% 0t this point, all memory of why you are implementing this ERP system vanish as the box of goodies is opened and the new toys are ta-en out and played with% 1ut before the sale, time should have been spent *uantifying why you are embar-ing on this pro+ect% 2ow much do you want to add to your bottom line in e )ciencies and increased revenue' 1y how much do you want to reduce customer complaints or increase business or audit controls' !he list of potential bene/ts goes on% !he point is they should be *uanti/ed% 3uring your implementation, you should reference these bene/ts constantly to ensure that what you are doing is actually delivering the desired outcome%  !he methods of ensuring you get these business bene/ts ar e complex and speci/c to the bene/ts you are trying to achieve% !he tric- is to ensure that this concept ta-es its proper place at the centre of your i mplementation%  About the Author:

ERP Implementation and the Importance of Benefits realisation.docx

Embed Size (px)

Citation preview

ERP Implementation: The Why vs The WhatAuthor: Kevin Mulcaire Solution Architect

I hope the reader will indulge me for a moment, I have experienced many system implementations and this experience has led me to the following conclusion: Most ERP implementations are dominated in their ethos by The What. So, is this important? In short; yes. The above is a provocative statement but I am using this to highlight the case where the focus of an implementation is about what is being replaced or improved with insufficient weight being given to The Why of an ERP implementation. It is my experience that if the balance between these questions is incorrect; it is difficult to get anything but a substandard implementation. What is worse; it is often not noticed that this imbalance occurred, so in project wash-up meetings, the lessons learnt do not include this basic mistake and therefore future systems replacements are doomed to make the same basic error.It is a common and simple trap to fall into. The ERP Salesmen and Saleswomen turn up and promise enhanced User interfaces, streamlined processes and a whole host of other benefits that will accrue from purchasing Acme ERP. A sale is made and an implementation team arrives. At this point, all memory of why you are implementing this ERP system vanish as the box of goodies is opened and the new toys are taken out and played with. But before the sale, time should have been spent quantifying why you are embarking on this project. How much do you want to add to your bottom line in efficiencies and increased revenue? By how much do you want to reduce customer complaints or increase business or audit controls? The list of potential benefits goes on. The point is they should be quantified.During your implementation, you should reference these benefits constantly to ensure that what you are doing is actually delivering the desired outcome.The methods of ensuring you get these business benefits are complex and specific to the benefits you are trying to achieve. The trick is to ensure that this concept takes its proper place at the centre of your implementation.About the Author: Kevin Mulcaire is a highly experienced IT and Management Consultant with a history of delivering complex projects in diverse businesses.