problem-framing-canvas

Guide users through the MITRE Problem Framing Canvas to create problem statements and How Might We questions.

1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/Johnnnmai/100x-product-manager --skill problem-framing-canvas-johnnnmai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: problem-framing-canvas
Source: https://github.com/Johnnnmai/100x-product-manager/tree/main/skills/problem-framing-canvas
Command: npx skills add https://github.com/Johnnnmai/100x-product-manager --skill problem-framing-canvas-johnnnmai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill guides users through a structured process to deeply understand and clearly define problems, preventing the common pitfall of jumping to solutions without fully grasping the root cause or stakeholder needs.

Core Features & Use Cases

  • Structured Problem Exploration: Asks targeted questions across "Look Inward," "Look Outward," and "Reframe" phases.
  • Bias Identification: Helps uncover assumptions and biases that might skew problem definition.
  • Equity-Focused: Explicitly prompts for overlooked stakeholders and beneficiaries.
  • Actionable Output: Generates a refined problem statement and a "How Might We" (HMW) question.
  • Use Case: A product manager suspects a new feature request might be addressing a symptom, not the core problem. They use this Skill to systematically explore the problem space, uncover underlying user needs and biases, and reframe the objective into an actionable HMW statement before ideating solutions.

Quick Start

Use the problem-framing-canvas skill to guide me through framing a new product idea.

Frequently Asked Questions about problem-framing-canvas

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

FAQPage Schema
How do I write a problem statement without jumping to solutions too early?

A problem framing canvas prevents premature solutioning by guiding product managers through targeted phases to explore user needs, identify assumptions, and generate actionable questions before ideation.

What is the best way to uncover bias and assumptions during product discovery?

Uncovering bias during product discovery requires systematically examining stakeholder perspectives and internal assumptions. A structured problem framing framework explicitly prompts you to identify overlooked beneficiaries and mitigate skewed definitions.

How do I turn user needs into actionable How Might We questions?

To turn user needs into How Might We questions, synthesize insights from exploring stakeholder perspectives and underlying assumptions. Reframing the core problem through structured discovery yields actionable HMW statements for product ideation.

Can I use problem framing for validating new feature requests from stakeholders?

Yes, you can use problem framing to validate feature requests by systematically exploring the problem space. It helps determine if a request addresses a symptom or the core problem before committing product development resources.

When should I not use a problem framing canvas?

A problem framing canvas should not be used when the root cause is already definitively understood and stakeholder consensus exists. It adds unnecessary overhead if the problem space requires no further discovery or bias mitigation.