problem-framing-canvas

Frame problems using the MITRE Problem Framing Canvas to produce a How Might We statement.

6.4k|767|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/deanpeters/Product-Manager-Skills --skill problem-framing-canvas
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: problem-framing-canvas
Source: https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/problem-framing-canvas
Command: npx skills add https://github.com/deanpeters/Product-Manager-Skills --skill problem-framing-canvas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps PMs frame complex problems clearly using the MITRE Problem Framing Canvas, ensuring teams start with a bias-aware, stakeholder-informed problem statement.

Core Features & Use Cases

  • Three-phase workflow: Look Inward, Look Outward, and Reframe guide structured problem exploration.
  • Bias and stakeholder surface: Structured prompts surface assumptions, conflicting perspectives, and who is affected.
  • Actionable outputs: Produces a refined problem statement and a How Might We (HMW) prompt to frame ideation and prioritization.
  • Use case: At project kickoff, run the canvas with cross-functional teams to align on the problem before proposing solutions.

Quick Start

  • Gather context about the problem and stakeholders.
  • Answer Phase 1 questions (Look Inward) to surface biases and initial framing.
  • Proceed to Phase 2 (Look Outward) to map who experiences the problem and who benefits or is left out.
  • Complete Phase 3 (Reframe) to restate the problem and craft a clear How Might We statement.

Frequently Asked Questions about problem-framing-canvas

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

FAQPage Schema
What is problem framing and why does it matter for product discovery?▼

Problem framing is the process of defining a complex issue clearly before ideation. It matters because surfacing biases and stakeholder perspectives early ensures teams align on the actual problem, preventing misguided solutions during product discovery.

How do I use the MITRE Problem Framing Canvas to align stakeholders?▼

To use the MITRE Problem Framing Canvas, guide cross-functional teams through three phases: Look Inward to surface biases, Look Outward to map stakeholder perspectives, and Reframe to produce an aligned problem statement.

How do I write a How Might We statement from a complex problem?▼

You write a How Might We statement by first gathering stakeholder context, surfacing assumptions, and mapping who is affected by the problem. The Reframe phase synthesizes this input into a concise HMW prompt for ideation.

Can I run a problem framing session without technical data or integrations?▼

Yes, you can run a problem framing session without technical integrations. The process requires only conceptual input about the problem space and stakeholders to generate a refined problem statement ready for ideation.

What is the best way to restate a problem before proposing solutions?▼

The best way to restate a problem is using a structured three-phase canvas workflow. This approach forces teams to examine internal biases and external stakeholder impacts before finalizing a clear problem restatement.

When should I avoid using a problem framing canvas?▼

You should avoid using a problem framing canvas for simple, well-defined issues that already have clear solutions. It is specifically designed for complex, ambiguous problems where stakeholder alignment and bias awareness are necessary.