Failure Friday #1 with Dan Ward
Summary
Key Insights
-
•
Failure is best defined as effort not producing the desired outcome, separating actions from identity.
-
•
Studying failure explicitly, as aviation pioneers did, accelerates innovation by identifying dead ends and promising directions.
-
•
Octave Chanute’s 1894 book documented 400 years of flying machine failures to guide future attempts.
-
•
National pride and geopolitics historically hindered data sharing and collective learning among aviation pioneers.
-
•
The Wright siblings included their sister Catherine as a key collaborator often overlooked in history.
-
•
Failure cake, a practice of gathering with cake after a failure, creates psychological safety and destigmatizes failure.
-
•
Celebrating the attempt, not failure itself, incentivizes boldness and risk-taking within teams.
-
•
Experiments should be framed as learning opportunities; even negative results provide valuable data.
-
•
Language choice around failure matters and should fit the cultural and contextual environment.
-
•
Clear definitions of success and intended impact are essential to meaningfully assess outcomes and failure.
Notable Quotes
"Failure is when effort did not produce the desired result, not putting in the effort in the first place."
"Failure is an outcome, not an identity. I may have failed, but I am not a failure."
"They studied their failures, faced them directly, and used those learnings to shape the next experiment."
"We can stop gluing feathers to wings and flapping wings; static wings are the way to fly."
"Fear, lack of data, and geopolitics kept engineers from sharing valuable failure information."
"We eat failure cake together, discuss what we learned, and plan what to do differently next time."
"We’re not celebrating failure. Failure sucks. We’re celebrating the attempt and boldness."
"The worst thing that could happen is we get cake. That changes how boldly a team tries."
"We do experiments not to make things work but to learn something new."
"Innovation is novelty with impact—something new that makes a meaningful difference."
Or choose a question:
More Videos
"The job market is flooded with overqualified candidates competing for fewer roles, often below their experience level."
Corey LongHiring in DesignOps: A Critical Study on How to Hire and Get Hired
September 23, 2024
"That’s the kind of feature that never would have made it to the top of anyone’s backlog without design."
Gretchen AndersonScaling the Human Center
June 8, 2017
"Ambiguity is considered a problematic in design, but ambiguity can be a feature."
Lori Muszynski Peter MerholzKeeping Design Weird
October 2, 2023
"Remote testing helps get closer to real-world results because users are in environments customized for them."
Sam ProulxSUS: A System Unusable for Twenty Percent of the Population
June 9, 2021
"Researchers often treat users as checkboxes, going in, doing research, checking the box and leaving."
Prayag Narula Rida QadriHCI 2.0: Humanity Deserves the Attention that UX Research has to Offer
March 28, 2023
"Assessing feedback urgency means understanding if the issue blocks critical work or if there are workarounds."
Deanna SmithLeading Change with Confidence: Strategies for Optimizing Your Process
September 23, 2024
"Reports aren’t always required; findings can be integrated directly into design docs or the product itself."
Lija HoganDoing more with more: Lessons from the Front Lines of Democratization
March 9, 2022
"Whenever someone makes a game accessible today, it’s considered an inspiring hack not a built-in feature."
Sam ProulxTo Boldly Go: The New Frontiers of Accessibility
March 11, 2022
"Sponsor sessions do not overlap at all with the main programming. It is 100% fully optional."
Bria AlexanderOpening Remarks
October 3, 2023
Latest Books All books
Dig deeper with the Rosenbot
How does Rally’s research infrastructure facilitate participant management and integration with enterprise data systems?
What are practical ways researchers experience 'aha moments' during their reflection process?
How should a vision be documented and communicated for maximum organizational buy-in?