The key to a great change release is to produce a model that supports visual "simulation" prior to production with sufficent detail to allow the stakeholders to see where they fit in the model, and prepares them for taking ownership before the application goes into production. Failure to paint this picture will require less productive resource.

Talented program managers spend hours creating change communications, process implication, and discussing key issues, inhibitors and success criteria all in the intent of getting their service to market or "done'. Yet too many set the "done" point too narrowly at "produced", and it seems the art for transition is providing sufficient summarization and detail to help stakeholders actually picture what they will do differently as the result of the change.

Varying levels of Approaches exist to managing the implications of change. One size does not fit all for productionalizing change, but awareness of the options might help you to pick the approach best suited for your stakeholder audience.

TERMINOLOGY:

(1) Model Approach defines a representative pattern for how the service to be produced will be managed. Model Approach: Defines the high level process flow for how the product will be produced, including high level elements of what is being produced or managed. The intent is to help stakeholders understand their roles and responsibilities need to align to the planned production standard.

(2) Simulation Approach extends a model approach with the intent of helping stakeholders to visualize how they prepare for and participate in the proposed change. Simulation Approach: Extends the model to present an example of the way the products elements will behave while the product is being produced, released, or managed. The intent is to help stakeholders understand the production capability, service ability and supportability elements they need to understand to support the go live production standard.

(3) Mentoring Approach extends a model approach by producing a coaching through simulation that has used this model and simulation to help produce other outcomes. Mentoring Approach takes a Subject Matter expertise to apply the model and then teach others how to do the same. They might employ a simulation or manifest alignment to help them to teach others more than how to catch. The objective of any approach is to clearly articulate what is being produced, what is required, and what must be managed to deliver availability, serviceability, and supportability.

PRACTICAL APPLICATION: Whether the "CHANGE" is an Oracle Implementation or Potty Training with a strong willed 2 year old, the APPROACH is important. Model Approach is useful when communicating the high level objectives, but more information is needed to help those supporting the implementation to understand what changes to reach the desired endstate. In the Oracle model this might include packaging what known services will change, and what new services will be introduced-- a "manifest" of the change implications so to speak. in the Potty Training model this might include the high level milestone, the benefits, and the desired celebrateable complete state.