problem-framing

name	problem-framing
type	workflow
family	workflow
rigor	full
description	Use when beginning analytical or strategic tasks, facing undefined problems, or facing analysis paralysis—requires explicit problem definition before proceeding.
keywords	discovery, problem-definition, root-cause, analysis-gate, requirements, scope
compatibility	Claude Code and compatible agent products
requires	[]
enhances	["competitive-analysis","buyer-persona","business-case","market-context"]
sources_pdf	["The Personal MBA (Kaufman)","Playing to Win (Lafley)","The Design of Everyday Things (Norman)","User Friendly (Kuang)","Designing Your Life (Burnett)","Making Things Happen (Berkun)"]
sources_web	["First Round Review: Design Sprint Discovery"]

Overview

Problem-framing is the "discovery gate" that ensures you are solving the right problem before investing resources in solutions. It uses human-centered design principles and strategic cascades to move from symptoms to root causes.

Iron Law

NO ANALYSIS WITHOUT APPROVED PROBLEM FRAMING FIRST Premature analysis leads to solving the wrong problem, wasting resources on elegant solutions to low-value or non-existent issues.

State Machine

digraph problem_framing_flow {
    "Start" [shape=doublecircle];
    "Step 1: Observe & Gather Context" [shape=box];
    "Step 2: Root Cause Analysis (5 Whys)" [shape=box];
    "Step 3: Reframing & Questioning" [shape=box];
    "Gate: User Approval of Problem Statement" [shape=diamond];
    "Step 4: Define Winning Aspiration" [shape=box];
    "Done: Discovery Gate Passed" [shape=doublecircle];

    "Start" -> "Step 1: Observe & Gather Context";
    "Step 1: Observe & Gather Context" -> "Step 2: Root Cause Analysis (5 Whys)";
    "Step 2: Root Cause Analysis (5 Whys)" -> "Step 3: Reframing & Questioning";
    "Step 3: Reframing & Questioning" -> "Gate: User Approval of Problem Statement";
    "Gate: User Approval of Problem Statement" -> "Step 4: Define Winning Aspiration" [label="approved"];
    "Gate: User Approval of Problem Statement" -> "Step 1: Observe & Gather Context" [label="rejected"];
    "Step 4: Define Winning Aspiration" -> "Done: Discovery Gate Passed";
}

When to Use This Skill

• At the start of any new project, strategy, or analytical task.
• When a project feels "stuck" or directionless.
• When stakeholders have conflicting definitions of success.
• When you find yourself jumping straight to "how" before fully understanding "what" or "why."

When NOT to Use This Skill

• For routine, well-understood tasks with established, validated procedures.
• For trivial tasks where the cost of framing exceeds the potential value (e.g., fixing a typo).
• When the problem has already been rigorously framed and approved in a prior step.

Core Process

Step 1: Observe & Gather Context

• Apply Applied Ethnography: Observe users in their natural environment to understand motives, interests, and true needs. Focus on activities performed rather than just demographics. (Source: Norman, The Design of Everyday Things)
• Describe the Problem: Aim to describe the problem better than anyone else. "Whoever best describes the problem is the one most likely to solve it." (Source: Kaufman, The Personal MBA)
• Gather SPIN Context: (1) Understand the current situation, (2) Identify the perceived problem, (3) Clarify short-term and long-term implications. (Source: Kaufman, The Personal MBA)