Add these 10 biases to your product team's shared vocabulary
1–Confirmation Bias
2–Fundamental Attribution Error
3–Availability Heuristic
4–Plan Continuation Bias
5–Law of Triviality
6–Curse of Knowledge
7–Law of the Instrument
8–OutcomeBias
9–Bandwagon Effect
10–Bias Blind Spot
The benefits of deeply understanding these biases & creating psychological safety for surfacing them:
- Better product decisions
- Better execution
- Happier teams
Descriptions, along with product team-specific examples of each of these biases👇🏾
1—Confirmation Bias
Interpret info/data that confirms one's preconceptions
Examples.
experiment results positive?
“yay, ship it!”
results negative?
“must be something wrong with our bucketing & analysis”
user says they need X
is X in the roadmap? yes
“we have user validation”
2—Fundamental Attribution Error
Attribute people’s behaviors to their character & justify one’s own behaviors with the situation & context
Example.
Bob: “Alice just doesnt care about users”
Also Bob: “my team's feature was buggy becos we were understaffed & under time pressure”
3—Availability Heuristic
Evaluate & decide based on data or anecdotes that can be readily recalled right now
Example.
PM: So we can do A or B. Neither option is perfect, will need to pick one
Exec: I was talking to Acme Inc last week—they’d love B & dislike A. Let’s do B
PM:👌🏾
4–Plan Continuation Bias
Unwillingness to change current plan despite new information or conditions.
Example.
PM: Apple’s launch has really changed the landscape.
Eng Mgr: We’ve already spent 6 months building this feature. I’m not going to tell my team to change course now.
5–Law of Triviality
Giving disproportionate attention to trivial issues (while ignoring big ones)
Examples.
PM Director: Product X is late by 3 weeks
Exec: I want a full report on this
Designer: Should we fix this border?
PM: Leave it in so execs can give that feedback to us
6–The Curse of Knowledge
People assume that others have the same knowledge & expertise as them
Example.
PM Director: "I just wish our teams would prioritize smarter & use common sense"
The said teams: "we don’t understand what these goals & activity are all adding up to"
7–Law of the Instrument
If all you have is a hammer, everything looks like a nail
Examples.
Eng Mgr: we followed the standard process, it isn't our fault that there were PR issues
PM: we launched feature X with similar uplift, so we must launch feature Y too for consistency
8–Outcome Bias
Judging the quality of a decision or quality of work by its outcome
Examples.
Eng Mgr: we’ve never done pre-mortems & things have turned out fine. I don’t see the need for one
Promo committee: revenue is through the roof, we should promote Bob despite the snags
9–Bandwagon Effect
Conforming with the majority's beliefs, customs, behaviors
Example.
PM Dir: "I didn't agree with the CEO's decision but I could tell from the body language in that meeting that I was the only one, so it didn't make sense for me to push back"
Eng Dir: "Me too"
10–Bias Blind Spot
Seeing oneself as less biased than others
Example.
Carol (PM): "that team should have nixed their project much earlier. fell prey to sunk cost fallacy"
Also Carol: "progress is slow, but we need to continue investing here so we can see results next year"
Which of these biases do I personally suffer from?
All of them.
Most notably:
Confirmation Bias (almost daily)
Availability Heuristic (almost weekly)
Fundamental Attribution Error (at least once a month)
Curse of Knowledge (5 yrs ago, almost daily)
Bias Blind Spot (not sure)
Dealing with these biases is a bit like meditation.
Goal of meditation isn't to stop all thought.
It's to observe that thinking is happening.
Similarly, we can't stop biased thinking.
But by understanding them well & giving them names, we can observe biases when they appear.
Related resources👇🏾
This thread was about biases that affect our decision-making as a product person or a product team.
Here are the biases that your users & customers are likely to have—understand these biases so you can build better products for them:
Some ppl are surprised by the exuberance with which PG’s Founder Mode blog post has been received. There are many reasons for its strong resonance.
But the main one is that it introduces a catchy term for something that many founders & leaders have seen & experienced first-hand.
Here’s my prediction: a majority of founders & leaders who said to themselves this weekend “henceforth I am going to be in Founder Mode” are likely to mess it up.
That is not bad per se. They might still end up being in a better place than if they continued with Manager Mode.
Product life in midsized & large companies starts making a lot more sense when you understand that a large % of middle & upper management thinks their main job is to (i) try & decipher what the CEO wants done (ii) align their org with it (iii) propose a plan that the CEO approves
This is instead of *often* telling the CEO what actually needs to be done, in a way that is grounded in (a) deep insight into customers & market (b) creative product & GTM solutions
Many in middle & upper management will of course blame incentives set by the company for this.
And they are not wrong. But it is worth evaluating how much of one’s career (and life) one wants to spend in aligning perfectly with incentives set by another party.
Everything we create, everything we do, it all starts with our thinking
Clear thinking drastically improves odds of success in all departments of career & life
While clear thinking is quite rare, it can be developed with practice
Advanced principles for clear thinking:
(1/12)
1) Essence first. Not story. Not analogy
Most people get seduced by great analogies & exciting stories.
Clear thinkers don’t *form* their thinking via analogies. They identify the essence of the issue, in their specific context. Then, they use analogies as one of their inputs.
2) WAYRTTD
“What Are You _Really_ Trying To Do” is a simple but powerful tool to make you pause & identify your real goal
Most people move too quickly to How & When to do a given task. But the task isn’t the goal
Clear thinkers have built a habit of asking themselves WAYRTTD.
Apple Pie Position:
A statement that instantly elevates the person who is saying it and is simultaneously hard for anyone else to push back on, and so everyone avoids the personal risk and just nods “yes”, even though its actual value in this specific situation might be… twitter.com/i/web/status/1…
Okay, so now that you understand Apple Pie, here’s your crash course on dealing with Apple Pie:
1) The greatest thing about Apple Pie Positions is that you now have a name to assign to a complex behavior (and it is a cute name, which helps a lot). Once you share this idea with… twitter.com/i/web/status/1…
One other important thing:
Note that Apple Pie Positions are, by definition, specific to the context. This means that the same sentence can be either the right thing to focus on, or it can be an Apple Pie Position. The way you determine which is which is through good judgment.