Shreyas Doshi Profile picture
Dec 17, 2021 42 tweets 13 min read
As they grow in size, teams within megacorps and startups tend to implicitly bias more towards Project Thinking and not enough Product Thinking.

Product Thinking is a mindset and a process that, once you see, you cannot unsee it.

Product Thinking, Project Thinking, a thread: Image
From my experience working in individual contributor & leadership roles over the past couple of decades, and from my advising work with a number of fast-growth startups, I have often seen myself and founders / CEOs / execs worry about these things: Image
And, having been in the trenches of product work for a large part of my career, and having managed / mentored / coached hundreds of PMs & PM Managers, I have often seen myself, and other ICs & managers worry about these things: Image
How is it that we all say we want the same thing i.e. to create tremendous value for our customers, to grow the company’s business and its positive impact, and yet we end up with such conflicting versions of “truth” in the throes of the inherent complexity of our work?
At least part of the answer lies in the observation that we are often speaking to each other in different languages, but are unaware of it. We litigate the minutiae of a decision, without recognizing that one of us is engaged in Product thinking & the other in Project thinking. Image
What is Product thinking & Project thinking?

Let’s dive deeper into that, because we cannot make much progress without first understanding these things.

And there’s no better way to start our journey than via a couple of example scenarios we see at work.

(based on real events)
Here, you have Alice (former PM, now General Manager) and Bob (PM, reports to Alice) discussing an escalation to the company’s CEO for 2 urgent feature requests.

Notice Bob’s response here.

It is a fairly common response in such situations & it is classic Project Thinking. Image
Let’s take another scenario.

Here, you have Dan (PM) at a product review meeting with Eve (CEO).

Notice how Eve asks a question that’s focused on the customer experience, and how Dan’s response is about resources, launch scope, SLAs.

Classic Project Thinking again. Image
Having seen some examples of Project Thinking, let’s explore more formally how Project Thinking & Product Thinking differ.

And there’s no better place to start here than to look at the types of questions that interest us when we are doing Project Thinking vs. Product Thinking.
Notice how “When” and “Who” are top of mind during Project Thinking, whereas “Why” and “What” are top of mind during Product Thinking. In both modes of thinking, we ask “What else” and “How”, but the actual questions asked differ depending on which mode we are in. Image
The difference in what these questions are seeking (and what answers they will elicit) is really the essence of the difference between the Project Thinking mode and the Product Thinking mode: Image
With this foundation, we are now ready to more formally define Product Thinking and Project Thinking.
Project Thinking:

Project Thinking is about understanding expectations, formulating plans, marshaling resources, and coordinating actions to meet those expectations.
Product Thinking:

Product Thinking is about understanding motivations, conceiving solutions, simulating their effects, and picking a path based on the effects you want to create.
Let’s now look at the two scenarios we saw earlier, and see how those conversations might go if the PM had applied more Product Thinking instead of solely applying Project Thinking.

As a reminder, this is what these scenarios looked like with Project Thinking: ImageImage
Here, when PM Dave is applying Product Thinking, the response to Alice’s question is a lot more nuanced. It turns out that one of the feature requests is actually quite strategically aligned and Dave recommends just building it. For the other request, Dave recommends a workaround Image
Not just that.

Whereas Project Thinker Bob saw this situation as a crisis, Product Thinker Dave has turned this crisis into an opportunity. He can see how valuable it will be for his company if Customer X can be a key “lighthouse customer” for the new Audit Logging feature.
Let’s now look at the second scenario. Here, Product Thinker Pat knows that a 2 day response time would be less than ideal and they had proactively identified a creative solution to reduce the response time to <10 minutes for a subset of these VIP customers. Image
By using the Product Thinking mode in this situation, Pat is able to see beyond the immediate resourcing constraints that the Support team faces, and presents much clearer trade-offs to CEO Eve: “We can create a better experience with creativity, and such-and-such investment.”
There is indeed a pretty wide contrast between the conversations (and often outcomes) when we are in Project Thinking mode vs. when we are in Product Thinking mode.

Here’s a cheat sheet that can help us better understand how these modes differ and in what ways they are valuable: Image
Before you proceed, I would encourage you to review that cheat sheet one more time, and evaluate how these distinctions might apply to your work, and, if you lead a team or a company, to the work that your team does.
You are probably now asking: how can I apply Project Thinking and Product Thinking in my work?

For any non-trivial project, the right answer isn’t this: Image
Nor is it this: Image
Nor this: Image
The right answer for any sufficiently complex product endeavor is usually this. Time & time again, I've found it useful to start with the Product Thinking hat, arrive at a differentiated, creative solution, assess its feasibility with my Project Thinking hat & iterate a few times Image
At the end of this process, you will have much greater clarity on the ultimate solution & the steps you need to take towards making this ultimate solution a reality, taking into account the constraints you face today & ones you might face tomorrow.

That enables decisive action.
Before we proceed, I want to reemphasize one thing: Product Thinking is not better than Project Thinking. For a team to succeed consistently, it needs to be able to do both Product Thinking & Project Thinking very well. Some of us will be better at one than the other. That’s okay
Because in reality, you can learn Product Thinking, and you can also teach your team the discipline of Product Thinking. To succeed, we need not all be world class Product Thinkers. But it helps if people can recognize these two modes, so they can communicate & decide better.
This thread is getting long, so I will now leave you with a primer to improve your own Product Thinking and team others about it.
Having known and talked to many capable Product Thinkers over the years, here’s how Product Thinking breaks down:

1. Suspend the Project Thinking mindset
2. Prioritize your real goals
3. Understand your users' needs
4. Generate options
5. Simulate Image
Note how each of these steps is fairly straightforward (perhaps even obvious). Despite that, the problem I see time and time again is that we don’t really give ourselves the chance to systematically perform these steps.
We are in a hurry, or we think we already know. Oftentimes, that’s the real enemy of Product Thinking. And remember that each of these steps involves great skill – Product Sense being the key skill that we can utilize to put Product Thinking in practice.

blog.tryexponent.com/improve-your-p…
Let’s now look at some examples of products & features that I think demonstrate the essence of the steps we looked at.
I think Spotify Wrapped is a great example of Product Thinking. The team at Spotify probably had a 1000 reasons not to build such an engaging recap experience (like, we have bugs to bash, dozens of feature requests & we’re building a "silly" recap feature, used once-in-a-year?) Image
Another good example is the Gmail “did you forget to attach the file” feature. This feature has saved me from embarrassment 100s of times over the years, and without fully exploring the option space, they wouldn’t have been able to build it as delightfully as they have done it. Image
Another example is this screen in @usehonk (h/t @round). The attention to detail, the insight that anytime we are asked to sign something, we are wired to pay close attention to what we are signing, and the simulation of the effects that will have on the user are all admirable. Image
To end this thread, I will leave you with two things.

First, for fun, watch this short clip from Avengers: Infinity War
As I said earlier, Simulation is the biggest secret of Product Thinking. If you can do better simulations, and you can hire/encourage certain people on your team to simulate, trust me, you will be able to do things that look like magic to the uninitiated. Just like Doctor Strange
Lastly, once you are adept at Product Thinking, you'll be able to apply it to many things beyond just building products. Ultimately, Product Thinking is about a systematic evaluation of your real goals, the effects you want to create, and exploration of how to create said effects Image
That’s all for today. I am not the first person to talk about Product Thinking (and pretty sure I won’t be the last), but I hope this thread is useful in helping you create better products, better experiences, greater impact, and wiser teams.

I wish you all the very best! Image
If you're looking for more, check out / bookmark this 1+ hour Twitter Spaces Q&A on the topic of Product Thinking & Project Thinking. Many thanks to @michael for help with moderating the session.
twitter.com/i/spaces/1YqGo…
For even more weekend listening, check out / bookmark this 1+ hour Q&A on Product Sense, which is an essential skill for Product Thinking. Many thanks to @sabakarimm for help with moderating this session.
twitter.com/i/spaces/1Yqxo…

• • •

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

Sep 30
New product initiatives within already-successful companies often fail to achieve their potential because they have too much rather than too little.

Too much of:

1) headcount: you are now under pressure to come up _something_ for all these people to do

👇🏾
2) democratic decision making: creative product ideas usually get killed (or watered down) by groups of people

3) optics requirements: need to manufacture metrics & milestones to *show* straight-line progress and demonstrate certainty during an inherently uncertain journey
4) involvement of the “core” product group: you have to make tremendous compromises within your new product to keep the leaders of the company’s core product happy
Read 6 tweets
Jul 8
Sharing a brief memo I wrote for a founder in response to this question:

What is product management?

Product management is the art, science, and practice of making successful products and making products successful.

(1/12)
2/
User adoption, Customer satisfaction, Business impact are good ways to begin measuring product success. Consistent product success comes from unique insight on customers & market, creative product solutions, and methodical execution in building & distributing the product.
3/
Anybody who has these abilities (or has the capacity & desire to develop them) can do product management. You don’t need a specific job title for this. In technology product companies, one or more of the founders initially perform the product management role.
Read 12 tweets
Jul 6
Some people who succeed wildly in school don’t achieve their apparent potential in the business world. Some others who do okay (or worse) in school manage to build an extremely successful life. Why is that?

What we learn in school & must unlearn in business & in life:

(1/10)
1/

In school:
Your teacher provides a rubric, you follow the rubric to a tee, you deserve an A.

In business & life:
There is rarely a rubric. Even if it exists, and you follow it to a tee, you often end up with average results, not outsized returns.
2/

In school:
If X is true then the opposite of X must be false.

In business & life:
If X is a good idea, the opposite of X can also be a good idea.

(source: Rory Sutherland)
Read 12 tweets
May 23
10 really great books:
(for B2B product people)
1/
The Mom Test: the bible (in my opinion) of how to understand what customers want and avoid the biases that nearly everyone in B2B falls prey to. This is among the books I recommend the most to B2B founders and senior product people.

amazon.com/The-Mom-Test-R…
2/
Amp It Up: an informative & actionable account of the operations & principles behind Snowflake’s success. Lots to understand & learn about how to build & scale modern B2B tech companies.

amazon.com/Amp-Unlocking-…
Read 13 tweets
May 20
This took me a long time to really understand: some people’s implicit goal in every interaction is to see themselves as higher status relative to the person or persons they are interacting with. That motivates (and explains) their body language, what they say and how they say it.
How to deal with such people at work?

1) If you report to them, and you don’t like this style, frankly you can’t do a whole lot. Just plan an exit/change when/if it makes sense for you

2) If they are a peer, frustrate them by being completely impervious to their shenanigans
This requires high self-confidence. They will eventually stop doing this with you and be forced to start focusing more on the content.

Most likely you won’t be their favorite colleague to work with, because you don’t bend to their need for dominance. But such is life 🤷🏾‍♂️
Read 7 tweets
May 17
A majority of arguments on Twitter are utterly stupid—they don’t change anyone’s mind, they just make people feel hurt, angry, frustrated.

Twitter should have Canned Replies (CRs)—the perfect reply so we can move on with our lives.

Until then, here are 10 or so CRs you can use:
Canned Reply 1:
I hear you.

Use when:
The other person seems triggered about something other than your tweet, decides to use your tweet to vent their frustration, perhaps unintelligible, perhaps aggressive, but you think they actually mean well, probably just having a bad day.
Canned Reply 2:
Perhaps you are right.

Use when:
The other person disagrees with your tweet, their reply does not suggest any curiosity on their part, you sense that they just want to be right, and frankly you don’t have the energy to debate the fine points of their argument.
Read 23 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

Don't want to be a Premium member but still want to support us?

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

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(