pm-thinking

To write a PRD using problem-first framing, describe the user pain in one sentence, then generate the document with measurable outcomes, non-goals, and a release plan to ensure cross-functional alignment.

Problem-first product management prioritizes user pain and measurable outcomes over feature outputs, improving roadmap prioritization by enforcing trade-offs, guardrails, and clear success criteria before design begins.

Set measurable OKRs for product strategy by defining specific user problems, attaching quantifiable outcome metrics, and documenting decision context with explicit non-goals to prevent misaligned work.

Evaluate a new feature before design begins by framing the core problem, specifying success metrics, and deciding what trade-offs to accept using scope-guided decision making and strict guardrails.

The best way to document product decisions for cross-functional teams is to record the problem framing, accepted trade-offs, and outcome goals, ensuring alignment on priorities and strategy.

You should not use problem-first framing when you lack a clearly defined user pain or cannot establish measurable outcomes, as the approach requires explicit constraints and success criteria to function effectively.