problem-statement

Articulate human-centered problem statements with persona, outcomes, barriers, and constraints.

Updated Aug 18, 2024
One-click install
npx skills add https://github.com/ch-m-n/dotfile --skill problem-statement-ch-m-n
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: problem-statement
Source: https://github.com/ch-m-n/dotfile/tree/main/opencode/skills/problem-statement
Command: npx skills add https://github.com/ch-m-n/dotfile --skill problem-statement-ch-m-n

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents teams from jumping into solutions before they deeply understand who is blocked, what outcome they seek, and why the current experience is unacceptable by guiding them through an empathy-first problem narrative.

Core Features & Use Cases

  • Empathy-first narrative: The provided structure prompts you to describe the persona, desired outcome, barriers, root cause, and emotional impact so stakeholders see the problem through the user’s eyes.
  • Context & constraint capture: Document geographic, technological, time-based, or demographic constraints, ensuring solutions stay grounded in reality.
  • Final statement refinement: Distill the narrative into one concise, empathetic sentence that aligns product, design, and engineering before any solution work begins, such as when preparing discovery artifacts or PRDs.

Quick Start

Fill out the template with a specific persona, the outcomes they care about, the barriers and root causes blocking them, their emotional response, context constraints, and a final single-sentence summary to produce a complete human-centered problem statement.

Frequently Asked Questions about problem-statement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a human-centered problem statement for a PRD?

To write a human-centered problem statement, document the specific persona, their desired outcomes, barriers, root causes, and emotional impact. Refine this empathy-driven narrative into a single concise sentence to align stakeholders before proposing solutions in your PRD.

What is empathy mapping in product discovery?

Empathy mapping in product discovery is structuring a narrative around who is blocked, what they want to achieve, and why the current experience is unacceptable. It captures persona outcomes, barriers, and emotional responses to guide prioritization and PRD framing.

How to align stakeholders before proposing product solutions?

Align stakeholders before proposing solutions by distilling user pain into a single-sentence problem statement. Capture context constraints like geographic or technological limitations to ensure proposed solutions remain grounded in reality and shared understanding.

How do I capture context and constraints for product management discovery?

Capture context and constraints during product management discovery by documenting geographic, technological, time-based, or demographic factors alongside persona barriers. This ensures solutions stay grounded in reality and prevents teams from jumping into unfeasible designs prematurely.

When do I need a problem statement template for user pain?

You need a problem statement template when preparing discovery artifacts or PRDs to prevent jumping into solutions before deeply understanding the user. It is required whenever you need to articulate who is blocked, what outcome they seek, and why the experience matters.

What to include in a problem statement for feature prioritization?

A problem statement for feature prioritization should include persona details, desired outcomes, barriers, root causes, emotional impact, context constraints, and a final single-sentence summary. This empathy-first narrative keeps product, design, and engineering teams aligned.