pressing the big scary red button

16

Click here to load reader

Upload: daniel-doubrovkine

Post on 24-Jan-2015

1.832 views

Category:

Technology


3 download

DESCRIPTION

How do we feel about project resets? 100% say resets are a consequence of failure. Is it always the right thing to do? Is there a different way - a culture of many small resets?

TRANSCRIPT

Page 1: Pressing the Big Scary Red Button

PRESSING

THE BIG SCARY RED

RESET BUTTON

DANIEL DOUBROVKINE (A K A DB.)

#NYCTOSCHOOL @DBLOCKDOTORG – [email protected]

CTO SCHOOL NYC / MAY 2012

Page 2: Pressing the Big Scary Red Button

HOW DO WE REALLY

FEEL ABOUT RESETS?

consequence of failure

failed to focus

failed at market fit

hacked with friends

failed to execute technology

failed to hire enough hands

failed to deliver in a timeframe

failed to fit a budget

failed to cut losses failed to convince

Page 3: Pressing the Big Scary Red Button

ADDED DRAMA

http://www.youtube.com/watch?feature=player_embedded&v=316AzLYfAzw

• slam the brakes

• change wings in-flight

• stop the hemorrhage

• jump from a sinking ship

• escape a train wreck

• stop flogging a dead horse

Page 4: Pressing the Big Scary Red Button

EXHIBIT 1: MICROSOFT

WINDOWS LONGHORN VISTA

• Development Begins in 2001

• “Longhorn” ETA 2003, btw. “Whistler” & “Blackcomb”

• Another “Cairo”?

• Reset in 2004 on top of Windows Server 2003

• Alchin in WSJ: “Longhorn was crashing into the ground.”

• In 2004 Developers no longer cared

• Ships 2006 as Vista, major fail

Page 5: Pressing the Big Scary Red Button

EXHIBIT 2: MICROSOFT

OFFICE ’98 & NETDOCS

• Windows Hawks vs. Internet Doves

• Office 98 Team Walked to be Netdocs, reset and shipped

• Netdocs 1 in Java, effectively an Office reset

• Netdocs 2 reset in C++

• Netdocs 3 reset as a Service

• Spent 500M$ over 4 years, 500 devs

• Canned in 2001

• Technology folded into Office

Page 6: Pressing the Big Scary Red Button

100% SAY THEY ARE

CONSEQUENCE OF A

FAILURE SURVEYED TWO DOZEN PROJECTS

Page 7: Pressing the Big Scary Red Button

4/10 HAVE A LARGE

SUNK COST

7/10 FACED STRONG

OPPOSITION

Page 8: Pressing the Big Scary Red Button

2/10 BLAME PURE

PRODUCT FAILURE

3/10 BLAME PURE TECH

FAILURE

2/10 BLAME PEOPLE

FAILURE

2/10 BLAME FAILURE ALL

AROUND

Page 9: Pressing the Big Scary Red Button

4/10 RESETS LEAD

TO FAILURE

100% OF PROJECTS

THAT WEREN’T

RESET FAILED

3/10 RESETS LEAD

TO SUCCESS

Page 10: Pressing the Big Scary Red Button

PRESSING RESET IS

ALWAYS THE RIGHT

THING TO DO* * PROVIDED YOU’RE 100% SURE THE PROJECT IS FAILING

Page 11: Pressing the Big Scary Red Button

PRESSING RESET IS

ALWAYS THE RIGHT

THING TO DO*

* PROVIDED YOU’RE 100% SURE THE PROJECT IS FAILING

• Find Truth-Sayers

• Measure Value vs. Cost

• Don’t be a Chicken

Page 12: Pressing the Big Scary Red Button

US AND THEM

RESETS CAN BE A SMART

CAREER MOVE

RESETS CAN BE A DUMB

CAREER MOVE

Page 13: Pressing the Big Scary Red Button

7/10 FACE STRONG

OPPOSITION

• Act Now

• Invest Into Trust Capital

• Double or Nothing

• Split Execute

• Underpromise and Overdeliver

Page 14: Pressing the Big Scary Red Button

PEOPLE TEND TO

FORGET HOW BAD IT

WAS BEFORE A RESET

• No Place for Heroes

• This is Your Job

Page 15: Pressing the Big Scary Red Button

FOSTER A CULTURE OF

FREQUENT BUT SMALLER

RESETS

• Everything is an Experiment

• Embrace Change

• Underpromise and Overdeliver

• Stop at the Top

100 % OF RESETS

ARE CONSEQUENCES OF

FAILURE

Page 16: Pressing the Big Scary Red Button

QUESTIONS?

art.sy: http://art.sy

twitter: @dblockdotorg

blog: http://code.dblock.org

email: [email protected]

slides on slideshare: http://www.slideshare.net/dblockdotorg