Database Reference
In-Depth Information
11.7.16.1 A Special Note about Lack of Business/User Participation and Buy-in
Lack of
business user participation and buy-in leads to low user adoption. This is a fate that has
been suffered by many an organization and can turn the Essbase system you slaved over
into shelf-ware. Why does this seem to happen frequently? We mentioned earlier in the
chapter the need to have end users involved throughout the project. It is critical to hav-
ing a strong user adoption. Also, management needs to stress the importance of the new
system. management needs to be clear that the new system is not optional and needs to
be utilized. A strong message from the right executive can make a world of difference.
And, finally, turn the old system off. Shut it down. Burn it down. Do whatever is neces-
sary to keep users from logging into the old system. users tend to be technologically lazy
and if given a choice would prefer to perform 50 steps over and over versus using 1% of
their brain power to learn the 10 steps in the new system.
11.8 post go-live tasks anD ConsiDerations
11.8.1 Lessons Learned
Lessons learned are an effective way of getting quality feedback to improve your per-
formance on future phases and future projects. A good practice is to have the Pm par-
ticipate as a member of the project team when conducting lessons learned sessions. Ask
someone who did not manage the project to facilitate and run the session so that the
team members feel open about providing honest feedback about the project's successes
and challenges. There may be some temptation to politically spin the results. Be the first
to lay bare your soul. Confession is good and this will engender an atmosphere of frank-
ness and honesty.
The following questions should be asked in each of the following areas: project man-
agement, risk management, scope control, issue resolution, communication, and team
dynamics:
• What worked well and why?
• What did not work well and why?
• What could be done better next time?
• What did we miss doing that we should have done?
From the lessons learned, you should be able to walk away with:
• What went well that should be replicated?
• What should be added?
• What should be avoided?
• What should be improved?
This is also a good time to note functionality or data that did not make it into the
project. Should there be a Phase II?
11.8.2 End User Training
It is easy to overlook on-going training. toward the end of a project, mass training
is rolled out to prepare users for the new system before go-live. But what happens
after go-live? Three months later? or even a year later? users will leave, new employ-
ees will be hired, and colleagues will change roles. If there is not a training plan for
post go-live, you will either spend a lot of time doing one-on-one training sessions or
