Intermediate concepts in Product Strategy, page 2
The Feature-Benefit-Value Ladder: Selling Outcomes, Not Specs
The Feature-Benefit-Value Ladder connects product specs to the outcomes customers truly want. It's used to prioritize features and craft messaging that links to core values.
Niche Market Strategy: Big Wins in Small Ponds
A niche strategy means dominating a small, well-defined market instead of fighting for a slice of a large one. It's used by startups to gain a foothold or by large firms launching specialized products. The footgun is picking a niche too small to be profitable.
Customer Lifetime Value (LTV): Predicting Future Customer Profit
LTV predicts the total net profit a customer will generate over their entire relationship with you. It guides how much to spend on acquiring customers (CAC) and helps identify your most valuable segments. The footgun: LTV is profit, not revenue.
AARRR 'Pirate' Metrics: A Funnel for What Really Matters
The AARRR framework is a five-stage funnel (Acquisition, Activation, Retention, Referral, Revenue) that tracks the user journey. It helps product teams focus on metrics that directly impact business health, not vanity metrics like social media likes.
The HEART Framework for Measuring UX
The HEART framework provides a structure for measuring user experience on large-scale web applications. It helps teams define user-centered metrics to track progress towards goals and make data-driven decisions.
Counter Metrics: Guardrails for Your Goals
Counter metrics are the guardrails for your primary goal, preventing you from optimizing one number at the expense of user experience. If you increase ad impressions for revenue, track user retention to ensure you aren't just driving users away with spam.
KPI Tree: Linking Product Changes to Business Outcomes
A KPI tree traces how changes ladder up to outcomes, giving metrics connective tissue. Build one when dashboards and experiments conflict and you need a defensible line from features to impact. Let it stay static and it becomes disconnected.
Thematic Roadmaps: Focus on 'Why,' Not 'What'
A thematic roadmap organizes work around strategic goals ("themes") like "Improve User Onboarding," not just a feature list. It's used to align teams on high-level objectives and persuade executives. The footgun is mistaking a feature list for a strategy.
Outcome-Based Roadmaps: Solve Problems, Not Ship Features
An outcome-based roadmap frames work around problems to solve, not a checklist of features to build. It gives teams autonomy to find the best solution for goals like increasing user engagement or improving conversion.
Roadmap Capacity Planning: Ideal vs. Reality
Capacity planning isn't about your team's ideal output (design capacity), but their actual output (effective capacity) after accounting for meetings, bugs, and on-call. Use it to build realistic roadmaps.
ICE Scoring: Prioritize Features with a Quick Gut Check
ICE scoring is a gut-check for prioritizing features by multiplying Impact, Confidence, and Ease. It helps teams rapidly sort experiments or backlog items. The main footgun is its bias towards easy wins, potentially ignoring high-effort strategic projects.
Buy vs. Build: A Strategic Choice, Not a Cost Problem
The Buy vs. Build decision is a strategic choice, not just a cost problem. Buy commodity functions to gain speed and stability; build core features to create a unique competitive advantage. The footgun is ignoring total cost of ownership and strategic control.
Opportunity Cost: The Value of the Road Not Taken
Opportunity cost is the value of the best alternative you forgo when making a choice. It's used to prioritize projects when resources are scarce, like choosing a new feature over a refactor. The footgun is ignoring non-monetary costs like lost time or utility.
Sales Enablement: Mission Control for Your Sales Team
Sales Enablement is a central nervous system for your sales team, connecting them with the right content, training, and coaching. It's crucial for complex sales cycles, ensuring consistent messaging. The footgun is treating it as just a content library.
Beta Programs: Testing with Real Users Before Launch
A beta program is your final dress rehearsal with a real audience. It's for validating user experience and catching deal-breakers before a public launch, not just finding bugs.
Customer Success Playbooks: Standardize Your Team's Responses
A Customer Success playbook is a recipe for handling key customer moments. It defines a standard workflow for events like onboarding or a drop in usage, ensuring every CSM follows the same proven process. Without them, customer experience is inconsistent.
Rules of Engagement: API Contracts for Teams
Rules of Engagement (RoE) are an API contract for human teams, defining how they interact to prevent chaos. They clarify who owns a customer conversation or how feature requests are handled.
Product Line Strategy: Selling a Family of Products
A product line strategy sells a family of related products individually, not as a bundle. It's used to capture different market segments, like offering 'good, better, best' software tiers or car trims.
Portfolio Roadmap: The Strategy Across Your Products
A portfolio roadmap is the top-line strategy for a group of related products, ensuring they all pull in the same direction. Use it to align multiple product lines with business objectives.
GE-McKinsey Nine-Box Matrix: Portfolio Strategy Beyond the 2x2
The GE-McKinsey matrix plots business units on a 3x3 grid to guide 'invest, hold, or divest' decisions. It's used to prioritize investments by weighing multiple factors for market attractiveness and business strength, not just market share and growth.
We are hiring for this. Every open role lists the topics its interview covers, so you can prepare for the real thing rather than guessing.
See open roles