Product7 min read

Product Management

Define, prioritize, and ship products that solve real problems - balancing user needs, business goals, and technical constraints through structured discovery and delivery.

Product ManagementPRDRoadmapPrioritizationStakeholders

skill: Product Management category: Product tags: [Product Management, PRD, Roadmap, Prioritization, Stakeholders] readingTime: 7

Great product management is 80% problem discovery and 20% solution definition. The #1 PM failure is building features without validated problem-solution fit. Write the press release before the PRD; if you can't excite yourself about the outcome, don't build it.

Workflow

Discover and validate the problemBuilding the wrong product perfectly is worse than building the right product imperfectly. Validate that a real problem exists at meaningful scale before scoping a solution.
Write a product requirements document (PRD)A PRD aligns engineering, design, and business before a line of code is written - preventing the expensive rework that comes from misaligned understanding.
Prioritize with RICE or MoSCoWPrioritization removes opinion from roadmap decisions - frameworks make tradeoffs transparent and defensible to stakeholders.
Build and communicate the roadmapA roadmap communicates intent and sequence, not a fixed schedule. It aligns teams, enables sales to set expectations, and helps engineering plan capacity.
Ship, measure, and iterateShipping is not the finish line - it's the start of learning. Every feature needs a measurement plan before launch.

Output Format

PM deliverables: problem validation, PRD, RICE-prioritized backlog, outcome-based roadmap, and post-launch metrics review.

PRD: problem → objectives → non-goals → stories → requirements → metrics
Roadmap: Now / Next / Later with confidence levels
Prioritization: RICE scores per feature
Metrics: activation rate, feature adoption, retention delta

Examples

Input

Output

Edge Cases & Gotchas

HiPPO-driven roadmaps - When the Highest Paid Person's Opinion overrides prioritization frameworks, PM loses credibility. Counter with data: show the RICE score comparison and user quote evidence for alternatives.
Feature requests from large customers - A single enterprise customer demanding a feature shouldn't override the roadmap unless the problem is widespread. Validate with 3+ other customers before committing.
Scope creep in implementation - Engineering adds features not in the PRD 'while they're there'. Add a scope freeze before each sprint starts and flag any additions as a new PRD item.
Shipping without measurement - Features shipped without metrics can't be evaluated. Always define 'what does success look like?' before engineers start building.

When to Break These Rules

Skip formal PRDs for very small features (< 1 day eng effort) - a detailed Jira ticket with acceptance criteria is sufficient.
Use Shape Up (Basecamp) instead of Agile sprint planning when the team needs longer uninterrupted cycles and less ceremony than weekly sprints.

Reference Files

https://www.intercom.com/blog/product-management-resources/
https://www.producttalk.org/