Part II — Models, Methods and Facilitated Inquiry

PSD.5 - Construct Complementary Situation and Option Models

Type: DPF pattern body Status: Candidate

Primary working result: a multi-model decision account: the smallest useful set of situation and option models, the questions each answers, their correspondences and limits, and the claims or unresolved questions that a named receiving inquiry may use.

PSD.5:1 - Problem frame

Use this when one diagram, spreadsheet, simulation, or agreed story is being asked to explain a contested situation, represent everyone’s concerns, predict consequences, and identify the best intervention. Also use it when several models exist but their different subjects, assumptions, or meanings make their combined result unclear.

Start with the question that could change the next decision-support move. Choose a model that can answer it, then add another only for a material question the first cannot answer. The gain is a usable account of complementary and conflicting findings, not a larger model collection.

The governed object is that bounded account of model contributions. A model makes selected claims about a subject; a diagram, table, or screen expresses some model content; the people, pumps, service arrangements, and possible changes being considered remain the subjects. The account connects these without making them one object.

Do not use this pattern when one already-qualified calculation or model answers the entire receiving question and no material contrast remains. Use the direct modeling, engineering, scientific, or evidence practice for its own validity question. Return to problem formulation or boundary work when the difficulty is that nobody can say what the models should help decide.

PSD.5:2 - Problem

A capacity calculation cannot show whose service standard should govern. A rich picture can reveal attributed concerns without estimating a failure probability. A scenario can expose a vulnerable condition without predicting how often it will occur. Treating any one of these as a complete account hides questions it was never built to answer.

Adding models does not automatically repair the loss. Two models may reuse the same data, employ incompatible units or populations, or label different quantities “risk”. Agreement can be duplicated error; disagreement can reflect different questions rather than a defect. A composite dashboard can conceal both.

PSD.5:3 - Forces

PSD.5:4 - Solution

Build a question-led set of complementary models. For each, state its subject, intended use, assumptions, evidence, and what it omits. Compare only the overlapping claims whose meanings can be aligned, retain material differences, and return the usable claims together with their limits.

PSD.5:4.1 - Recover the questions and current boundary

Use the plural formulation set from PSD.3 where its differences identify claims or intervention logics that models must discriminate. A formulation is an interpretation of the problem, not already a validated model of the situation. Use the PSD.4 scope and reopen basis for the same subject, receiving decision, operating conditions, and horizon.

These are conditional inputs, not compulsory earlier stages. A qualified direct source may supply the needed formulation or scope. If a needed result is unavailable, stale, outside the present use, or incompatible, return its exact missing premise or narrow the inquiry; do not infer it from the presence of another model.

Turn the live differences into questions, such as “Does this arrangement retain service when road access is lost?” and “Whose loss is omitted by the aggregate service measure?” Keep question, assumed condition, and proposed intervention separate.

PSD.5:4.2 - Choose complementary contributions at the needed grain

Consider what each model can actually contribute before selecting a notation or tool.

Select the smallest set that covers the material questions. A qualitative model may reveal a question worth quantifying; a numerical model may reveal a missing qualitative distinction. Neither direction is a universal order. Drop a model that supplies no distinct contribution unless its independently grounded evidence is needed to challenge another.

A concern map can already complete the task of making participants’ concerns discussable. When another material question asks what causes an outcome or what an intervention would change, use an adequate causal model directly. If the causal relations still need to be constructed or compared, C.28.CM helps turn the relevant subject knowledge and mechanism accounts into explicit models for that question. Return their assumptions, conditional consequences and unresolved alternatives to the combined account. Keep each existing model for the question it can answer; the constructed causal model still needs the claim-specific assurance in :4.5.

When the question concerns participants’ intentions, their dependence on one another and possible alternatives, the Reference’s goals-and-dependencies walkthrough develops an actors-and-goals model from a service difficulty. It explains how to select what a view reveals, turn a question into analysis assumptions, interpret the answer and return to an omitted assignment when the result exposes a conflict. Use that connected account when these joins need explanation; a sufficient existing model can be used directly.

PSD.5:4.3 - Make each model’s use intelligible

A reader should be able to say: “This model concerns this subject, answers this question under these conditions, and supports this limited use.” Supply the assumptions, evidence source and interval, important omissions, and an observation that would invalidate or narrow that use. Identify the exact model content or edition when a changed value could alter the result.

For a mathematical formalism, simulation, or learned representation, apply C.29 when the choice of mathematical object, mapping, preserved structure, or information loss changes the claim. For example, a road graph can preserve routes and travel-time assumptions while omitting residents’ access rights and the reliability of an untested deployment procedure. C.29 does not establish those omitted facts.

Ordinary local meaning needs only the relevant meaning, units, scope, or evidence statement. Use A.1.1 when the decision needs to establish whether a model applies to a stated subject within a stated claim scope, whether an assignment holder actually uses the model during Work concerning that subject, or whether fixed model and expression contents satisfy a declared coherence criterion under a comparison scheme. Select its broader bounded model-use structure only when the organization of those relations changes the receiving decision. Neither a model collection nor the word “context” supplies that structure.

PSD.5:4.4 - Reconcile overlaps without forcing one model

For each overlap that matters, compare the subject and configuration, population, time horizon, units, definitions, assumptions, and evidence dependencies. Establish whether the models concern the same object or different related objects before treating them as views of one thing. For example, a travel-expense model and a repair-performance model can concern different work commonly called a business trip; matching that label does not equate their completion conditions. State an actual correspondence only as far as the objects and meanings support it. If “service failure” means lost pumping capacity in one model and inability to reach a refuge in another, keep the meanings distinct and ask whether a further relation can be established.

Classify a consequential mismatch before repairing it: different questions, different assumptions, incompatible meanings, contradicted evidence, or a genuine unresolved conflict. Correct a unit or input error locally. Retain alternative assumptions when their truth is not known. When the conflict can reverse the receiving result, compare an obtainable direct investigation with retaining the qualified alternatives or narrower answer through C.11.DUA. Use A.15.9 for a selected outside-practice contribution, including its whole acquisition burden.

Do not average unlike outputs, infer a shared probability from scenario counts, or count models drawing on one dataset as independent confirmation. A combined explanation may show how models inform one another without claiming that they form one unified model.

PSD.5:4.5 - Match assurance to the claim being used

Recognition can begin with a sketch and a plausible contrast. Before consequential reliance, inspect the claims that bear the result: source qualification, implementation or calculation correctness, fitness to the intended use, validation evidence, sensitivity, and extrapolation limits as applicable. The direct domain practice determines what is sufficient; this pattern supplies no universal validation threshold.

Separate confidence in the modeler, internal consistency, empirical adequacy, robustness to assumptions, and authority to decide. A stakeholder’s confidence can affect whether a model is used, but cannot substitute for evidence. A model that cannot yet support a recommendation may still support the narrower result “this conclusion depends on an unresolved assumption”. That limit does not itself select a test.

Return a qualified claim, a narrowed use, or an explicit inability to discriminate; include an evidence request when its contribution warrants acquisition. Where an unresolved safety, rights, legal, or technical premise blocks the proposed reliance, retain that stop. A stronger use needs its direct competent result; obtaining it remains a separate feasible and worthwhile continuation.

PSD.5:4.6 - Return the account and its reopen basis

Keep enough content for the recipient to recover:

• the subject, question, receiving use, configuration, and horizon;
• each selected model’s distinct contribution, current content, source basis, assumptions, and losses;
• the material correspondences, conflicts, and shared evidence dependencies;
• what the account supports, what remains hypothetical or unknown, and which alternatives or claims it can discriminate; and
• the observation that would reopen a model, its connection to another, the problem formulation, or the boundary.

This can be a short annotated comparison; it need not be a new repository or universal record form. If no model combination answers the question, say so. A missing direct result is more useful than a polished but unsupported combined answer.

The same account may inform Method selection, alternative generation, uncertainty treatment, or conflicts between simultaneous inquiries. Each recipient takes only the current, compatible contribution it needs; the account does not complete those later judgements.

PSD.5:4.7 - What changes in practice

Instead of asking which model is “the right one”, the practitioner asks which claims need a model, what each selected model contributes, and which difference would change the next move. Models can remain usefully plural while their overlaps and limits are explicit.

PSD.5:5 - Archetypal Grounding

PSD.5:5.1 - Flood-pump models that answer different questions

In this illustrative continuation of the flood-pump inquiry, the board needs a pre-season decision-support return about permanent pumps, mobile capacity, maintenance, staffing, and access. The current formulations distinguish capacity shortage, deployment reliability, unequal service, and transferred downstream consequences. The scope includes the next flood season and preserves relocation rights and long-term watershed change as material exclusions.

The inquiry team constructs the following bounded account. The values are illustrative case premises, not engineering advice.

The account returns: “Nominal capacity is not presently the discriminating uncertainty. The mobile branch depends on an unqualified access premise. The service comparison must retain both property protection and reachable assistance.” It does not rank the branches.

If verified access evidence closes the transport gap, only the affected model claim and its dependent uses reopen. If no feasible pump branch supports the service concern, the problem boundary reopens. Repeated use of the same inflow dataset by both technical models supplies one evidence dependency, not two confirmations.

Suppose the board additionally asks whether securing an alternative road would get mobile pumps operating sooner during a main-road closure. Two mechanisms remain plausible: road access delays an otherwise ready crew and pump, or the flood also disables power at the staging site, preventing pump preparation even with another road. Use the causal-construction branch in :4.2 to compare road availability, pump-and-crew readiness and time to operation under the same assumed flood conditions. In the first account a usable alternative road removes the named access delay; in the second, preparation remains a limiting condition. These are conditional consequences of the proposed mechanisms. The scenario provides no evidence to choose between them or assert an arrival time.

Return the narrowed answer: another road could remove the access delay, while pump preparation remains a premise that can change its practical benefit. An operations result about readiness and the alternative route could resolve that distinction; :4.4 governs whether obtaining it is worthwhile. The residents’ two service meanings remain as stated in the concern map.

PSD.5:5.2 - Development advice across two holders

An adviser compares a training direction for two service teams. A skills map suggests similar learning needs, but each team’s queue model uses its own demand and staffing evidence. The combined account keeps those holders separate: an improvement simulated for Team A supplies no performance claim for Team B.

For Team B, retain the plausible training direction with its unknown demand and performance contribution; Team A’s benefit estimate does not transfer. A trial is a further choice whose attainable contribution must warrant its burden. More detailed modeling of Team A would not repair the absent Team B evidence.

PSD.5:5.3 - Cheap non-use

A technician needs one conversion under an already-qualified formula, with agreed units and no material uncertainty about applicability. Use that calculation directly. A rich picture, scenario set, and second model would add no discriminating result.

PSD.5:6 - Bias-Annotation

Scope: models supporting bounded problem-structuring and decision-support questions. Lenses: Onto/Epist separates subject, model, expression, and evidence; Prag selects useful discrimination; Arch exposes model connections; Gov preserves later choice and direct authority; Did makes different model contributions readable.

Model-prestige bias favors the most technical representation. Agreement bias counts correlated outputs as corroboration. Model-availability bias turns measurable variables into the whole problem. Counter these by naming each model’s question, inspecting shared assumptions and evidence, and keeping material unmodeled concerns visible. Plurality itself can become a bias: remove a redundant model when it changes no claim or assurance need.

PSD.5:7 - Conformance Checklist

• The account serves a named subject, question, receiving use, configuration, and horizon.
• Needed formulation and scope inputs are current and compatible, or their exact gaps are returned.
• Each model supplies a distinct useful contribution; one sufficient model remains a valid cheaper exit.
• The subject, model content, expression, evidence, and possible intervention remain distinguishable.
• Assumptions, important losses, and limits accompany every relied-on output.
• Material overlaps are compared by meaning, scope, units, and evidence dependency; unresolved differences are not averaged away.
• Mathematical-lens and actual model-use claims receive their direct treatment only when needed.
• Recognition, validation, confidence, causal evidence, and authority are not substituted for one another.
• The returned account identifies usable claims, unresolved discriminating questions, and local reopen conditions.

PSD.5:8 - Common Anti-Patterns and How to Avoid Them

PSD.5:9 - Consequences

The recipient sees which model can answer which question and where the combined account stops. Contradictions can guide inquiry instead of being hidden by one score. The cost is explicit assumptions and correspondence work; limit that work to overlaps that could alter the result. A smaller qualified answer may replace an apparently comprehensive conclusion.

PSD.5:10 - Rationale

Complementarity is a relation between useful contributions to a question, not a model count. Purpose-led selection and explicit loss preserve different interpretations while making technical claims inspectable. Separate assurance keeps a useful representation from becoming unearned evidence about the world.

PSD.5:11 - SoTA-Echoing

PSD.5:12 - Relations

• PSD.3 supplies formulations only where their differences guide model discrimination. PSD.4 supplies the scope and reopen basis for the same subject and decision. Missing needed values require qualified direct sources or an exact gap.
• PSD.6, PSD.8, and PSD.16 may use the model account to discriminate their Method, alternative, or simultaneous-inquiry claims. Representation does not make the represented condition obtain.
• PSD.10 may use the account’s evidence only for the same configuration and horizon; that evidence neither entails its uncertainty judgement nor authorizes action.
• C.29 governs load-bearing mathematical-lens use. A.1.1 governs claims about a model’s applicability, its actual use in assigned Work, and the coherence of fixed model and expression contents under a declared criterion and comparison scheme. Direct scientific, engineering, causal, and evidence practices retain their own truth and adequacy questions.
• C.28.CM supplies causal construction when the needed relations are missing. Its conditional models join the account at :4.2–4.3; their causal support remains a separate question under C.28 and :4.5.
• Value treatment and comparison remain separate from constructing models. A model can expose a value conflict without settling it, and the later choice remains with its authorized owner.

PSD.5:End

PSD.6 - Select Problem-Structuring Methods and Combine Them When Needed

Type: DPF pattern body Status: Candidate

Primary working result: an engagement Method and limits: the selected reusable way of conducting the bounded inquiry, why its contributions fit the required result, how any combined Methods connect, and the conditions under which the selection must change or stop.

PSD.6:1 - Problem frame

Use this when a favorite workshop recipe, analytical technique, or problem-structuring method is being proposed before anyone has tested whether it can produce the needed result with these participants, uncertainties, conflicts, and resources. Also use it when several useful Methods are available but their combination has no clear contribution or usable join.

Start by naming the result the engagement is missing. Compare the simplest sufficient Method with a serious alternative, including a bounded combination when one Method cannot supply the needed contributions. The practical gain is a defensible way of proceeding, with visible limits and a cheaper exit when elaborate facilitation adds no value.

A Method (U.Method) is a reusable way of doing under stated applicability, participant meanings, preconditions, intended effects, and bounds. The governed question here is which such way fits this decision-support engagement and whether a proposed combination is coherent. A document describes it, a plan schedules intended work, and people enact it in actual work; none of those is the Method merely by appearance.

Do not use this pattern to select software by feature count, establish that a named person is competent or authorized, or schedule an already-selected Method. If one direct calculation or an existing sufficient Method closes the question, use it. If the missing result is the engagement’s purpose or scope, return that question before choosing a workshop.

PSD.6:2 - Problem

A popular method can be well described and still be wrong for the current inquiry. It may require participation that cannot be obtained, assume a shared purpose that is disputed, depend on data that do not exist, or produce agreement when the recipient actually needs competing claims and discriminating evidence.

Combining methods creates further risks. A concern map becomes numerical weights without an elicitation basis. A scenario becomes a probability distribution. Two workshops duplicate the same task while an essential technical question remains unanswered. A schedule of activities is called an integrated Method even though no one can explain what connects its results.

PSD.6:3 - Forces

PSD.6:4 - Solution

Select by needed contribution and actual applicability, not by a school name or workshop format. Recover what each candidate Method does, compare alternatives at comparable effort, and justify every combination through the meaning of its inputs, outputs, and conditions.

PSD.6:4.1 - State the required result and selection conditions

Use the PSD.4 scope for the same subject and receiving decision when it constrains the selection. Use a PSD.5 model account only where its models, limits, or conflicts can discriminate candidate Methods. Neither input creates a mandatory sequence.

Recover the current facts that can change Method fit: whether the difficulty concerns interpretation, evidence, interconnected choices, values, or action; who can participate and through which channels; what disagreement must remain visible; the available expertise and data; and the time and resource boundary. Obtain consequential participation, competence, safety, and authority premises from qualified direct sources.

A source is useful only for its named subject, condition, and evidence window. If a required scope, model, or participation premise is missing or incompatible, state the exact gap, select a narrower use if defensible, or stop. Do not treat availability of a MethodDescription as evidence that the Method fits.

PSD.6:4.2 - Recover candidate Methods as ways of doing

For each serious candidate, describe the action in plain language: what participants do, with what accepted inputs, to produce which result under which conditions. When the proposed reusable way is already recoverable, use A.3.1 to identify it.

Use A.3.1.MR only when several grounded occurrences or direct sources create a candidate-recovery question about what reusable way the material may show, and no Method has yet been established. It returns provisional source-traceable candidate accounts, a distinguishing question, or an honest lower result; Method identification remains a separate A.3.1 question.

If the way is known and only its wording is unclear, clarify the statement; use E.10 only if an FPF kind or relation question remains. If a prospective recipe lacks a decision about its intended action or applicability, return that missing design question to the person designing the engagement Method. A missing design choice is not by itself a reason to reconstruct past practice.

For a concrete contrast, three grounded inquiry accounts may leave two explanations plausible: a fixed question sequence with local exceptions, or a reusable rule that changes questions when a concern is challenged. That is a candidate-recovery question for A.3.1.MR. A new proposal saying only “interview residents” leaves its intended return and conditions unstated: ask its author to make those design choices, without inventing earlier inquiries. Once the proposed way is sufficiently stated, apply A.3.1 without requiring such a history.

For example, an attributed-mapping Method elicits a participant’s claims, explores their implied connections, checks the rendering with that participant, and retains unresolved differences. A conditional-analysis Method evaluates named alternatives under stated conditions with qualified models and returns consequences and limits. Their labels are insufficient; their actual contributions and applicability make comparison possible.

A source description can explain a Method without demonstrating its effectiveness in this engagement. Keep instructions, reported applications, direct comparative evidence, and practitioner competence distinct. A document about several Methods is not automatically a U.MethodDescription of one composite Method; A.3.2 governs that membership.

PSD.6:4.3 - Compare the simplest sufficient candidate with a real alternative

Choose the comparison dimensions from the required result. The following questions are often decisive:

• Does the Method reveal the material interpretations, or does it require agreement that is absent?
• Can it use the available evidence without manufacturing precision?
• Can affected participants meaningfully contribute or challenge the result through available channels?
• Does it produce the kind of result the next inquiry needs?
• Can the needed expertise, time, and resources be provided?
• What important limitation or failure would remain?

Compare a single sufficient Method, the plausible incumbent, and a bounded combination only when each is a live alternative. Do not turn every engagement into a survey of all PSM families. State the trade-off if a richer result costs more preparation or excludes a faster route. Method popularity, a successful workshop elsewhere, and participant satisfaction do not establish comparative fit here.

If the necessary premise cannot be tested before the receiving decision, select a qualified provisional use or return the limitation. A declared gap is not a low score to be averaged away.

PSD.6:4.4 - Combine contributions through explicit joins

Combine only when the second Method contributes something material the first cannot provide at acceptable effort. Name the result or preserved condition passed between them, its meaning, the receiving precondition, and what happens when the join fails.

An attributed concern map can supply candidate objectives for examination. It cannot supply legitimate numerical weights without the separate elicitation and value assumptions those weights require. A qualitative scenario can supply a condition for technical analysis, not its probability. Keep such conversions as explicit additional work or leave the outputs uncombined.

Recover order from dependence. An analysis may need a specific formulation before it can run, while participation inquiry and technical evidence collection can proceed concurrently once their common question is clear. Their later join still needs compatible subject, conditions, meanings, and limits. Document order, calendar order, and simultaneous use do not establish Method composition.

When the engagement needs one composite U.Method, first identify the whole under A.3.1, then use B.1.5 to qualify its independently identified part Methods and whole-forming claims. State the whole action, applicability, accepted inputs, result, required joins, allowed variations, exposed interactions, and failure or stop conditions. A different part, ordering, or interface outside the permitted variations can identify another Method.

If several Methods are merely coordinated without a recoverable whole, return that bounded arrangement honestly. It may be useful interim planning content, but it is not yet the promised engagement Method. Name the missing whole-action or join question rather than relabeling the activity list.

PSD.6:4.5 - Assess the fragile premise and retain a stop

Examine the assumption most likely to make the selected way unusable: for example, whether a participant can challenge an attributed statement, whether a model accepts the needed scenario, or whether two outputs mean the same thing. Use present support to select a qualified Method or narrow its promised result. When a rehearsal, direct evidence check, or bounded trial could improve that selection, apply C.11.DUA to its obtainable contribution and full cost, delay, access, and burden before commissioning it; A.15.9 governs an outside-practice request.

State what the trial can establish. A successful rehearsal may show that the contribution can be produced under those conditions; it does not demonstrate universal effectiveness or later implementation success. If a required participant, expertise, safeguard, or evidence input is unavailable, adapt the Method within its admitted variation, choose another, narrow the result, or return a blocker.

Continue only while the selected Method can produce its declared result without concealing the unresolved premise. A deadline may justify a narrower return; it does not justify claiming that an omitted contribution was completed.

PSD.6:4.6 - Return the selected Method and limits

Keep dated assignments and scheduling in the work plan. Record actual enactment and its results separately. A selected Method is neither a commitment by absent participants nor proof that anyone has enacted it.

Supply this result to facilitated inquiry or the reconciliation of simultaneous engagements only where the same situation and qualification window fit. A receiving practitioner still checks the current conditions; Method availability is not fit, enactment, or cultural uptake.

PSD.6:4.7 - What changes in practice

The practitioner can explain why this way of working fits, which simpler alternative was considered, and where the arrangement would fail. Adaptation becomes a reasoned change of action and conditions instead of an unexamined mixture of workshop exercises.

PSD.6:5 - Archetypal Grounding

PSD.6:5.1 - Choosing a bounded flood-pump inquiry Method

In this illustrative case, the board needs a pre-season return while service meanings remain contested and the mobile-pump branch depends on unqualified road-access evidence. The current scope and model account make two contributions material: recovering attributed service claims and testing the conditional technical premise.

The author of the engagement design compares three plausible ways:

The proposed reusable whole is: for a bounded intervention inquiry with contested service meanings and conditional technical feasibility, contrast attributed service claims with qualified conditional consequences, resolve only the joins needed for the receiving question, and return shared findings and unresolved contrasts without choosing the investment.

The mapping part elicits, connects, and confirms attributed claims. The analysis part tests named configurations and conditions and reports supported consequences or exact gaps. They can proceed in parallel after the subject and conditions are fixed. Their join accepts only outputs concerning the same intervention, service meaning, and horizon; an unmatched service claim is retained as an unresolved question, not converted to a technical metric.

The whole admits written or spoken elicitation when attribution and challenge remain possible. It does not admit replacing participant confirmation with the sponsor’s paraphrase. Its externally usable result is the bounded claim account; internal map-editing steps are not separately promised services. Those action, join, variation, and boundary conditions identify the proposed composite Method for the A.3.1 and B.1.5 questions.

For actual use of this combination, participation must permit attribution and challenge. Without qualified access evidence, the return remains a conditional technical claim. A direct access inquiry is worthwhile when an obtainable result can change the pre-season decision enough to warrant its burden; otherwise the conditional claim completes this return. The plan’s date and assigned analyst are separate from the reusable Method.

PSD.6:5.2 - A failed join rather than a failed workshop

A team proposes transferring the frequency of concerns mentioned in interviews into numerical criteria weights. The mapping Method yields attributed concerns, not preferences under a weighting model. The join fails even if the interviews were well facilitated.

The practitioner either obtains a separately justified elicitation Method and tests its assumptions or keeps the value contrast qualitative. The failed conversion does not invalidate the interviews or authorize invented weights.

PSD.6:5.3 - Cheap non-use

An operations team has an agreed question, a current qualified calculation Method, sufficient evidence, and no material participation or interpretation conflict. Use that Method. A new multimethod arrangement adds cost without changing the required result.

PSD.6:6 - Bias-Annotation

Scope: selection and bounded composition of Methods for problem structuring and decision support. Lenses: Prag tests fitness and effort; Onto/Epist separates Method, description, plan, enactment, and evidence; Arch exposes real joins; Gov preserves participation and authority conditions; Did makes the reusable action explicit.

Facilitator-familiarity bias favors the method the team can already run. Brand bias mistakes a school name for an identified way of doing. Integration bias treats more techniques as broader competence. Time-pressure bias hides omitted contributions. Counter these with one serious simpler alternative, a result-based contribution comparison, and the exact fragile premise that could reverse selection.

PSD.6:7 - Conformance Checklist

• The selection names the missing result and current subject, scope, conditions, and receiving use.
• Needed model, participation, expertise, and authority premises are qualified or explicitly missing.
• Candidate Methods are recoverable reusable ways, not merely titles, descriptions, plans, or reported workshops.
• A serious simpler alternative and the selected trade-off are explicit.
• Each additional Method supplies a distinct material contribution.
• Passed results preserve meaning, scope, and limits; conversions requiring new evidence are not hidden.
• Real dependence and possible overlap are distinguished from document and calendar order.
• Any composite-Method claim satisfies the direct whole and part questions; a mere arrangement remains an honest lower result.
• Fragile premises, allowed variation, failure routes, and local reopen conditions are stated.
• The result establishes neither actual enactment, participant commitment, effectiveness, nor later choice authority.

PSD.6:8 - Common Anti-Patterns and How to Avoid Them

PSD.6:9 - Consequences

Selection becomes inspectable and adaptations become easier to challenge. Methods can contribute together without forcing one universal workflow. The cost is a small comparison and join analysis; a genuinely composite Method may require more identification and assurance work. The pattern can therefore return an existing single Method, a bounded composite, or an explicit incomplete selection.

PSD.6:10 - Rationale

Method fit is relational: it depends on what the engagement needs and what its conditions permit. Complementary labels do not establish complementary results. Recovering reusable actions and their joins explains why the combination can work and what would defeat it, while keeping plans and enacted outcomes separate.

PSD.6:11 - SoTA-Echoing

PSD.6:12 - Relations

• PSD.4 supplies the scope/result frame for the same subject and decision. PSD.5 supplies model contributions only where they discriminate Method alternatives. Either needed input can be replaced only by a qualified direct result or returned as an exact gap.
• PSD.7 and PSD.16 may consume the selected Method and limits for the named situation and qualification window. Availability establishes neither fit nor enactment or cultural uptake.
• A.3.1.MR supplies provisional accounts only when several grounded occurrences or direct sources create a reusable-way recovery question and no Method is yet established; A.3.1 identifies a recoverable proposed way without making that recovery compulsory. A.3.2 governs a description of one identified Method; B.1.5 governs the composite qualification when needed.
• A.15.2 governs intended Work and A.15.1 actual Work and its enactment relation. Direct competence, participation, authority, evidence, and safety practices govern their own premises.
• This selection can request a missing domain result; it cannot manufacture that result by choosing a better workshop format.

PSD.6:End

PSD.7 - Facilitate Decision-Support Inquiry and Preserve Material Dissent

Type: DPF pattern body Status: Candidate

Primary working result: shared and contested claims without forced identity: a bounded inquiry return that distinguishes what participants understand, support, reject, or leave unresolved, with attribution, evidence limits, consequences for the receiving use, and a way to reopen material differences.

PSD.7:1 - Problem frame

Use this when participants need to work on a decision-support question but disagree about its meaning, evidence, consequences, or acceptable action. Also use it when a smooth workshop is producing an apparently unanimous answer that participants cannot recognize as their own.

Start by making the inquiry’s purpose, participation conditions, challenge route, and later choice boundary clear. Help participants state and test claims in terms their holders can recognize. Return useful common ground and material disagreement; agreement is one possible result, not a condition for an honest return.

The governed object is the bounded account of shared and contested claims for the receiving inquiry. Facilitation is the practical work of enabling that inquiry; the account is its result, not the conversation itself or a decision by the group. Shared wording, shared understanding, assent to a claim, consent to an action, and authority to choose remain different.

Do not use this pattern merely to circulate one clear qualified fact, record attendance, or administer an already-valid decision rule when no inquiry or interpretation problem remains. Direct mediation, adjudication, safeguarding, or emergency-command work retains its own remit. If the engagement has no recoverable receiving question or choice owner, return that missing premise.

PSD.7:2 - Problem

Facilitation can suppress the differences it is meant to make usable. A participant’s objection becomes a neutral-looking label, an absent group is treated as represented, and silence is recorded as consent. A model becomes “our view” although participants attach different meanings to it.

The opposite failure is endless disagreement. Every difference reopens the whole discussion, no one distinguishes an evidence gap from a value conflict, and the recipient receives a transcript instead of a result. Productive inquiry needs neither forced consensus nor unlimited debate; it needs a bounded account of what matters and what can be done with it.

PSD.7:3 - Forces

PSD.7:4 - Solution

Create conditions for participants to express, understand, challenge, and revise claims. Distinguish disagreement by what would resolve it, preserve material differences with their consequences, and return only the agreement and support actually established.

PSD.7:4.1 - Recover the inquiry, participation, and Method conditions

Use the current PSD.2 participation and concern account only for participants, affected Systems, concerns, representation limits, and missing voices material to this inquiry. Use the PSD.6 engagement Method and limits only for the same situation and qualification window. These inputs help establish what to facilitate; their availability does not show that participation is complete or the Method is being enacted.

Recover the receiving question, intended result, and later choice boundary from the current engagement terms or another qualified direct source. Make clear what this interaction can establish and what remains with the decision owner or a direct specialist.

If an input needed for the result is missing, stale, or incompatible, obtain its qualified direct source or name the precise gap. Do not infer consent, representation, permission, or authority from a participant list, a concern map, or a Method description. An affected System need not have a person present who is entitled or able to represent all its concerns.

PSD.7:4.2 - Establish workable participation and challenge conditions

Tell participants what is being asked, how their contribution will be used, how attribution and correction will work, and who will receive the return. Choose channels that permit meaningful contribution and challenge: a joint session, separate conversation, written response, accessible format, or a combination suited to the actual conditions. A workshop is not mandatory.

Make the facilitator’s remit and material interests visible. If the facilitator also owns a preferred intervention or controls participants’ opportunities, choose safeguards appropriate to that conflict, such as independent handling of a contested claim or a different facilitator. Do not describe the arrangement as neutral merely because the facilitation script is neutral.

Recover any rule governing consent, participation, confidentiality, or later decision from its actual authority. Ask whether the proposed conditions are usable, but do not treat acceptance of the discussion format as assent to its eventual findings. Where credible participation would expose someone to material harm or coercion, use an appropriately protected route, obtain competent support, narrow the claim, or stop that part of the inquiry.

PSD.7:4.3 - Elicit and test meaning before merging claims

Ask for concrete statements: what is happening or might happen, to whom, under which conditions, why it matters, and what would change the speaker’s view. Show how a contribution has been represented and invite its holder to correct the meaning. When useful, ask another participant to restate the claim and let its holder identify the remaining difference.

Separate observations, reported experience, causal hypotheses, preferences, duties, proposed actions, and commitments. A participant may agree that a claim was represented accurately while disagreeing that it is true or desirable. Keep those answers distinct.

Use models and shared displays to make questions discussable. A new connection or translation remains a proposal until its meaning and evidence are established. If two participants use “reliable service” differently, retain the two meanings instead of selecting a single label for convenience.

PSD.7:4.4 - Turn material disagreement into a usable inquiry result

A disagreement is material when it can change a formulation, candidate intervention, consequence claim, value treatment, recommendation, implementation condition, or legitimate receiving use. Preserve at least the disputed claim, its attributed positions, why the difference matters, the current basis, and what could change the next move.

An objection is neither an automatic veto nor something to erase by a majority count. Its effect follows from the actual claim and applicable decision rule. A vote can establish its own result when authorized; it does not settle truth, all participants’ consent, or the legitimacy of an unsupported trade-off.

Continue with unresolved differences when the receiving use can honestly preserve them. If a missing premise prevents that use, return the premise or narrow the result. Do not ask participants to manufacture consensus to keep the engagement on schedule.

PSD.7:4.5 - Keep the result faithful without collecting everything

Keep enough attribution and evidence for the recipient to understand and challenge each material claim. Retain the scope of representation: “the association’s representatives stated” is different from “residents agreed”. Where a protected contribution cannot be openly attributed, preserve its qualified status and disclosure limit without inventing public endorsement.

A transcript is not normally needed. Reuse a concise claim account, a corrected map, or annotated conclusions. Avoid collecting personal detail that contributes nothing to the receiving question, and do not promise anonymity or confidentiality that the actual arrangements cannot support.

Recognition of a difference needs no formal relation register. If later reliance requires a claim that consent, authorization, representation, or another relation obtains, use that relation’s direct pattern and evidence. Use A.6.REL only when the receiving use must additionally distinguish occurrences of the same relation kind, including separate episodes with the same participants.

PSD.7:4.6 - Close with shared and contested claims