Open this lesson in your favourite AI. It'll walk you through the why, explain the demo, and quiz you on the try-it list.
There's no single definition, but consistent patterns across great PMs: customer obsession, strong written communication, opinionated about what NOT to build, comfort with ambiguity, technical literacy, ability to align stakeholders without authority. Understanding these helps you know what to build toward.
Patterns of effective PMs.
Use these three in order. Each builds on the one before.
Explain in one paragraph the 8 components of effective PM.
Walk me through what 'customer obsession' looks like in daily practice for a PM.
Given a PM moving from individual contributor to managing 3 PMs, which of the 8 components becomes more critical?
THE COMPONENTS OF GOOD PM:
1. CUSTOMER OBSESSION
Knows customers deeply.
- Talks to them weekly (interviews, calls).
- Watches them use the product (sessions, support tickets).
- Can articulate the JTBD (job to be done) for top personas.
Without this: builds features no one wants.
2. STRONG WRITTEN COMMUNICATION
Writes clearly.
- PRDs that engineers can build to.
- Updates that execs can scan.
- Slack messages that resolve ambiguity.
Without this: misalignment + churn.
3. OPINIONATED — KNOWS WHAT NOT TO BUILD
Has a thesis.
- Says no often. Says no with reasons.
- Defends scope cuts.
- Doesn't ship features because "someone asked."
Without this: feature factory.
4. COMFORT WITH AMBIGUITY
Doesn't need certainty.
- Makes decisions with 70% confidence.
- Adapts when wrong.
- Doesn't freeze when data is missing.
Without this: paralysis.
5. TECHNICAL LITERACY
Understands the stack at high level.
- Knows what's hard vs. easy.
- Can read schemas, dive into logs.
- Doesn't blindly trust engineering estimates.
Doesn't need to code daily, but does need to engage.
6. ALIGNMENT WITHOUT AUTHORITY
Influences without commanding.
- Builds consensus across functions.
- Manages up to exec, sideways to peers, down to team.
- Knows when to escalate vs. when to figure it out.
Without this: politics + frustration.
7. EXECUTION DISCIPLINE
Ships things.
- Manages scope.
- Hits dates (or escalates honestly).
- Doesn't drop balls.
8. STRATEGY
Connects work to the bigger picture.
- Each initiative has a "why."
- Aligns with company strategy.
- Knows what to kill.
ANTI-PATTERNS (signs of bad PM):
- Defers all decisions to engineering or to design.
- PRDs are 30 pages of speculation.
- Backlog has 200 items, all "high priority."
- Doesn't know any customers personally.
- Can't explain why a feature exists.
- Says "we'll figure it out in implementation."
- Treats their team as ticket-takers.
LEVELS OF GOOD:
APM: tactical execution + learning.
PM: owns a surface, ships consistently.
Senior PM: defines strategy for their area.
Staff/Principal: cross-team strategic influence.
GPM/Director: org-wide impact.
VPP/CPO: company-wide strategic ownership.
THIS MODULE'S FOCUS:
Self-assess against the 8 components. What's strong? What's weak?
Pick 2 to invest in.