Jackie Bavaro on Product Strategy and PM Career

Source: Lenny’s Podcast Speaker: Jackie Bavaro Source URL: https://www.lennysnewsletter.com/p/jackie-bavaro

Key ideas

Strategy = three components: vision (inspiring future picture), strategic framework (market + big bets), and roadmap (feasibility check). Missing any one means the strategy is incomplete — even if it contains the other two.
Good strategy = connecting the dots: from high-level business goal to specific product work, with every intermediate assumption made explicit. Unexplained gaps are missing dots.
The promotion conversation: ask your manager “What should I work on now so I’ll be ready for X when the opportunity comes?” — frames growth as collaborative, targets feedback, and brings the manager onto your side.
PEARL interview framework: Problem → Epiphany → Action → Result → Learning — a richer version of STAR that specifically captures the insight (epiphany) that made the project succeed or fail.
Early PM career: deliver well on the narrow scope you’re given for the first 6 months; don’t reinvent strategy on arrival. Trust is earned through execution, not by critiquing the existing plan.

What is strategy?

Jackie identified the gap after being told she “needed to be more strategic” at Google with no one able to explain what that meant. Later at Asana she refined the definition with head of product Alex Hood:

Three components:

Vision — an inspiring picture of a future state that invites people to join. “Here’s where we want to get to; come build this future with me.” Motivating, directional, inspiring.
Strategic framework — the market analysis and big bets. Who are we going after? What does winning that market require? What are our pillars? This is where you express your unique breakdown of the problem: who the best customers are, what they need, how you’ll win.
Roadmap — a working-backwards feasibility check. If the vision is a 5-year goal, what does that require in years 1–3? Most roadmaps reveal that the vision is actually 30 years away at current velocity — which is actionable information: it forces bigger bets, more resource allocation, or a more modest vision.

Common mistake: treating “increase revenue by 50%” as a strategy. That is a goal, not a strategy. The strategy is the chain of reasoning between that goal and the product choices that will achieve it.

Good strategy vs. bad strategy

A good strategy connects the dots: from the high-level business goal, through the reasoning about why a given approach wins the market, down to the specific product work. Every assumption must be made explicit.

The way to find missing dots: communicate the strategy and watch for confusion. People will try to hide confusion rather than state it directly. The PM must actively solicit “where does this lose you?” and keep re-explaining until no dots are missing.

Recurring disagreements over individual features are almost always strategic disagreements in disguise. Write down the underlying strategic principle and resolve it at that level rather than fighting case by case.

How to get better at strategy

Cross-application: strategy frameworks transfer across domains. Shishir Mehrotra’s “consistency vs. comprehensiveness” framework (from Google Shopping) unlocked the strategic question for YouTube’s external linking debate. Looking at how other products make choices provides new lenses.
Collaboration: real strategy is collaborative. Bring your thinking into conversations with stakeholders; update your views when someone makes a better argument.
Staying long enough to see results: pattern recognition in strategy requires iterating through multiple cycles — trying something, measuring, trying something different, noticing what changed.
First 6 months: spend on customer research and learning the existing strategy, not creating new strategy. “If you don’t believe in my strategy, why did you join my team?”
After 6 months: block half a day, draft whichever strategy component draws you most (vision, framework, or roadmap). Use this as the basis for collaborative work with the product triad.

PM career advice

The promotion conversation

Template: “I would love to become [X] someday. What do you suggest I work on now so I’ll be ready when the opportunity comes?”

Why it works:

Frames the goal as future (not threatening)
Brings manager onto your side (collaborative, not adversarial)
Targets feedback: not all feedback is promotion-critical; this question filters for what matters
At committee-based companies: if your manager is new, find a peer of your manager who has gotten someone promoted and ask the same question

Early career

Work at large or mid-size companies: higher salaries, better mentorship, more structured learning.
Don’t try to redesign everything from scratch. The narrow scoped problem you’ve been given should usually be solved simply and well — that earns trust for bigger scope later.
Common error: wanting to be a people manager immediately while appearing to devalue the day-to-day IC PM work. This signals immaturity and makes the person harder to manage.
Don’t over-insert or under-insert: don’t crowd out teammates, and don’t let a strong designer carry everything while you take notes.

People management

Being a manager is lonelier and less fun than IC work. Team dynamic shifts; harder to be authentic due to confidential personnel information.
Consider it a two-way door: try it; if it doesn’t suit you, go back to IC.
Senior IC compensation at top companies is comparable to doctors and lawyers; people management is not the only path to financial success.

PEARL interview framework

Jackie’s variant on STAR for PM stories:

Letter	Component	What to show
P	Problem	A problem big enough to be worth solving
E	Epiphany	The insight that unlocked the solution — what did you see that others missed?
A	Action	What you actually did; specifics of how you overcame challenges
R	Result	Concrete outcomes; good results or instructive failures
L	Learning	What you took away; what you do differently since

The Epiphany component distinguishes it from STAR: it captures the product thinking, not just the execution sequence.