How AI will evolve the PM role
Product conviction anchored in taste and intuition, plus the ability to align and inspire teams, will be the key PM value adds.
Career reflections
As I recently reached a career milestone, several people have asked for advice on building a career at a large tech company. Here are reflections on what helped me along the way.
Why product takes both optimism and paranoia
The best product people wear two hats: the naive optimist, and the paranoid realist.
Communicate without subtext
Say the quiet part out loud, even (especially) when it’s hard. Do so with compassion and an open mind.
How to make good tradeoffs
Tradeoffs are the heart of a good strategy. When evaluating opportunities, high performing teams don’t say “yes” or “no” without due diligence. Nothing is free, yet with enough creativity, nothing is impossible, either.
Extreme Clarity
Good business communication is extremely clear. It needs to be skimmable, clear, precise, and memorable.
There’s no such thing as “above your pay grade”
Internalizing that you should act like an owner and help wherever you can is an empowering perspective. Demonstrating the grit to tackle problems beyond your assigned scope is a path to growth.
Product growth myth busting: Why good growth work can drive product quality
The tension between product growth and quality is common for any team trying to scale usage. But these concepts shouldn’t be misaligned. Good growth work drives product quality, while reasonable definitions of quality should be deferential to metrics.
This note defines what it means to apply a “growth” approach to a product, and ensure it supports quality.
Write for the 30s, 2 mins, and 10 mins+ reader
The objective of business communication is to ensure your audience digests your message. Readers are likely diverse in their interest and investment with your work. So a lesson I’ve internalized: Explicitly structure your communication to support the 30 second, 2 minute, and 10 minute+ reader.
To summarize: Make it easy to skim with tl;drs, bolded key messages, and visuals – but provide depth under the hood, sometimes embedded with links.
Product Strategy Template
Every PM has stared at a blank screen with the intent to write a product strategy. After going through this one too many times, I formalized a template to give myself a head start. I won’t claim it’s especially novel, but here’s the template I use for any strategy, ranging from a specific product concept to a multiyear vision.
Tips for effectively asking for feedback on your work
This note details how to ask for feedback on your work, and shares corresponding tips for feedback givers:
Set the right context by outlining the purpose of the work and its audience
Highlight why this person is giving feedback, such as their expertise or your general reverence for their opinion
Establish feedback expectations by asking for it at the right time, sharing how you want it, and setting a deadline
Define the type of feedback needed, like whether you want approval vs. input, specific advice vs. general reaction, and suggestions on substance vs. form
Build for the future, not the present
Change is the only constant in technology. We need to build products for the world we’re shipping in, not building in. Future-proofing your work requires intention.
Anticipate trends.
Proactively align.
Orient toward the long-term.
Intro to Goal Maps
Goal maps are visualizations of your team's strategy that show how tactics, strategies, metrics, goals, and visions ladder.
These maps facilitate cohesive strategies where everything is connected and build to something great. They're also convenient ways to visualize your entire roadmap.
7 common mistakes in product reviews
Product reviews are a crucial forum, so I wrote out guidance to remind myself for avoiding missteps. The thread between these issues is abdicating ownership.
Not enumerating the meeting goal or type of review.
Skipping the context.
Presenting options without sharing a recommendation.
Obfuscating disagreements.
Only sharing what you think your managers want to hear.
Presenting risks without proposing mitigations.
Forgetting the next steps.
Career tip: Impact and scope are not the same
Perception is: If you are ambitious, you should maximize your scope. Never say no. But this is, at best, short-sighted, and at worst, counter-productive.
Even if you’re laser focused on career growth, scope is not the goal. Impact is.
Product principles should have tradeoffs
Good principles should *not* be self-evident. In fact, the best principles should catalyze debate and disagreement up to the point when the team formalizes alignment. When principles are opinionated, they bring clarity.
Metrics are divine. Metrics are worthless. What’s the truth?
A dominant aspect of product culture is our obsession with and divisiveness around metrics. It’s at once our super-power and our biggest weakness. I’ve observed that individuals, and even full teams, tend to fall into one of two camps:
Metrics are worth everything
Metrics are worth nothing
These views lack nuance. Metrics are at once blunt instruments that must be contextualized and powerful tactics to achieve a goal.