Friday 18 December 2009

Getting the focus right when implementing a new system

When a new system is being implemented there are three elements that must be balanced:
  1. Functionality - what it needs to do;
  2. Speed – how quickly do you want it in place;
  3. Price – what is the budget.

It's easy to say that we want everything, now, and at a rock bottom price but that's not the real world. It's also a recipe for a failed implementation.

In most cases, the answer is a blend of the three but the mix will determine how your project proceeds. For example, a project focused on price will almost certainly result in less functionality being delivered, whereas a focus on functionality will take longer to deliver and probably cost more. No implementation is the same so consider the triangle (right) and think about where your priorities are.

We find that there are 4 broad categories of implementation:

Balanced - requiring “a little of all of them”, is where most of our clients actually sit. They want a balance between a solution that is implemented quickly, but is somewhat tailored to their needs, with enough training to get both users and administrators up and running with a minimum of stress, effort, and delay.

Speed - A focus on speed means getting the system as fast as you can. This does not necessarily mean sacrificing functionality or quality, but can result in a higher cost. It may involve several consultants working together on a system. Speed focused implementations need careful project management.

Functionality - The functionality focus typically suits organisations that want the system configured to their specific needs, detailed user and administration training, and have lots of data to be migrated from one or more legacy systems.

Price - A focus on price looks for all options to keeping the cost down. This includes absolute out-of the-box functionality, and training to give administrators enough information to continue the learning process themselves in the use, setup and administration of the system, and to train the end users themselves.

The best route to understanding the right mix for your implementation is to meet with the vendor and discuss the options, your in-house skills and how critical the system will be. It's also worth pointing out that the mix will change from system to system and should not be a company standard

No comments: