driving technical change

74
DRIVING TECHNICAL CHANGE Terrence Ryan

Upload: terry-ryan

Post on 20-May-2015

820 views

Category:

Documents


15 download

TRANSCRIPT

Page 1: Driving Technical Change

DRIVING TECHNICAL CHANGE

Terrence Ryan

Page 2: Driving Technical Change

DOES THIS SOUND FAMILIAR?

Page 3: Driving Technical Change
Page 4: Driving Technical Change
Page 5: Driving Technical Change
Page 6: Driving Technical Change
Page 7: Driving Technical Change
Page 8: Driving Technical Change
Page 9: Driving Technical Change
Page 10: Driving Technical Change
Page 11: Driving Technical Change
Page 12: Driving Technical Change
Page 13: Driving Technical Change
Page 14: Driving Technical Change

THE PROCESS

•  Identify the Skeptics •  Match to countering tactics •  Tactics implement Strategy

Page 15: Driving Technical Change
Page 16: Driving Technical Change
Page 17: Driving Technical Change

SKEPTICS

The People in your Neighborhood

Page 18: Driving Technical Change

THESE ARE CARICATURES.

Page 19: Driving Technical Change

PEOPLE ARE MUCH MORE COMPLEX

Page 20: Driving Technical Change

THIS IS A WAY OF UNDERSTANDING THEM

Page 21: Driving Technical Change
Page 22: Driving Technical Change

UNINFORMED

•  Symptoms –  Don’t know

•  Cause –  Never came across it

•  Prognosis –  Easy to change –  Initial change likely to be

other persona

Page 23: Driving Technical Change
Page 24: Driving Technical Change

HERD

•  Symptoms –  “No one told us to use the

technique.” –  “Are we allowed to do

that?” •  Cause

–  Look to a strong leader to tell them what to do

•  Prognosis –  Easiest to change –  You have to be willing to

lead

Page 25: Driving Technical Change
Page 26: Driving Technical Change

THE CYNIC

•  Symptoms –  Have not tried technique –  Question effectiveness –  Question degree of

effectiveness

•  Cause –  Doubt without proof –  Trying to score points

•  Prognosis –  "ey can be converted with

miles and miles of proof

Page 27: Driving Technical Change
Page 28: Driving Technical Change

THE BURNED

•  Symptoms –  Had past failures with

technique. •  Cause

–  Umm… Past failures •  Prognosis

–  Hard to change –  Can be done if you prove

previous implementation was •  misapplied •  #awed •  de$cient

Page 29: Driving Technical Change
Page 30: Driving Technical Change

THE TIME CRUNCHED

•  Symptoms –  “I don’t have time for it”

•  Cause –  Do not believe they can

afford the time to learn and implement

•  Prognosis –  "ey can be converted if

you prove that technique will save them time

Page 31: Driving Technical Change
Page 32: Driving Technical Change

THE BOSS

•  Symptoms –  Don’t care about this

level of detail

•  Cause –  Not really their bailiwick

•  Prognosis –  Hit or miss –  Make your solution a $x

to their problems

Page 33: Driving Technical Change
Page 34: Driving Technical Change

THE IRRATIONAL

•  Symptoms –  Resist any a%empts to

introduce method –  Hides as another type –  Brings up objections that

don’t conform with previous behavior

•  Cause –  Doesn’t ma%er

•  Prognosis –  Can’t change, don’t worry

Page 35: Driving Technical Change

TACTICS

What to Focus on

Page 36: Driving Technical Change
Page 37: Driving Technical Change

EXPERTISE

•  Use these techniques for yourself •  Don’t wait for your organization •  Gain an expertise not just a familiarity

Page 38: Driving Technical Change

EXPERTISE - PERSONAS

•  Effective on: – Uninformed – Herd – Cynic – Burned

Page 39: Driving Technical Change
Page 40: Driving Technical Change

DELIVERY

•  Be passionate •  Don’t be zealous •  “Have you tried…” vs “You should…”

Page 41: Driving Technical Change

DELIVERY- PERSONAS

•  Effective on: – Uninformed – Cynic – Burned –  Irrational – Boss

Page 42: Driving Technical Change
Page 43: Driving Technical Change

DEMONSTRATE

•  Show, don’t tell •  Write an application in a weekend •  Solve a group problem

Page 44: Driving Technical Change

DEMONSTRATE- PERSONAS

•  Effective on: – Uninformed – Herd – Time Crunched – Cynic – Burned – Boss

Page 45: Driving Technical Change
Page 46: Driving Technical Change

COMPROMISE

•  Be passionate •  Don’t be zealous •  “Have you tried…” vs “You should…”

Page 47: Driving Technical Change

COMPROMISE- PERSONAS

•  Effective on: – Uninformed – Cynic – Burned –  Irrational – Boss

Page 48: Driving Technical Change
Page 49: Driving Technical Change

SYNERGY

•  Connect implementing your technique with a larger concern – Security – Regulations Compliance

Page 50: Driving Technical Change

SYNERGY- PERSONAS

•  Effective on: – Boss

Page 51: Driving Technical Change
Page 52: Driving Technical Change

PRESSURE

•  Network Externalities – Electronic peer pressure – Create a solution that people really need that relies

on your technique

Page 53: Driving Technical Change

PRESSURE- PERSONAS

•  Effective on: – Uninformed – Herd – Time Crunched – Cynic – Burned

Page 54: Driving Technical Change
Page 55: Driving Technical Change

BRIDGING

•  Create something enticing that is halfway between where you are and where you want to be – Bridging Framework

Page 56: Driving Technical Change

BRIDGING- PERSONAS

•  Effective on: – Time-Crunched – Herd

Page 57: Driving Technical Change
Page 58: Driving Technical Change

PUBLICITY

•  Get your code reviewed •  Open Source your solution •  Apply for awards

Page 59: Driving Technical Change

PUBLICITY- PERSONAS

•  Effective on: – Uninformed – Cynic – Burned – Boss

Page 60: Driving Technical Change
Page 61: Driving Technical Change

TRUST

•  Be honest •  Don’t lie by: – omission – spin

•  Avoid FUD

Page 62: Driving Technical Change

TRUST- PERSONAS

•  Effective on: – Healthy Cynic – Burned –  Irrational

Page 63: Driving Technical Change

STRATEGY

What to do big picture wise.

Page 64: Driving Technical Change

IGNORE THE HOSTILE

Page 65: Driving Technical Change
Page 66: Driving Technical Change

HARNESS THE CONVERTED

Page 67: Driving Technical Change

CONVINCE MANAGEMENT

Page 68: Driving Technical Change

CONCLUSIONS

Now what?

Page 69: Driving Technical Change
Page 70: Driving Technical Change
Page 71: Driving Technical Change
Page 72: Driving Technical Change
Page 73: Driving Technical Change
Page 74: Driving Technical Change

QUESTIONS?

h%p://terrenceryan.com [email protected] @tpryan on Twi%er