Implementation

Philosophies

The implementation of any system is difficult. We have developed the following set of implementation philosophies that guide all of the work that we do.

Manage the Change

• Change is hard. Recognize, over-communicate, and continually address change issues.
• Get the right people backing the effort, publicly and at the right level.
• Minimize the impact to end users.

Shop Reality NOT Theory

• Avoid analysis paralysis during the planning portion. Involve day to day users to get the 'reality' perspective.
• Leave the theory to the PMO. PMs/RMs/Users aren't excited by theory.
• Prototype solutions. Wow users with what is already built.

Training AND Mentoring

• Training is the imparting of information with others. This is needed, but not sufficient.
• Mentoring involves personal commitment to the other person's long-term success.
• Dedicate one-on-one time before, during, and after a deployment.

Let the Users Drive

• Create value for the managers and end users, not just upper management.
• The change will not last without the day-to-day users recognizing its value.
• Adapt views for local needs and learn to know where to be flexible.

Think Big, Implement Small

• Perfectionism is overrated. The process or setup may not be ideal at first, but remember 80% automation will save a great deal of time.
• Rapid Incrementalism - Introduce only small bits of functionality, and do it quickly.
• Continue to reinforce the initial focus of the rollout.

Be Prepared

• Find and address the root causes instead of just the most pressing problems.
• Time is money. Dedicate the necessary time upfront defining processes and reports.
• Become fully immersed in the application. This will save support time and cost.