Problem Statement Framework vs User Story Writer

Problem Statement Framework

By Dean Peters (PM)

Frame customer problems with empathy and evidence before jumping to solutions.

User Story Writer

By Dean Peters (PM)

Turn ideas into clear user stories with testable acceptance criteria—no dev work required.

Problem Statement Framework

• Guides you through a five-part narrative: who the user is, what they're trying to do, what's blocking them, why, and how it makes them feel
• Produces a single-sentence problem statement that teams can rally around
• Helps you avoid solution smuggling and ensures you're solving a problem worth solving
• Provides quality checks and examples to validate your problem framing with real users

User Story Writer

• Formats user needs using the industry-standard Mike Cohn template (As a/I want/So that)
• Generates Gherkin-style acceptance criteria that define when the work is done
• Ensures stories focus on user outcomes rather than just features or tasks
• Provides quality checks to catch vague requirements before they reach the dev team
• Includes templates and examples for writing product-ready stories quickly

Reach for Problem Statement Framework when…

• You're kicking off discovery or user research and need to align the team on what problem you're solving
• Stakeholders are pushing for features but no one has articulated the underlying user problem
• You need to pitch why a problem is worth solving to engineering, design, or executives
• You're writing a PRD and want to start with a rock-solid problem definition

Reach for User Story Writer when…

• You're a PM or founder translating customer feedback into development work
• You need to communicate a product requirement clearly to your engineering team
• You're prepping for sprint planning and need properly formatted backlog items
• You want to ensure acceptance criteria are testable before development starts