Palace/Workshop

Problem Framing

problem-solvingstrategydiagnosisdecision-making

Problem Framing

Problem framing is the disciplined act of exploring and defining what problem you are actually facing before rushing into solutions.

Core Idea

Many teams are fast at solution generation and weak at diagnosis. Problem framing slows the process down long enough to:

  • generate multiple plausible definitions of the problem
  • inspect root causes rather than surface symptoms
  • understand stakeholder perspectives
  • connect the issue to wider structures, incentives, and culture
  • define the desired future state before picking interventions

The point is not delay for its own sake. The point is to avoid solving the wrong problem with great efficiency.

This is closely related to First Principles Thinking (stripping false assumptions) and Second-Order Thinking (seeing downstream consequences of the chosen frame).

Operational Components

to-solve-a-tough-problem-reframe-it describes a practical sequence:

  1. expand the possible frames
  2. examine root causes
  3. empathize with stakeholders
  4. elevate to the system level
  5. envision the future state and backcast the path

This makes problem framing more than a mindset. It becomes a repeatable team process.

Relationship to Other Concepts

  • first-principles-thinking asks which assumptions should be stripped away
  • second-order-thinking asks what downstream effects a frame or solution will create
  • epistemic-humility asks you to treat first impressions as hypotheses, not truth
  • 5-whys is a sharp tool for the "examine root causes" step — drill from symptom to systemic cause before drafting the problem statement
  • computational-thinking is the downstream counterpart: once the right problem is identified, CT provides the systematic approach for building the solution (decompose → pattern recognize → abstract → algorithmize)

Problem framing sits upstream of all three.

Sources

Also connects to kaizen (continuous reframing) and inversion.