product-wisdom

name

product-wisdom

description

Product management frameworks and counterintuitive truths from Lenny's Podcast. Use when helping with product strategy, prioritization, roadmap decisions, feature scoping, team structure, customer discovery, activation metrics, positioning, or when the user is making product decisions that could benefit from battle-tested PM wisdom. Triggers on questions about what to build, how to prioritize, team organization, go-to-market strategy, or product-market fit.

Product Wisdom

Condensed insights from top product leaders. Apply these frameworks when helping with product decisions.

Core Frameworks

Activation: Get Users to Value Fast

The magic moment matters more than features. Find yours:

• Slack: 2,000 messages exchanged = team is hooked
• Gamma: 30 seconds to first presentation = user activated

Apply when: Discussing onboarding, retention, or "users aren't sticking"

Positioning (April Dunford's 5 Steps)

Start with competitive alternatives, not messaging:

1. What would customers use if you didn't exist?
2. What's your unique capability?
3. What value does that capability enable?
4. Who cares most about that value?
5. What market context makes this obvious?

Apply when: Go-to-market, messaging, or "how do we differentiate"

Product Discovery (Teresa Torres + Marty Cagan)

Talk to customers weekly, not quarterly. Use Opportunity Solution Trees:

• Desired outcome → Opportunities → Solutions → Experiments

Validate Four Risks before building:

1. Value risk: Will customers buy/use it?
2. Usability risk: Can they figure it out?
3. Feasibility risk: Can we build it?
4. Viability risk: Does it work for our business?

Apply when: Deciding what to build, validating ideas

Prioritization (Shreyas Doshi's LNO)

Categorize tasks by type, not just impact:

• Leverage: 10x returns, deserves 10x effort
• Neutral: Standard work, standard effort
• Overhead: Minimize time, just get it done

Focus on opportunity cost, not ROI. What are you NOT doing?

Apply when: Roadmap planning, sprint planning, "we can't do everything"

Team Structure

Give teams problems to solve, not features to build. Empowered teams vs. feature factories.

Small teams win: Jason Fried's 2-person/6-week constraints. Shopify's pair programming. Companies produce MORE after layoffs—coordination overhead is the silent killer.

Apply when: Team org, hiring decisions, "we need more people"

Pre-Mortems (Shreyas Doshi)

Before starting: "It's 6 months from now, this failed. Why?" Surface failure modes before they happen.

Apply when: Project kickoffs, high-stakes decisions

Counterintuitive Truths

Apply these when conventional wisdom might mislead:

Conventional Thinking	Reality
More features = more value	Fewer features often wins. Walkman succeeded by REMOVING recording. QuickBooks: half features, double price.
Reduce friction everywhere	Strategic friction can INCREASE conversion. Amplitude added personalization questions, +5% conversion.
Always A/B test	Don't A/B test big bets. Instagram/Airbnb reject testing for transformational changes.
Trust customer requests	"Bitchin' ain't switchin'" — 93% said they wanted energy-efficient homes. Nobody bought them.
OKRs = strategy	Goals are not strategy. Confusing them is the most common strategic error. OKRs are often wish lists.
Data > intuition	Your gut IS data—compressed experiential learning that isn't statistically significant yet.
Fear = danger	Fear gives bad advice. Whatever you're afraid to do is exactly what you should do.
Add people to go faster	Adding people makes you slower. Coordination overhead compounds.

How to Apply

When the user faces a product decision:

1. Identify the decision type — prioritization? positioning? team? validation?
2. Surface the relevant framework — don't lecture, apply it to their context
3. Challenge conventional thinking — if they're following an "obvious" path, check it against counterintuitive truths
4. Ask the uncomfortable question — what are they afraid to do? That's probably the answer.