A brief thread on

Impact = (Execution ^ Strategy) × Market

for product people:
Obviously, this is not a formal mathematical formula. Its goal is to help us understand & explain to others the *relative* roles of the factors that determine long-term impact. To understand it, it’s useful to assign a value of 0 to each factor (while keeping the others non-zero)
Let’s start with:
Strategy = 0 (others non-zero)

You get:
Impact ≈ Market

What it tells us:
A very bad strategy won’t kill you. But if you don’t fix it, it will severely limit the impact of your execution over the long term.
Now let’s set:
Execution = 0 (others non-zero)

You get:
Impact ≈ 0

What it tells us:
Abysmal execution almost always assures zero long-term impact, regardless of our strategy or market.

That is why I’d rather have some execution with no strategy, and not the other way around.
Finally:
Market = 0 (others non-zero)

You get:
Impact ≈ 0

What it tells us:
Lack of a market (or at times, a rapidly shrinking market) also kills our future impact over the long term.
As I said above, I’d rather have some execution and no strategy. But also note that strategy has an exponential effect on your execution. So I’d rather have excellent strategy & just OK execution vs. excellent execution & just OK strategy. This is counterintuitive for many people
In practice, if you make superb strategy choices i.e. how you differentiate your product and/or distribute it to create lasting competitive advantage, you can afford to have OK execution and still end up in a very good place over the long term.
Of course, the very best teams nail both strategy and execution. And that is what you should aim to do too, as a leader of a product team. When your business and your team’s future is at stake, why become dogmatic about an extreme position just for some Twitter likes & retweets?
That is why broad proclamations like “Execution is everything, Strategy is only for MBAs” or “Strategy is everything, Execution is for losers” might appear to be provocative and fun on Twitter, but are not very helpful in practice (and might even be harmful).
As a leader, you need to obsess over both your strategy and your execution. How much you obsess over each of them depends on your product’s context. That also changes over time as you assess current reality and decide what it will take to reach where you want your product to be.
Last thing:

(for leaders who are very good at strategy)

When you’re just starting to build a team, it is usually a better idea to hire people such that your team will be excellent at execution, even if that comes at the expense of your team being somewhat weak on strategy.
Because it is easier to add strategic discipline to a team that's excellent at executing than to add execution discipline later on.

How a new team executes sets its early culture a lot more than how (or if) it strategizes.

And that early culture is very hard to undo later.
This covers the basics. Will cover some more advanced aspects for a future thread, if there's interest. For instance:

- When to not worry about strategy at all

- What to do if your strategy needs to be the same as your competitor's

- The role of strategic assets & momentum
Since some folks asked, I figured some definitions might be useful👇🏾
Product strategy is about the choices you make to differentiate & distribute your product to create long term competitive advantage, and tying these choices to a credible action plan.

Product execution is about the pace at which you deliver and the quality at which you do it.

• • •

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

11 Sep
My Slack policy:

Closely track 2-3 channels that matter most for my team’s priorities

Largely ignore the rest

Chime in as a last resort (often the team will resolve the issue on their own, without needing me to “provide value”)

Mobile / after hours notifications OFF

Contd.👇🏾
Respond to most DMs ~immediately (except those sent after hours)

Don't use the Slack native app on my laptop

Pin the Slack tab in Chrome (along with my standard 5-6 other pinned tabs)

Check the Slack app on the phone 2-3 times over the weekend (for any @ mentions or DMs)
Star the important channels

Set a Slack auto-responder when on vacation

Mute the Slack tab before starting "deep work"

Quickly redirect complex team discussions to a doc / email (Slack is often a great discussion starter, but also not the best discussion resolver)
Read 9 tweets
27 Aug
If you lead teams that are directly involved in conceiving, building & launching products (i.e. product mgmt, engineering, design, user research, data science, product ops, product mktg, ...), this thread is for you.

Top 5 must-read books for product leaders:
1)
Working Backwards, for principles & tactics on operating
amazon.com/gp/product/125…
2)
The Mom Test, for truly understanding your customers
amazon.com/gp/product/149…
Read 18 tweets
16 Aug
A thread with 7 high value ideas & habits that took me more than a decade of my career (and dozens of costly mistakes) to learn:
1/

Most Execution problems are really Strategy problems, Interpersonal problems, or Culture problems.

Good leaders execute well because they see this. They fix the root problem.

Bad leaders struggle because they have a habit of sticking Execution band-aids on very deep wounds.
2/

In a high leverage role, you can think of doing your work at 3 levels

-The Impact level

-The Execution level

-The Optics level

Each level is important. But the level at which you think *by default* matters a lot. This default becomes your habit. You are now on autopilot.
Read 18 tweets
31 Jul
July 2021 content recap:

Job change decisions
Evaluating a company
Calendar & todo list
Placebo productivity
Firefighting
3 key cognitive biases
Writing culture
Megacorps
Hard in practice
Product leaders & mistakes
Technique & mindset
Underrated job search tip
and more...

👇🏾
A thread with 8 ideas I’ve found useful over the years, from my own experience and from speaking with 100s of talented & ambitious tech people about making better job change decisions
A thread on evaluating the caliber of people at a company as a job candidate
Read 21 tweets
27 Jul
A tragedy with most megacorps is that they program their talented & ambitious product people to conflate what it takes to get promoted with what it takes to create actual customer value. Image
What can megacorps do about this?

I am not an expert and I don't know if anything significant can be done. Megacorps are incredibly complex entities and I doubt that any simple/obvious/seductive advice such as "do X, don't do Y" is practicable enough to effect meaningful change.
However, I do think that there's a concrete lesson for talented & ambitious people working at megacorps.

If you want to eventually build your career outside of megacorps, you need to avoid drinking the megacorp kool-aid.

This is not easy, but quite do-able with self-awareness.
Read 7 tweets
12 Jul
The MSN list is a simple & powerful format for hiring managers to create clarity on what they are looking for when hiring for a given role

It cuts through the noise of typical JDs & forces you to focus on what really matters for *this* role.

The MSN list, explained in 6 tweets:
Here’s the format of the MSN list

Must
• ...
• ...
• ...

Should
• ...
• ...
• ...

Nice
• ...
• ...
• ...

(told ya, simple!)

The rules are also simple

-Max 3 bullets each for M/S/N

-Each bullet is an atomic attribute

-You can evaluate each in the hiring process
A real-ish example for a specific senior PM role 👇🏾
Read 7 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!

:(