Problem Scope Reframing Workshop¶
Facilitated process — instantiates Boundary Reframing
A facilitated session that lays the current problem boundary beside a few deliberately different ones, then selects and diagrams the reframed scope the team will act on.
Most reframing conversations stall in one of two ditches: nobody ever names the boundary they are actually using, or the room critiques the boundary forever without ever choosing a new one. The Problem Scope Reframing Workshop exists to do exactly one thing the other mechanisms don't — converge on a decision. It makes the current boundary explicit, generates a small menu of alternative boundaries (expand, contract, shift, split, merge), filters them through a materiality test, and forces the group to select one and draw it. Its output is not a diagnosis and not a finished solution; it is a chosen boundary, rendered as a shared map that everything downstream can hang on. What makes it this mechanism and not a critique is the mandatory act of selection under a facilitator who will not let the session end in "interesting questions."
Example¶
A city public library is losing patrons and the running assumption is a marketing problem: the boundary is the building and its programs, measured by turnstile door-count. A half-day workshop puts that boundary on the wall in one sentence, then generates rivals. Contract it to a two-branch high-use core and close the rest. Expand it to a "community information and access system" that counts wifi sessions, digital-literacy classes, after-school supervision, and homebound delivery. Split it into a physical-space problem and a separate access problem.
Each candidate is run through a materiality filter — would adopting this boundary change the diagnosis or the options? The access-system expansion clearly does: a large share of "patrons" already use the library remotely and never touch a turnstile, so door-count was measuring the wrong system. Adding a café or vending, by contrast, is immaterial and gets cut. The room selects the access-system boundary and diagrams it, naming the new interfaces it exposes — schools, the county social-services desk, the municipal broadband office. The workshop stops there, with a chosen frame and a map. It deliberately does not rewrite the library's success metrics or negotiate who now owns the school interface; it hands that map to the people who will.
How it works¶
- Surface the incumbent boundary in one sentence. Before any reframing, the facilitator writes down the boundary the team is already using — its system, its measured unit, its "out of scope" list — so the reframe is a visible change, not a fresh start.
- Generate rivals from the move menu. Rather than free-associating, participants apply a fixed set of moves — expand, contract, shift symptom→cause, split, merge — to produce three to five concrete alternative boundaries.
- Filter by materiality, not enthusiasm. Each candidate must clear a single test: would adopting it change the diagnosis, the responsibility, or the option set? Candidates that only add scope get pruned.
- Select and draw. The group commits to one boundary and renders it as a map with its new interfaces named. Selection is non-negotiable; a session that ends without a chosen frame has failed.
Tuning parameters¶
- Candidate count — how many rival boundaries to carry into the materiality filter. More surfaces a better frame but risks a room that admires options instead of picking one.
- Expansion vs. contraction bias — whether the move menu is weighted toward including more or toward narrowing. Bias toward expansion when local optimization is hurting the whole; toward contraction when the frame is already too big to act on.
- Materiality strictness — how high the bar is for a candidate to count as changing the decision. Strict keeps the reframe tractable; loose lets in scope that will later have to be pruned.
- Facilitation neutrality — how hard the facilitator suppresses the highest-status voice. Strong neutrality guards against premature lock-in but slows convergence.
- Timebox — a single session forces a decision; a multi-session series produces a better frame at the cost of momentum and the risk of a critique loop.
When it helps, and when it misleads¶
Its strength is that it breaks the "that's out of scope" reflex and ends in a commitment — a named boundary and a map, not another open question. It is the fastest way to turn a diffuse sense that "we're solving the wrong problem" into a concrete, inspectable reframe the rest of the organization can adopt.
Its characteristic failure is that a room converging under time pressure converges on the loudest reframe, not the best one — classic groupthink, where the drive for consensus outruns appraisal of the alternatives.[n1] The near cousin is rhetorical reframing: the group renames the problem, draws a satisfying new map, and changes nothing that anyone is measured on, so the old boundary quietly reasserts itself. The guarding discipline is to require every selected boundary to name at least one downstream thing that must change because of it — a metric, an owner, an interface — and to seat an explicit dissenter whose job is to defend the incumbent frame until it is genuinely beaten.
How it implements the components¶
current_boundary_description— the opening move is literally to write the incumbent boundary on the wall as the before-state the reframe will change.inclusion_exclusion_revision— the selection step is the decision about what moves inside, what stays out, and what becomes an interface.reframed_system_map— the deliverable is the drawn map of the chosen boundary with its new interfaces named.materiality_threshold— the filter that prunes candidate boundaries down to those that actually change the decision.
It does not perform the deep stakeholder_analysis or boundary_critique that reveal hidden exclusions — Boundary Critique Workshop does that — and it stops short of metric_and_accountability_realignment, which Stakeholder-Inclusive Redesign and Total Cost of Ownership Framing carry out.
Related¶
- Instantiates: Boundary Reframing — this is the general engine that produces and commits to a boundary change.
- Consumes: Boundary Critique Workshop when a prior critique has already surfaced what the incumbent boundary hides; the workshop then selects among the exposed options.
- Sibling mechanisms: Stakeholder-Inclusive Redesign · Environmental Impact Scoping · Lifecycle Assessment · Total Cost of Ownership Framing · Whole-System Problem Definition · Boundary Critique Workshop · Red-Team Scoping Review
Editorial Notes¶
Form Classification¶
Form family: Communication, Facilitation & Learning
Rationale: The facilitated session makes the incumbent boundary explicit, generates rival scopes, and builds shared understanding of the scope the team will act on.
Nearest alternative: Decision, Gate & Allocation — The team selects a boundary, but participatory reframing and collective sensemaking are load-bearing.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Engineering & Design
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Deliberately redrawing a problem boundary is a canonical design-thinking and systems-design move.
Related originating lineages:
- Human-Computer Interaction — The human_computer_interaction tradition materially shaped Problem Scope Reframing Workshop through its own practice of interface disclosure, user guidance, interaction design, and cognitive load.
- Organizational & Management Science — The organizational_management tradition materially shaped Problem Scope Reframing Workshop through its own practice of the coordination, governance, learning, and redesign of organized work.
- Systems Thinking & Cybernetics — Problem Scope Reframing Workshop is most plausibly rooted in the systems_cybernetics tradition because its characteristic form depends on feedback, thresholds, dynamic regulation, and whole-system intervention. The assignment tracks that formative lineage, not the many settings in which the mechanism can now be applied.
Review resolution: Light authoritative-source research resolves the primary-origin disagreement in favor of engineering design. NASA Systems Engineering Handbook: Problem Definition and System Boundaries; NASA Systems Engineering Handbook: Design Solution Definition documents the defining practice, history, or theory described in the selected origin rationale. Other domains are retained only where the blind reviews identify material co-development or translation; broad later application is recorded separately as domain_reach=universal, while origin_mode=cross_disciplinary_synthesis describes the relationship among formative lineages.
Attribution caveat: The blind-review boundary with systems cybernetics is substantive: those traditions materially developed, translated, or operationalized part of the mechanism. The cited provenance places its defining lineage in engineering design.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
- NASA Systems Engineering Handbook: Problem Definition and System Boundaries
- NASA Systems Engineering Handbook: Design Solution Definition
Notes¶
[n1] Irving Janis's term for a mode of group decision-making in which the pressure for unanimity overrides realistic appraisal of alternatives, producing confident but poorly examined choices. A neutral facilitator and an assigned dissenter are standard correctives, which is why both appear in the guarding discipline above. ↩