Library / Problem Structuring and Decision Support Principles Framework
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 08:45:20 UTC

PSD.15:4.2 - Recover candidate ways of working and their contribution boundaries

State each serious candidate as a way of doing: its entry conditions, participant meanings, actions, input/result commitments, required joins, allowed variation, and stop. Use A.3.1 for Method identification. Keep an unresolved proposal as a candidate account; an attractive name, complete document or parent Method does not admit it.

When several grounded occurrences or direct sources leave the reusable way genuinely unclear, A.3.1.MR can help recover candidate accounts. It is not the route for filling a missing design choice in a prospective recipe. Ask the designer to state the proposed action and its conditions.

Decompose a heavyweight school or package only far enough to compare contributions. The following contrasts are useful starting questions, not an exhaustive taxonomy or automatic assignment rule.

Recurring difficultyContribution to recoverCondition that must not be silently supplied
Participants formulate different problemsWays to elicit, represent and challenge attributed interpretations; purposeful-activity or concern-mapping contributions where suitable.Attendance or a shared map does not establish equal influence, representation or agreement.
Related decisions cannot be treated independentlyWays to expose connected choice areas, feasible combinations and commitments.A diagram of dependencies does not establish feasibility or authorize commitments.
Values and trade-offs are incompletely statedWays to elicit value judgements and compare alternatives under the admitted preference information.A preference model cannot create legitimate weights or permission to trade a protected condition.
Consequences depend on uncertain conditionsQualified conditional modelling, uncertainty analysis, scenarios, robustness and information-priority work.A scenario is not its probability; one robust region does not cover every model or value scheme.
Analysis does not become usable adviceWays to compose and explain a source-bounded recommendation, dissent, limits and next use.A score or specialist answer is not the whole recommendation or recipient choice.
Advice loses its basis after changeWays to observe decision-significant conditions, interpret evidence and reopen the exact affected result.A signpost, dashboard or missed observation is neither an authorized response nor evidence of no change.

Soft Systems Methodology, SODA/cognitive mapping, Strategic Choice, MCDA, scenario and robust-decision approaches can contribute to different rows under their actual source conditions. A software platform may support several such contributions. None supplies a universal Method merely by appearing in the repertoire.

PSD.6 supplies the engagement-level comparison and combination discipline. Preserve its joins: an attributed concern may become a candidate objective for examination, not automatically a numerical weight; a scenario may constrain a calculation without supplying a probability. If a proposed whole cannot recover its reusable action and joins, retain the bounded candidate or arrangement description rather than calling co-use a composite Method.