Celebrating failure or success? Why not both?
summary
Examines how software teams can learn from failures without increasing risk by combining preventive actions with deliberate analysis of errors. Reviews studies and company best practices for balancing innovation-driven experimentation and disciplined execution, focusing on using failure-derived knowledge to improve preventive measures in engineering and software development.
AI-written summary · about
related talks
44mThe role of catastrophic failure in software design
45mThe human nature of failure & resiliency
41m‘Failure’ as Success: The Mindset, the Methods, and the Landmines
20mBeauty of Failure
34mWhy Good Software Goes Bad
01h 06mCongratulations, you Failed!
23mElephant in the room and Innovation!
07mFailure Is Not an Option It's a Fact