Isaac Newton’s (1642-1727) perspective on software deployment

n  2^nd Law:
The acceleration of an object varies directly as the external unbalanced force applied to it and inversely as its mass.

n  Translation:  Implementation Speed
How fast users adopt new software and incorporate change will vary directly with

                  (a) how much force is applied and

                  (b) how much resistance to change exists/remains.

Isaac Newton’s (1642-1727) perspective on software deployment

n  3^rd Law:
For every action force there is an opposite and equal reaction force in the opposite direction on the object exerting the action force

n  Translation:  Push Back
For every new software deployment effort, there will be an opposite and equal force applied to the change effort… the question is only who will persevere

Isaac Newton “take-aways”

1. Software adoption is driven by an outside force upsetting familiar habits, not intrinsic evolvement
2. The speed of software adoption is dependent upon level of force behind the change effort (including insistence from above) and the effectiveness of resistance removal
3. Resistance is part of the experience, not an alarm signal

Thomas Kuhn (1962)
“Structure of Scientific Revolution”

n  Paradigms Rule:
One’s paradigm predetermines the conclusions about reality, and new facts that don’t fit an existing paradigm are ignored

n  Translation:  Rejection Response
Introducing new software into a person’s work system that is already defined by a paradigm of customary processes, steps and preferred tools – will evoke a rejection response

n  “Most people when confronted with either changing their mind or proving why they don’t have to… get busy on the proof.”
                                                                                                John Galbraith

Thomas Kuhn (1962)
“Structure of Scientific Revolution”

n  Crises & Paradigm Shifts
Paradigm shifts seldom occur as soon as a new paradigm is invented, but rather only when the old one is shown to be inadequate

n  Translation:  “Shake it Up”
Introducing new software changes paradigms, the success of which is dependent upon proving the “old” is inadequate

The Software Deployment Wall

Proof of Inadequacy

Active Push Back & Resistance

The Inertia Power of Habit and Paradigm

Managing Resistance

n  Value/Assumption shift

Planning/Information    Growth & Learning

   
Rules/Best Practices      People

n  Interpersonal Process (past & present)

n  Confusion, Logical Dis-connect

n  Apprehension, Loss & Fear

n  Change =
Solution + Vision

Deployment Paradigms Needing an Update

n  Purchasing drives usage

n  Training drives usage

n  Efficiency drives usage

n  Past success drives usage

A new paradigm for software deployment

n  Treat it as project management effort escorting people up the 4 step ladder of software adoption

n  Treating it as a change management effort.

n  Treat it as a leadership effort, using PST’s Push-Pull model

Software Deployment as PM
with the PST 4 step Usage Ladder

n  Use pm steps of defining scope, deliverables, installation, training, configuration, start date, milestone due dates, etc.

n  Step 1 – Usage match up at the personal level

n  Step 2 – Usage as described and defined by job function and compensation structure

n  Step 3 – Usage as defined by projects being tracked

n  Step 4 – Usage as defined by strategic management and business navigation