I am on my way to a client location
for an Enterprise Resources Planning (ERP) go live this week which I at times refer to as a “corporate heart
transplant”. If you are familiar with an ERP implementation project, then I am sure you will see an analogy to heart transplant
surgery: for this enterprise, the client’s heart (all of their enterprise
data) is disconnected and the company’s operations are halted this weekend as
the conversion is underway. So in a way, their “heart” is in our hands this
weekend as we are converting data and preparing the systems for the “go live”
Monday morning.
I use the heart surgeon analogy
(with all due respect for doctors and nurses), because many times I sense my
client’s concern and angst as they go into the final phase of the project and
realize that the fate of the business can ride on the next few days. Like the
patient who knows their beating heart must be stopped, replaced and re-started,
this requires complete confidence in those around you in the operating room.
While I have been in a hospital operating room six times undergoing procedures
in my life, none have been as life threatening as a heart replacement. At each
time I was confident in my surgical team, so I can only begin to appreciate
someone going into that operation: they must have full confidence in their
surgeon and her/his team!
While going through an ERP go live
may not be life threatening to the people in an organization, it certainly can
threaten your career. I know people whose careers were impacted due to ERP
project failures, and picking up those pieces is not much fun! Like the
patient, you must have full confidence in the consulting team, the ERP
application, and your internal project team members. Everyone must be committed
to success. But how do you really know it will all turn out well? We have
checklists and plans and tests and demos galore, but at the end of the day it must
work and your employees must be able to run the organization with the new
business processes.
Consultants differ in approach to
the ideal ERP project implementation. Some may say scope and detailed
requirements must be locked down at the beginning of a project and relentlessly
managed to be successful. I am not so sure it is realistic to stop all business
change for a year or more while a new system is planned, designed, built,
tested and employees trained. Organizations must continue to adapt to change
and business processes being designed with the new system may identify
opportunities for competitive advantage. So there is no simple solution in my
view, except the project must retain a balance between risk, scope, benefits,
time, and resources. Your consulting and internal team are critical to making
this journey achieve success and I am convinced that building the business
process delivery excellence into the system design and organization throughout
a project are the way teams insure a successful go live.
As I contemplate this latest
journey, one of my next tasks is to put my keyboard back to work and write some
of my thoughts on the topic. What do you think? What successes and challenges
have you experienced on these lengthy (typically a year or more) journeys to
new business processes and systems with ERP?
In the meantime, I look forward to
the next couple of weeks as we help our client transition to their exciting new
world of business processes and information technology using Microsoft Dynamics
AX 2012.
During my 30
year consulting career there have been many and each was unique and special in
the bonds built with my client and the rest of our consulting team. I both look
forward to the go live and feelings of loss as the relationships invariably
begin to fade and I move on to the next project. But at the end of each there
is definitely a “sigh” of relief, pride of accomplishment for what has been
done, and time to rest.
I am on my way to a client location for an ERP go live. During
my 30 year consulting career there have been many and each was unique and
special in the bonds built with my client and the rest of our consulting team.
I both look forward to the go live and feelings of loss as the relationships invariably
begin to fade and I move on to the next project. But at the end of each there
is definitely a “sigh” of relief, pride of accomplishment for what has been
done, and time to rest.
If you are familiar with an Enterprise Resources Planning
(ERP) implementation project, then I am sure you will see the heart surgeon
analogy: for this enterprise their heart (all of their enterprise data) is
currently in our hands and the company’s operations are halted this weekend
while this conversion is underway. So in a way, their “heart” is in our hands
this weekend as we are converting data and preparing the systems for the “go
live” Monday morning.
I use the heart surgeon analogy (with all due respect for
doctors and nurses), because many times I sense my client’s concern and angst
as they go into the final phase of the project and realize that the fate of the
business can ride on the next few days. Like the patient who knows their
beating heart must be stopped and replaced, this requires complete confidence
in those around you in the operating room. While I have been in a hospital
operating room six times undergoing procedures in my life, none as life
threatening as a heart replacement. At each time I was confident in my surgical
team, so I can only begin to appreciate the foreboding facing someone going
into that operation: they must have full confidence in their surgeon and
her/his team!
Going through an ERP go live may not be life threatening to the
people in an organization, it certainly can threaten your career. I know people
whose careers ended due to ERP project failures, and picking up those pieces is
not much fun! Like the patient, you must have full confidence in the consulting
team, the ERP application, and your internal project team members. Everyone
must be committed to success. But how do you really know it will all turn out
well? We have checklists and plans and tests and demos galore, but at the end
of the day it must work and your employees must be able to run the organization
with the new business processes.
Consultants say scope and detailed requirements must be locked
down at the beginning of a project and relentlessly managed to be successful. I
am not so sure it is realistic to stop all business change for a year or more
while a new system is planned, designed, built, tested and employees trained.
Organizations must continue to adapt to change and business processes being
designed with the new system may identify opportunities for competitive advantage
that cannot be ignored. So, there is no simple answer in my view, except the
project must retain a balance between risk, scope, benefits, time, and
resources. Your consulting and internal team are critical to making this
journey achieve success and I am convinced that building the business process
delivery excellence into the system design and organization capability throughout
a project are the way teams
insure the go live goes well
There may be many other theories and opinions on how to be
successful with an ERP project, so one of my next tasks is to put my keyboard back
to work and write some of my thoughts on the topic. What do you think? What
successes and challenges have you experienced on these typically year or more journeys
to new business processes and systems with ERP?
In the meantime, I look forward to the next couple of weeks
as we help our client transition to their exciting new world of business
processes and information technology using Microsoft Dynamics .

No comments:
Post a Comment