Shreyas Doshi+ Your Authors @shreyas early PM & first PM lead @stripe. formerly a PM lead @twitter @google @yahoo. I share offbeat ideas here—useful for some, useless for many, not for everyone ❤️ Jul. 12, 2020 3 min read + Your Authors

Why do smart product people & teams often build products with mediocre or no impact?

A cautionary thread of biases and fallacies we encounter when building products👇🏾

1/10

1/ The Execution Orientation Fallacy

We craft flawed product strategies & make suboptimal product decisions because we base these decisions on what we know we can easily execute today.

Shortsightedness & Low Agency typically cause this fallacy.

I see this one all the time.

2/ The Bias-for-Building Fallacy

We don’t take the time to thoroughly understand the problem, domain, competitors & other determinants of product success because we feel compelled to be in constant motion. We tell ourselves we must begin building & just iterate based on feedback

3/ The IKEA Effect for products

Usually applicable to an 𝘦𝘹𝘪𝘴𝘵𝘪𝘯𝘨 product that’s struggling, we base our 𝘤𝘶𝘳𝘳𝘦𝘯𝘵 product decisions on 𝘱𝘢𝘴𝘵 product execution because we’re too attached to the work we’ve already put in & don’t want it to "have been for nothing".

4/ The Focusing Illusion for products

When we talk to customers about the problem that our product solves, we overestimate its severity & get surprised when the customer doesn’t end up buying or using our product. Any problem will feel more critical while you’re talking about it

5/ Maslow’s Hammer

We use a framework, a skill, or a proxy that we are most comfortable with (or one that our company endorses) even when its utility is limited or counterproductive in a specific product context.

Example: FB uses metrics as a hammer for most product problems.

6/ The Authority Approval Bias

We devise product strategies, conceive product features & propose product plans based largely on what we think is going to either confirm the beliefs held by those in a position of authority at the company or more easily get us approval to proceed.

7/ Russian Roulette for products

We don’t account enough for scenarios that could, under certain conditions, lead to a catastrophic outcome for our product or a PR nightmare for our company.

Usually found in companies where “following orders” or “just get it done” is rewarded.

What to do?

The ultimate onus for avoiding these traps is on PM/Eng/Design leaders in middle mgmt. They need to recognize & call out whenever they see these issues crop up: upwards (pushing back on sr. mgmt) AND downwards (educating their product teams).

No other easy answer💪🏾

Related further reading.

Present bias:  https://en.wikipedia.org/wiki/Present_bias 

Status quo bias:  https://en.wikipedia.org/wiki/Status_quo_bias 

IKEA effect:  https://en.wikipedia.org/wiki/IKEA_effect 

Plan continuation bias:  https://en.wikipedia.org/wiki/Sunk_cost#Plan_continuation_bias 

Bandwagon effect:  https://en.wikipedia.org/wiki/Bandwagon_effect 

contd..

Maslow’s hammer:  https://en.wikipedia.org/wiki/Law_of_the_instrument 

Availability cascade:  https://en.wikipedia.org/wiki/Availability_cascade 

Focusing illusion:  https://fs.blog/2015/09/focusing-illusions/ 

Russian roulette:  https://en.wikipedia.org/wiki/Russian_roulette 

Back to the top of this thread:

Want even more on these topics?

Here's a B2B Product Management story that depicts the perils of the Focusing Illusion for products:

Here's a tweet-sized story that I often seen repeated on product teams, related to the Bias-for-Building Fallacy:

Here's a tweet that depicts the common proxies used within companies, related to Maslow's Hammer:

Incompetent executives can unwittingly cause the Authority Approval Bias:

A thread on preventing catastrophic mistakes, related to Russian Roulette for products:

A sensible null hypothesis when building B2B products (among other things, helps combat these biases & fallacies)

A sensible null hypothesis when building Consumer products

Update:

Version 2.0 of this thread is now available in article format, in case you want to re-read it in one place, bookmark it, or share with friends or colleagues who aren't on Twitter. It also includes additional suggestions on combating these biases.
 https://www.linkedin.com/pulse/why-products-dont-succeed-7-biases-product-teams-shreyas-doshi/ 


You can follow @shreyas.



Bookmark

____
Tip: mention @threader_app on a Twitter thread with the keyword “compile” to get a link to it.

Enjoy Threader? Sign up.

Since you’re here...

... we’re asking visitors like you to make a contribution to support this independent project. In these uncertain times, access to information is vital. Threader gets 1,000,000+ visits a month and our iOS Twitter client was featured as an App of the Day by Apple. Your financial support will help two developers to keep working on this app. Everyone’s contribution, big or small, is so valuable. Support Threader by becoming premium or by donating on PayPal. Thank you.


Follow Threader