problem-framing-canvas

Start by gathering problem and stakeholder context, then answer eight structured questions across three phases: Look Inward, Look Outward, and Reframe. The skill offers enumerated answer options at each step and outputs a completed markdown canvas with a How Might We statement.

Problem framing defines and challenges the problem itself before any solutions are proposed, examining assumptions, affected stakeholders, and root causes. Solution brainstorming comes afterward and uses the reframed problem statement and How Might We question as its starting point.

Skip it when the problem is already well-understood and validated, for tactical bug fixes or technical debt, or when stakeholders have already committed to a solution. In those cases, address alignment or move directly to solution exploration.

Use the format "How might we [action] as we aim to [objective]?" and keep it broad enough to allow multiple solutions. Avoid narrowing to a single idea like "add a mobile app"; instead frame the underlying user need and target outcome.

It is possible but discouraged, since solo completion lets biases persist and keeps marginalized voices excluded. The canvas works best as a facilitated workshop with a cross-functional team and customer input.