Good product strategy clearly identifies target customer segments and non-target segments.
Bad product strategy either ignores customer segmentation or attempts to cater to all customer segments.
Good product strategy presents an honest assessment of the market, the competition, and the product’s current position.
Bad product strategy either downplays the competition or ignores these factors altogether.
Good product strategy creates clarity on customer needs. Good product strategy is intentional and creative about tackling the right subset of those needs.
Bad product strategy presents a laundry list of priorities or “strategic goals” that attempt to tackle all customer needs.
Good product strategy is intentional about whether to play head to head against incumbents or to play on a different turf entirely.
Bad product strategy defaults to one of these stances without a rigorous assessment of options and industry trends.
Good product strategy highlights trade-offs and lays out the rationale for said trade-offs.
Bad product strategy eschews trade-offs and tries to be “all things to all people”.
Good product strategy builds upon the company’s existing advantages (companion products, distribution channels, partner relationships, etc.).
Bad product strategy either ignores these advantages or overestimates their potential impact on the product’s success.
Good product strategy increases chances of success by largely relying on the company's long-lasting advantages.
Bad product strategy relies on factors that might be a current source of advantage but are over time more susceptible to getting neutralized by the competition.
Good product strategy meaningfully differentiates the product in the market.
Bad product strategy makes proclamations about wanting to be “the best”, “most delightful”, “world-class” etc. without adequately specifying the concrete product choices that will make it so.
Good product strategy identifies leading and lagging indicators of success, whether they are metrics or milestones.
Bad product strategy either ignores success indicators or misses the leading indicators.
Good product strategy clearly presents its positive effect on the company, in terms of the company metrics impacted and the assets created or amplified.
Bad product strategy doesn’t provide a rigorous point of view on company-level upside.
Good product strategy is cognizant of the importance of execution. It prompts org-wide decisions and action by mapping the proposed product choices to a high-level action plan and associated risks.
Bad product strategy doesn’t map the proposed choices to cohesive actions.
Good product strategy provides company executives with a fresh perspective on the domain and the product.
Bad product strategy attempts to conform to executives’ pre-existing opinions about what should be done with the product.
Good product strategy is inspiring because it’s vivid, rigorous, and actionable.
Bad product strategy tries to sound visionary and ambitious, usually by employing Rah-Rah language and Apple Pie positions. Bad product strategy often reads like a prayer.
Lack of time is a perpetual source of stress in the product manager’s journey.
No matter how well you’ve prioritized, no matter what milestone your product has just reached, there is a near-infinite list of really important things you could be doing that you just cannot do.
There are many well-known resources & principles for managing time: systems such as GTD, “managing your energy, not your time”, prioritization formulas, Eisenhower Matrix, etc.
These are no doubt useful, but for product managers, these systems leave a lot to be desired.
Why do companies with major resources & distribution make products that are mediocre & often fail to reach their potential?
There are a handful of reasons, many of which you already know. But there is one under-discussed reason: Operators Optimizing for Optics
Thread:
To understand this, let’s start with a story.
START OF STORY
Acme Inc has brilliant, visionary founders (Alice & Bob), amazing culture, has built a well-loved product, and thereby created a business much larger than the early people (including the founders) had ever imagined.
With this growth, they’ve had to hire a bunch of Operators: leaders who are skilled in scaling process, teams, operations, and overall execution. So far so good. As the business & the customer-base grows, it is a no-brainer for Acme to tackle adjacent areas of opportunity.
Some reflections since turning on Twitter’s Super Follows two weeks ago.
800+ superfans have joined 🙌🏾
Biggest benefit:
I am tweeting a lot more freely because I know I am speaking to superfans who understand what I am about. More advanced & nuanced content. Fewer unsent drafts
Biggest surprise:
The community aspect of Super Follows has been A+ thus far.
While not a primary goal, it was 1 of my hypotheses for doing Super Follows. And it has vast exceeded everyone’s expectations. I polled folks yesterday for feedback, and community was mentioned by most
Many super followers mentioned that they are now using Twitter more frequently & are replying/sharing a lot more freely with the community than they might in public, because of shared alignment.
One super follower said it best: people writing without fear of being misunderstood
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:
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:
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:
1) Be proactive 2) Begin with the end in mind 3) Put first things first 4) Think win-win 5) First understand, then seek to be understood 6) Teamwork & creative cooperation 7) Continuous improvement
Basically, the habits in the classic book.
I know that many Product Managers will ignore this because they want something more advanced.
They have already read Covey's book at age 23, so there's nothing more & nothing new to learn from it.
They want an edge over others, so they seek & love esoteric advice & tactics.
And yet, 9 out of 10 times when I am working with extremely smart & ambitious PMs who are struggling (not getting promoted, not getting the performance reviews they think they deserve, not executing well, etc.) it is because they have forgotten one (or more) of these 7 habits.