think-boundary-critique

Boundary Critique

Every problem frame draws a line before any reasoning starts: who counts, what counts, whose improvement is the point, and who is left on the other side of the line. Those prior decisions are boundary judgments, and they condition both the facts you collect and the values you weigh. The reflex is to reason inside the frame as given. Boundary critique refuses that reflex and makes the frame itself the suspect object. It interrogates each boundary judgment in two modes - how the frame currently draws the line (the is mode) and how it ought to (the ought mode) - and forces an explicit account of the parties who have a stake in the consequences but no seat in the frame. The move is the de-branded core of Critical Systems Heuristics (Werner Ulrich, from 1983, later with Martin Reynolds). The output is a boundary-judgment audit, not a discussion.

When to Use

• A plan, metric, proposal, or "solution" already encodes who matters and who does not, and the risk is solving a tidy problem for the people inside the line while externalizing harm onto people outside it.
• An "improvement" claim rests on an unexamined judgment about whose improvement (a growth metric, an efficiency gain, a success measure that quietly picks a beneficiary).
• The situation is contested, value-laden, or multi-party: policy, programme or intervention design, evaluation, or any decision where reasonable parties would draw the boundary differently.
• You suspect a frame is illegitimately bounded - that the affected-but-excluded exist - and want them surfaced before the frame is acted on.

When NOT to Use

• The frame is genuinely settled and uncontested. If the stakeholder set and the success measure are already agreed and legitimate, auditing the boundary manufactures doubt and stalls execution. This is the same failure as reframing a correct problem. This is the central wall.
• The problem is technical or single-party. With one obviously-correct beneficiary and no excluded affected parties, the audit produces empty "ought" columns - ritual, not insight.
• You expect it to resolve the disputed boundary. Boundary critique surfaces and debates the is-vs-ought gap; it does not adjudicate it. It exposes the boundary question and names who is excluded; it does not settle who is right or compel a powerful actor to widen the line. When the gap is real, route the decision onward (e.g. to think-decision-option-review) - the audit informs that choice, it is not the choice.
• You only need to hear the stakeholders. If you just want each in-scope party voiced, that is a stakeholder round-up - use think-parallel-perspectives-review (stakeholder mode) or think-problem-restatement (its stakeholder shift). Boundary critique is the different, upstream move: it takes the stakeholder set itself as suspect and audits inclusion-versus-exclusion in is/ought terms. Run it as a round-up and it collapses into the move the library already ships.