Creative Failure Review
Learn from a failed idea without destroying the contributor's confidence
- Difficulty
- Moderate
- Time to result
- ~days to results
- Steps
- 6
- Confidence
- 97%
Creative Failure Review combines a learning postmortem with active protection of the contributor's confidence. After an idea fails in the market, the leader first separates the person from the result and acknowledges the value of having run the experiment. The team then reviews what went right, what went wrong, and what might have changed the outcome. Retrospective claims such as 'I knew it all along' are challenged if the concern was never raised before execution, because they add blame without improving the original decision. The review allows three honest conclusions: change the idea, change the execution, or accept that sound work sometimes fails. It ends by restoring forward motion and inviting another contribution.
Origin
Extracted from The Diary of a CEO
Core principles
- 01A market failure does not prove the original contribution was foolish
- 02Leaders protect the willingness to contribute again
- 03Hindsight criticism has value only when it improves learning
- 04Some sound ideas and executions still fail under real conditions
How to run it
- 1
Protect the person
State clearly that one failed outcome does not make the contributor a pariah. Recognize the willingness to put an idea into the world.
Pro tip Thank the contribution before opening the analysis.
Watch out Do not use reassurance to avoid an honest review.
- 2
Reconstruct the decision
Return to what the team knew when it approved the idea. Preserve the difference between a reasonable bet then and an obvious result now.
Pro tip Use the original brief and assumptions if available.
Watch out Hindsight makes uncertain outcomes look inevitable.
- 3
Review both sides
Identify what worked, what failed, and what could have been done differently. Include execution and external conditions, not only the idea.
Pro tip Begin with the elements that worked to prevent a blame-only review.
- 4
Challenge silent certainty
If someone says they always knew it would fail, ask why the concern was not raised before execution. Convert valid concerns into future decision criteria.
Pro tip Record the new warning signal in the next brief.
Watch out Do not punish dissent that actually was raised and ignored.
- 5
Choose the learning
Decide whether to change the idea, the execution, or nothing because the conditions simply did not produce a hit. State the next experiment.
Pro tip End with an owner and a next move.
- 6
Restore contribution
Explicitly invite the contributor and team to generate the next idea. The review is complete only when creative participation can continue.
Pro tip Ask for another idea in the same session when appropriate.
Watch out Forced enthusiasm can feel dismissive if grief over the work has not been acknowledged.
In the wild
The guest describes a meeting idea that everyone supports before it reaches the market and fails. Her leadership response is to help the contributor get back up, review what worked and failed, and prevent silent hindsight critics from piling on.
→ The team extracts learning while preserving the person's ability to contribute again.
A team ships a feature after users express interest, but adoption is low. The review confirms the research was reasonable, finds that onboarding hid the feature, and tests a clearer entry point without branding the proposer as unreliable.
→ The next test addresses a specific execution weakness while creative confidence remains intact.
Common mistakes
Monday-morning blame
People who did not object earlier portray the failure as obvious. This substitutes status protection for useful learning.
Protecting confidence by skipping analysis
The leader offers encouragement but never examines the decision or execution. Confidence and accountability can be protected at the same time.
Treating every miss as preventable
The team invents a fix even when the idea, conditions, and execution were reasonable. The guest allows for the conclusion that sometimes a sound attempt simply does not hit.
Is it for you?
Best for
It is best for campaigns, launches, and experiments whose outcome was uncertain before reaching the market.
Not ideal for
It is not ideal for excusing repeated negligence, concealed risks, or conduct violations.
From the transcript
“As a leader, it's like you gotta come in and protect the people's spirit.”
“What was the thing that went right? What was the thing that went wrong?”
“Sometimes the conditions were right, the idea was right, it was executed right, it just didn't hit.”
From the episode
CMO Of Netflix, Uber & Apple! Work Life Balance Is BAD Advice! "I Lost My Baby & My Husband!" - Bozoma Saint John