Failure is not an option. It's a fact
summary
Conference survey of studies and practical advice shows software projects behave with a fat tail: analysis of ~4,000 IT projects finds 70% schedule overrun and one-in-six budget blowups, DoD data shows only 35% finish within budget. Classification of failures into preventable, complex and intelligent guides responses; use testing tools like Testcontainers, build small safe experiments to fail fast, and create psychological safety so teams report errors and turn failures into learning.
AI-written summary · about
chapters (14)
- 0:00Introduction and speaker intro
- 1:31Emotional weight of failure
- 5:56Cultural perspectives on failure
- 7:45Failure in IT projects
- 12:27Types of failure in development
- 14:16Defining failure historically
- 16:25Preventable vs intelligent failures
- 19:19Success and failure cycle
- 23:17Learning from failure challenges
- 27:32Psychological and technical barriers
- 31:32Organizational learning strategies
- 32:56Psychological safety in teams
- 36:55Personal definitions of success
- 37:59Audience reflections on failure
related talks
07mFailure Is Not an Option It's a Fact
44mFAIL is Not a Four-Letter Word
14mHow to Succeed with Your Software Project
22mChoosing Failure
26mFail Fast Vs Fail Smart - Lessons Learnt
01h 28mDon't Fail Fast -Learn Fast: Innovating Fast is a Must
49mHow to tell people they failed and make them feel great!
06mDon't Fail Fast. Learn Faster