Why do smart companies & orgs make stupid mistakes?

A thread:
Last month, I gave a talk about product management & leadership @SVPMA.

This Tweetstorm covers one of the seven topics I presented at the talk.

It’s the topic that appeared to resonate the most with the audience. https://twitter.com/shreyas/status/1196807903929229313
Why does Facebook make stupid mistakes, over and over and over again?
What about the mistakes that Uber, Google, and so many others in our industry have made over the years?
Mind you, I’m not talking about “mistakes in hindsight”.

Rather they are the “what the heck were these people thinking?” flavor of mistakes.
When we read exposés in the press that lay out the timeline and events leading up to such mistakes (and there have been so many in just the past 5 years), the most common conclusion (incorrect) tends to be:

“The people in these companies are stupid”
The next most common conclusion tends to be:

“The people in these companies are evil”

(also incorrect)
So, what is actually going on when an otherwise smart, well-meaning organization makes obvious blunders?

And why do some organizations tend to do this over and over again?
While the exact details surely vary across these situations, one organizational cognitive bias most often at the root.

What is it?
People on Twitter, I present to you the preventable problem paradox:
Now, why do smart, even tremendously-successful organizations fall prey to this?
There’s no better way to understand that than watching this scene from Superman II.

It is, IMVHO, among the greatest 200 seconds in motion picture history.
Watch it. I’ll wait.

(For future readers: Use this link if the YT video gets taken down for some reason:
https://www.google.com/search?q=superman+ii+niagara+falls+scene )
No, really, watch that scene before moving to the next Tweet.
Welcome back. So, what did we just see?
Let’s break it down.
Clark Kent (who is actually Superman) at Niagara Falls with colleague (and love interest) Lois Lane.
Clark notices a little boy doing something dangerous / stupid at the observation deck.
Clark rushes towards the boy, asking him to stop. Boy’s mom also notices and manages to get the boy down. He's safe now.
Notice, Lois is oblivious of this event during this whole time.
Clark runs back to Lois asking her if she saw what just happened.
Lois ignores Clark and simply responds that she’s hungry.
Clark heads over to the nearby hot dog stand.

Boy is at it again, but this time, putting himself in even greater danger (he’s now on the other side of the railing).
And sure enough...
Boy is now falling. Yells.
Now, Lois springs into action. Somebody help!
Clark, at the hot dog stand by now, hears this.
Unidentified man yells “Somebody do something”

(as an aside: 1980s special effects at work here)
Clark Kent has now transmogrified into Superman, zips towards the falling boy.
So close.
Crowd cheering Superman along.
Superman manages to reach the boy just as the boy is inches away from certain death.
The appreciation begins.
The return journey.
Almost safely back on the ground.
Look at those faces, in awe, and appreciative of what Superman has just done.
Look at Lois Lane. Pretty much ignored Clark Kent earlier when he tried to save the boy, but is vying for Superman’s attention after this dramatic save.
Scene ends.
Now, I have a question for you.

If Superman is like most of us — if he cares about appreciation for a job well done — what will he do the next time he’s in this situation?
(A) Will he try to prevent the boy from falling?

Or, (B) will he let the boy fall, transform into Superman within a nanosecond, and heroically rescue the boy from certain death?
It should be obvious that, if he’s motivated by appreciation and accolades (as certainly most humans are), you should bet on (B), not (A), being the correct answer.
Mind you, this is not merely an academic question.
Because what you just saw happens in the organizations that we’re part of, every... single... day....
In fact, this is such a common phenomenon that once you understand it, you’ll see it everywhere. Companies, non-profits, government. Especially the government.
And while no organization (or leader) *wants to* incentivize problem creation over problem prevention, they unwittingly end up doing it anyway.
This paradox is so important for us to understand, as a community and as a society, that I’m going to share another story.
Paragraph 1:
Paragraph 2:
With this contrast between how humans innately perceive problem solving vs. problem prevention, is it any surprise that this paradox permeates almost every complex organization?
Let’s bring this back to product management (and leadership in general).
In the earlier stages of your career as a PM (or a leader), it makes sense for you to go in and solve whatever problem is facing the team.
And some PMs (and leaders), after multiple years of doing this, convince themselves that problem *solving* is their job. They come in to the office, look for the “problem of the day”, and then get to work.
However, if you want to be a true and unselfish leader of people,
to do what’s right for your company,
you need to be the captain who just avoids the iceberg,
and not the one who hits it and then heroically attempts to rescue everyone.
Which brings us to this question:
Leaders looking to combat the preventable problem paradox within their organization should:

1. Create awareness of its existence

2. Change the mechanisms for rewards and recognition

3. Embrace pre-mortems
Want to learn more about these solutions?

Share the excitement via your replies, quote Tweets, retweets, and faves, and I’ll post a follow up thread within the next few days.

(warning: it’ll be equally long :) )

To be continued...
If you reached this far (❤️), check out my talk about PM leadership from 2018 (along with another long Tweetstorm): https://twitter.com/shreyas/status/1058908181630398464
Update.

A Tweetstorm on pre-mortems is now available here: https://twitter.com/shreyas/status/1221257560033857536
It's worth reading this book passage too: https://twitter.com/dinesh_tewari1/status/1314579163043430408
This book passage is also worth reading: https://twitter.com/wgalyean/status/1218764760079986688
An excellent illustration: https://twitter.com/_workchronicles/status/1314436905501511681
You can follow @shreyas.
Tip: mention @twtextapp on a Twitter thread with the keyword “unroll” to get a link to it.

Latest Threads Unrolled: