@readwiseio save thread

More from Shreyas Doshi

A thread of product management frameworks:

(this might be useful if you are a product manager, product leader, or founder)

Before we jump in:

Frameworks will not fix all your problems.

Used right, they should help you
1) better understand your context
2) create structure for problems
3) communicate ideas & solutions

I often use these frameworks in my product work, sometimes without realizing it.

1/
3X framework (Kent Beck)

A product can be in one of 3 stages
1. Explore
2. Expand
3. Extract

For product leaders this is the most vital framework to understand because almost every important decision should account for the stage your product is

Examples of decisions you can make more rigorously with the 3X framework:
- optimize for inputs, outputs, or outcomes?
- set more qualitative or quantitative goals?
- how to measure progress?
- what skills to look for?
- how to evaluate PMs'

2/
5Qs for product rigor

1) Who is the customer?
2) What is the problem/opportunity?
3) What is the main customer benefit?
4) How do you know customers want this?
5) What is the customer experience?

This framework provides useful structure for product proposals, reviews, etc.

Shreyas Doshi
@shreyas

🗓️Recap of March 2021 content

Includes:
Solve THE problem
3 types of product leaders
Levels of product work
Getting work done
“I don’t know”
Good people, bad managers
Customer segmentation
LinkedIn Envy
On communication
Important definitions
Life-changing books
& much more..

👇🏾

A story that often plays out when we are not rigorous enough about the importance of the customer problem our product

A B2B Product Management Story: on discovering problems that customers actually care about

Very visual story thread\U0001f447\U0001f3fe pic.twitter.com/SQKpmLtBGC
— Shreyas Doshi (@shreyas) March 28, 2021

The 3 types / hats / modes of product

3 types of product leaders:

1) The Operator

2) The Craftsperson

3) The Visionary

It is important for you as a startup founder or CEO, product manager, or a product leader to deeply understand these types, as you make decisions on whom to hire or whom to work for.

Thread\U0001f447\U0001f3fe
— Shreyas Doshi (@shreyas) March 26, 2021

An extremely important observation about product

There are 3 levels to product work

(1) The Execution level

(2) The Impact level

(3) The Optics level

When an individual & their team are fixated on different levels, often there is conflict.

E.g.
PM is fixated on (2), Team on (1)
PM on (3), Team on (2)
PM on (2), Team on (3)
— Shreyas Doshi (@shreyas) March 12, 2021

A thread on getting work

How I like to plan my work:

Limit meetings
\u21d2 Long scheduled work blocks

At end of the work day, plan next day
\u21d2 Easier to disconnect, be present

Fit the next day's tasks in calendar
\u21d2 Forces prioritizing

Plan next week on Friday evening
\u21d2 Go into weekend with a clear mind
— Shreyas Doshi (@shreyas) March 17, 2021

Shreyas Doshi
@shreyas

Why does Your Manager’s Manager (YMM) request a deck/doc during a meeting, says it’s urgent, and then doesn’t respond for days after you create & send it?

Or, why does YMM often respond with trivial feedback (e.g. formatting) & not substantive feedback?

Answers in this thread👇🏾

Have you set an entirely new password on a site & said to yourself: “surely, I’ll remember it becos this site is so important for me”. Have you then gone on to forget that password the very next week?

Me too.

The reason for YMM’s odd behavior & my password optimism is the same.

That reason is the Focusing Illusion, first described by Daniel Kahneman.

The Focusing Illusion:
Nothing in life is as important as you think it is while you are thinking about it.

When YMM asked you to create that doc as one of the follow up actions during the Product Review, YMM fell prey to the Focusing Illusion.

Trust me, YMM had no intention of making you do busywork.

YMM truly believed that it was very impt & urgent to create that doc & review it.

This was YMM’s conception of how much of their future time was appropriate to spend on the item for which they requested that doc (Item A):

Shreyas Doshi
@shreyas

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.

Fallacy 2/

Just because you found an exception to a general pattern, you argued that the entire pattern is false.

Example of Fallacy 2

X says: Venture capital is useful for startups.

Y argues: Not true. Foo’s startup took VC money and they crashed & burned.

Z piles on: I agree with Y. In fact, Bar’s startup did not take VC money and it’s worth a bajillion.

Shreyas Doshi
@shreyas

If you’re a Startup trying to compete with a Megacorp—the 800-pound Gorilla in the space—you need to understand the tax inherent to being a Gorilla

And then you need to make that tax work against the Gorilla—with your product's positioning & features

A thread on Gorilla taxes👇🏾

1/
Collaboration Tax

Getting two or more product groups at a megacorp to collaborate on creating a seamless end user experience is the hardest problem in computer science.

(I am not joking)

Examples of Collaboration Tax:

Calendly exists because the Gmail team & Calendar team haven’t worked together on creating a more seamless experience for that use case.

Loom might succeed because the Gmail, Video, Meet teams at Google are probably too busy with their own goals.

The takeaway for startups:

If you can create meaningful value by seamlessly integrating features of two or more distinct Gorilla products, you will typically have a lot of runway before the Gorilla can get its act together and eliminate its Collaboration Tax.

2/
Denominator Tax

Once a Gorilla’s product reaches massive scale (i.e. the denominator for its metrics gets very large), the pressure of OKRs & incentives will often force the Gorilla’s product teams to prioritize breadth of usage more than depth of usage.

The paper is a good example of lots of elements of good experimental design. They validate their metric by showing lots of variants give consistent results. They tune hyperparamters separately for each condition, check that optimum isn't at the endpoints, and measure sensitivity.

They have separate experiments where the hold fixed # iterations and # epochs, which (as they explain) measure very different things. They avoid confounds, such as batch norm's artificial dependence between batch size and regularization strength.

When the experiments are done carefully enough, the results are remarkably consistent between different datasets and architectures. Qualitatively, MNIST behaves just like ImageNet.

Importantly, they don't find any evidence for a "sharp/flat optima" effect whereby better optimization leads to worse final results. They have a good discussion of experimental artifacts/confounds in past papers where such effects were reported.

Tom Hirst
@tom_hirst

How to create a freelancing website that makes money.

Everything I've learned.

A thread.

As a freelancer,

Your website is everything.

First, prioritise its existence.

Second, prioritise its improvement.

The technology you use is irrelevant.

- WordPress
- Notion
- Carrd
- Wix

It doesn't matter which you choose,

What matters is you have a website.

Pick a platform that you're comfortable with.

If you can:

- Capture leads
- Add content easily
- Have a clear design

You're good.

If your website doesn't get leads,

It's not working.

Don't rest on a website that doesn't work for you.

Improve it until it does.

Shaun Russell
@_ShaunRussell

"I really want to break into Product Management"

make products.

"If only someone would tell me how I can get a startup to notice me."

Make Products.

"I guess it's impossible and I'll never break into the industry."

MAKE PRODUCTS.

Courtesy of @edbrisson's wonderful thread on breaking into comics – https://t.co/TgNblNSCBj – here is why the same applies to Product Management, too.

"I really want to break into comics"

make comics.

"If only someone would tell me how I can get an editor to notice me."

Make Comics.

"I guess it's impossible and I'll never break into the industry."

MAKE COMICS.
— Ed Brisson (@edbrisson) December 4, 2018

There is no better way of learning the craft of product, or proving your potential to employers, than just doing it.

You do not need anybody's permission. We don't have diplomas, nor doctorates. We can barely agree on a single standard of what a Product Manager is supposed to do.

But – there is at least one blindingly obvious industry consensus – a Product Manager makes Products.

And they don't need to be kept at the exact right temperature, given endless resource, or carefully protected in order to do this.

They find their own way.

$Paul M Domenick\U0001f43a$