This talk is an updated version of my earlier talk "Failing Up" that I presented at Tom Tom and at App Builders Switzerland, 2016. It's a talk about how to create a failsafe environment for software companies and teams. It's critical to acknowledge that failure is necessary for innovation. So, if failure is a given, how do you fail well?
This version of the talk was first presented at Seattle Code Camp 2016
7. @kevingoldsmith #failsafe
–Mikael Krantz
"we want to be an internal combustion engine, not a
fuel-air bomb. Many small controlled explosions
propelling us in a generally ok direction, not a huge blast
leveling half the city”
Minimize the blast radius
12. @kevingoldsmith #failsafe
Each failure tells you something about
• your process
• your team
• your perception of your customers
• your understanding of your product
• yourself
Extract the lessons from failure
13. @kevingoldsmith #failsafe
Do project retrospectives with the intent to not only figure
out what happened on the project, but with the intent to
make future projects better.
Extract the lessons from failure
21. @kevingoldsmith #failsafe
– Bob Sutton
“The most creative people — and companies — don’t
have lower failure rates, they fail faster and cheaper, and
perhaps learn more from their setbacks, than their
competitors.”
@kevingoldsmith #failsafe
26. @kevingoldsmith #failsafe
Minimize the cost of failureInvestment
Time
Think it Build it Ship it Tweak it
Paper Prototypes
UI Mockups
User Testing
MVP
Employee
Testing
Gradual
Rollout
A/B Testing
User Testing
Analytics
Validation
A/B Testing
User Testing
Analytics
ValidationBeta
Testing
31. @kevingoldsmith #failsafe
Roll new things out over time, watch how your users react,
watch how your systems scale, watch your customer service
queues, watch your analytics, watch your crash logs.
Take your time
35. @kevingoldsmith #failsafe
Talk about when things don’t go well with an eye to future
improvement rather than blame
Creating a supportive culture
36. @kevingoldsmith #failsafe
Talk about when things don’t go well with an eye to future
improvement rather than blame
Creating a supportive culture
37. @kevingoldsmith #failsafe
Talk about when things don’t go well with an eye to future
improvement rather than blame
Creating a supportive culture
38. @kevingoldsmith #failsafe
Do retrospectives
In your retrospectives, think beyond the current project to
future projects.
The goal: continuous improvement.
Creating a supportive culture
39. @kevingoldsmith #failsafe
Monoliths are natural when a small team (or a startup) are
building a product.
Building lots of small services means building infrastructure
to support them.
The trick is knowing when it is time to make the transition.
Fail-safe infrastructure