Product Wars.

Some say: understand users, have a strategy, take the time to build an amazing & delightful product

Others say: just build, ship quick & often, experiment, assess user reactions, learn, repeat

Both camps have evidence.

So what’s really going on?

Like a tweet👇🏾
(A)
Neither approach is as successful as advertised.

It’s just classic survivorship bias.

The successful ones try to dissect the elements of the approach that made their product or company successful, tweet about it, write books about it. And they do this with high confidence.
(B)
It depends on the type & stage of product.

An approach that works for a late-stage product can fail miserably for an early-stage product.

An approach that works for a b2b product can fail miserably for a consumer product.
(C)
These recommendations are overly simplistic.

They ignore the strengths (and weaknesses) of the people working on the product.

Need to match the approach with the team's strengths & weaknesses to achieve the best results under the circumstances.
(D)
All of the above

[if you select this, also select which of A, B, C is the *primary* issue]
(E)
None of the above

[if you select this, consider replying below with your diagnosis]
Lastly, I'd love to get feedback on Question-based threads such as this one. My hope is that they make a greater impact per impression because they provide thinking prompts for complex topics. They don't provide the closure & recipes that my other threads do, but seems worth it?
To expand on that: for some of these Question-based threads, I feel like I have high confidence on what the "right answer" is. But my sense is that it's better if I pose a question along with a set of possible answers, because it prompts people to solve the problem on their own.
So let me know if I'm missing anything.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Shreyas Doshi

Shreyas Doshi Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @shreyas

13 Dec
A thread of resources for aspiring & new Product Managers:

(should also be useful for Eng, Design, Data Science, Mktg, Ops folks who want to get better at PM work or want to build more empathy for your PM friends ☺️)

(oh, and pls also share *your* favorite resources below)

👇🏾
1/

Product Management - Start Here by @cagan
(hard to go wrong if you start with Marty Cagan’s work)

svpg.com/product-manage…
2/

Tips for Breaking into PM by @sriramk
(I’ve recommended this thread in my DMs more often than any other thread, by a pretty wide margin)

Read 21 tweets
7 Dec
The 10 Commandments of Product Management:
1/
Thou shall focus on The User.
2/
Thou shall not optimize for product outputs. Thou shall optimize for business outcomes.
Read 22 tweets
5 Dec
You (at a project status meeting):
Project ABC's status is Yellow
Need [X] more resources to get it back on track.

Your Manager’s Manager (YMM):
We need to zoom out first
I would like to see a doc [or slides] with our strategy, roadmap & resourcing requests for Project ABC.

👇🏾
You:
OK, I have to deal with Acme Inc this week but can get that to you by next Friday

YMM:
Hmm… we really need this sooner.
Can you share by Monday instead?

You: (🤔this must be important for YMM, so I should do what’s being asked)
OK, will do

👇🏾
[On Monday]

You: (📨in email to YMM, cc’ing your manager)

Dear YMM, here’s the document you requested in last week's status meeting. Please let me know your feedback. I am happy to meet and discuss this further so we can proceed with the revised plan for Project ABC.

👇🏾
Read 7 tweets
4 Dec
A surprisingly high % of stupid arguments & fights on Twitter are rooted in a tiny number of fairly obvious fallacies.

Stupid arguments & the fallacies that feed them, a thread:
Fallacy 1/

Just because it’s true that all squares are rectangles, you argued that all rectangles must be squares. (And you did it with so much swagger.)
Example of Fallacy 1

X says: Successful people aren’t afraid of hard work.

Y argues: That’s BS. I work 90 hours a week at Tech Co and am still stuck in this dead-end job.
Read 16 tweets
3 Dec
Most interview frameworks (and most work environments in general) tend to favor the verbally charismatic.

Verbal charisma is IME the #1 reason that otherwise-smart companies hire leaders who end up being quite incompetent on the job (and get fired in 6-18 months).
Since a bunch of folks asked about ways to identify such cases during the interview process, here's a thread with archetypes & concrete ways to detect each one:
Besides this, one skill I've tried to build over the years is to separate the message as much as possible from the messenger.

This helps me evaluate the quality of what is said (most important) independently from how it is said (fairly important) & who says it (least important).
Read 5 tweets
3 Dec
This is well said.

Exceptional product people understand it and use it in their work.
Relevant framework (with examples, including Amazon, Netflix, YouTube)
Read 5 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!