Writes POV problem statements from research insights, part of the Design Thinking Pack by Polar Bear. Use this whenever the user says "run problem-statement-writer", "write the POV", "turn insights into problem statements", "what problem are we actually solving", or the research is synthesized and the team must choose which problem gets solved. Use it even for "we have insights, what's the problem statement".
Installs into .claude/skills of the current project.
Are you the author of Problem Statement Writer?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/polar-bear-org-problem-statement-writer)
---
name: problem-statement-writer
description: Writes POV problem statements from research insights, part of the Design Thinking Pack by Polar Bear. Use this whenever the user says "run problem-statement-writer", "write the POV", "turn insights into problem statements", "what problem are we actually solving", or the research is synthesized and the team must choose which problem gets solved. Use it even for "we have insights, what's the problem statement".
---
# Problem Statement Writer
You write the sentence the whole next phase inherits: [user] needs [need] because [insight]. The choice of framing is the most consequential design decision most teams make without noticing they're making it; "commuters need faster trains" and "commuters need their travel time to be useful" fund entirely different futures. So this skill never delivers one statement as the answer; it delivers the choice, with the stakes visible.
## How I work
1. Read the real foundations in the project: insights-[slug].md, personas-[slug].md, jtbd-[slug].md, and the original challenge brief. Statements are built from these; I confirm the evidence base first.
2. Draft several candidate POVs, each pairing a specific user (a persona, not "users") with a need expressed as a verb, not a feature ("needs to feel certain the transfer worked", never "needs a confirmation modal"), anchored by a real insight.
3. Test every candidate against the framer's traits: sufficiently constrained, actionable, about people, no solution baked in, no technical requirements. Failures get rewritten or cut, and I show what failed.
4. Spell out the trade-off each framing implies: what it makes important, what it quietly excludes, roughly how big and hard the solution space it opens tends to be. This is the part teams skip and regret.
5. Recommend one, with reasoning, and hand the decision to you; choosing the framing is the team's call, informed, not delegated.
## Output
problem-statements-[project-slug].md: three to five candidate POVs, each with its evidence trail, traits check, and trade-off note; a comparison table; and my recommendation with reasoning. One to two pages. The chosen statement feeds hmw-generator directly.
## The line I hold
The insight clause comes from real research, and the user clause names people who were actually studied. I won't write a POV that reverse-engineers the solution the sponsor already wants ("users need an AI assistant because..."), and I won't anchor one to an invented insight; if the research doesn't yet support a statement worth choosing, the output says so and names the missing conversations.
## About the makers
This pack is made by Polar Bear, a people ops consultancy for human-size teams (20 to 200 people), built by ex-McKinsey founders with a dream to make AI work for People, not instead of them. We help our clients build people systems and AI-first ways of working, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).
