Pressing the Big Scary Red Button
•
2 likes•1,276 views
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?
More Related Content
What's hot
What's hot (10)
Viewers also liked
Viewers also liked (11)
Similar to Pressing the Big Scary Red Button
Similar to Pressing the Big Scary Red Button (20)
More from Daniel Doubrovkine
More from Daniel Doubrovkine (20)
Recently uploaded
Recently uploaded (20)
Pressing the Big Scary Red Button
- 1. CTO SCHOOL NYC / MAY 2012 PRESSING THE BIG SCARY RED RESET BUTTON DANIEL DOUBROVKINE ( A K A DB .) #NYC TOSC HOOL @ D B LOC KD OTORG – D B LOC K@D B LOC K.ORG
- 2. HOW DO WE REALLY FEEL ABOUT RESETS? failed at market fit failed to focus failed to execute technology failed to fit a budget consequence of failure failed to deliver in a timeframe hacked with friends failed to hire enough hands failed to convince failed to cut losses
- 3. 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
- 4. 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
- 5. 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
- 6. 100% SAY THEY ARE CONSEQUENCE OF A FAILURE SURVEYED TWO DOZEN PROJECTS
- 7. 4/10 HAVE A LARGE SUNK COST 7/10 FACED STRONG OPPOSITION
- 8. 2/10 BLAME PURE PRODUCT FAILURE 3/10 BLAME PURE TECH FAILURE 2/10 BLAME PEOPLE FAILURE 2/10 BLAME FAILURE ALL AROUND
- 9. 3/10 RESETS LEAD TO SUCCESS 4/10 RESETS LEAD TO FAILURE 100% OF PROJECTS THAT WEREN’T RESET FAILED
- 10. PRESSING RESET IS ALWAYS THE RIGHT THING TO DO* * PROVIDED YOU’RE 100% SURE THE PROJECT IS FAILING
- 11. 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
- 12. US AND THEM RESETS CAN BE A SMART CAREER MOVE RESETS CAN BE A DUMB CAREER MOVE
- 13. • Act Now • Invest Into Trust Capital • Double or Nothing • Split Execute • Underpromise and Overdeliver 7/10 FACE STRONG OPPOSITION
- 14. PEOPLE TEND TO FORGET HOW BAD IT WAS BEFORE A RESET • No Place for Heroes • This is Your Job
- 15. 100 % OF RESETS ARE CONSEQUENCES OF FAILURE FOSTER A CULTURE OF FREQUENT BUT SMALLER RESETS • Everything is an Experiment • Embrace Change • Underpromise and Overdeliver • Stop at the Top
- 16. QUESTIONS? art.sy: http://art.sy twitter: @dblockdotorg blog: http://code.dblock.org email: dblock@dblock.org slides on slideshare: http://www.slideshare.net/dblockdotorg