problem-framing-canvas
SolidGuide teams through MITRE's Problem Framing Canvas. Use when you need a clearer problem statement before jumping to solutions.
Install
Quality Score: 86/100
Skill Content
Details
- Author
- deanpeters
- Repository
- deanpeters/Product-Manager-Skills
- Created
- 3 months ago
- Last Updated
- 1 weeks ago
- Language
- Shell
- License
- NOASSERTION
Similar Skills
Semantically similar based on skill content — not just same category
problem-framing
Use when a team is converging on solutions before agreeing on the problem, when a brief reads as a feature request, when symptoms and root needs are tangled, or when assumptions need surfacing before design work proceeds. Do NOT use for code-level bug triage, runtime failure diagnosis, or root-cause analysis of system errors — those are engineering investigation tasks, not design problem framing.
problem-framing
Use when decomposing a vague problem into a structured problem statement, identifying who has the problem and why it matters, sizing the opportunity, mapping constraints, prioritizing across multiple problems, or producing a Problem Definition Document that feeds into Discovery, Competitive Analysis, or Spec Writing. Encodes Problem Definition Canvas, 5 Whys Root Cause, JTBD Problem Framing, Opportunity Sizing, Problem-Solution Fit Assessment, Constraint Mapping, Stakeholder Impact Matrix, and ICE/RICE Prioritization.
recommendation-canvas
Evaluate an AI product idea across outcomes, hypotheses, risks, and positioning. Use when deciding whether an AI solution deserves investment or recommendation.
ai-product-canvas
Structure AI and ML product decisions with the rigour of any product decision. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Produces a complete AI product canvas covering problem definition, model approach, data requirements, evaluation framework, UX design, responsible AI checklist, and launch monitoring plan.
problem-framing-audit
Step-back protocol — restate, generalise, specialise, invert, ask why, pre-mortem, check stakeholders, and audit framings before solving