Approaches for making messy, ambiguous, multi-stakeholder problems discussable before trying to optimize or solve them.

Distinctions

Is

  • A family of approaches for situations where the problem definition itself is contested, incomplete, or unstable.
  • A way to move from “everyone sees a different problem” toward a workable shared structure for inquiry and action.
  • Most useful when the challenge is social, political, systemic, or ambiguous rather than merely technical.
  • Focused on framing, surfacing assumptions, mapping stakeholders, clarifying constraints, and identifying plausible interventions.
  • Common in operations research, systems thinking, facilitation, strategy, and organizational change.
  • A precursor to analysis and decision making when premature problem definition would hide the real structure of the situation.
  • It is a category that including a number of approaches

Is Not

  • Not a single method.
  • Not the same as optimization, root cause analysis, or decision analysis, though it may feed them.
  • Not just brainstorming or open-ended discussion without structure.
  • Not a guarantee of consensus. It often reveals legitimate conflict that cannot be “solved away.”
  • Not primarily for problems that are already well-defined, measurable, and agreed upon.

Boundary

Problem Structuring Methods begin where a problem is still being framed and usually end once the situation has been structured well enough to support judgment, choice, experimentation, or design.

  • If the work is mostly about naming stakeholders, reframing the issue, surfacing assumptions, or exploring alternative representations of the situation, it is inside the boundary.
  • If the work is mostly about calculating the optimal answer to a stable, agreed-upon model, it is outside the boundary.
  • If the main bottleneck is ambiguity about goals, boundaries, or causal structure, PSMs fit.
  • If the main bottleneck is execution inside an already-accepted frame, other methods are usually a better fit.

Systems

Relationships

RelationshipConceptRationale
includesDysfunction Mapping
includesFulcrum Mapping
includesSoft Systems Methodology (SSM)
includesStrategic Options Development and Analysis (SODA)
includesForce Mapping

Perspectives

StanceWho (Point)What They See (View)Optimize ForInsightBlind Spots
FacilitatorPerson convening the conversationA messy situation with conflicting stories and no trusted shared frameShared understanding and forward motionThe first job is often to structure the conversation, not solve the issueCan overvalue process at the expense of concrete action
ExecutiveDecision maker under pressureSlow, ambiguous work before any visible solutionSpeed, alignment, reduced uncertaintyGood structuring can prevent expensive misfiresMay see PSMs as delay or intellectual overhead
AnalystResearcher or OR practitionerA pre-modeling phase where assumptions and variables are still unstableBetter models and cleaner decisionsA bad frame makes every later analysis weakerMay drift back into technical abstraction too quickly
StakeholderPerson affected by the systemWhether their lived experience is being represented in the framingFairness, voice, legitimacyThe problem definition already contains powerMay prioritize local experience over system-level tradeoffs
Change agentDesigner of interventionsA way to find leverage without oversimplifying the systemActionable insight and learningBetter framing leads to better experimentsCan rush from structure to intervention before conflict is metabolized