PSD.15 - Decide Whether and How to Change Problem-Structuring and Decision-Support Methods

Type: Method pattern (DPF) Status: Candidate

Primary working result: a current decision-support Method repertoire for named recurring uses, with the ways offered or retained as candidates, their comparative reasons, applicability and evidence limits, cultural lineage, source-to-claim basis, and conditions for refresh or withdrawal from a particular use.

PSD.15:1 - Problem frame

Use this when a practice needs to decide which problem-structuring and decision-support Methods to retain, change or withdraw from its offering for future engagements. A familiar workshop no longer covers a recurring participation difficulty. A new analytical technique seems promising, but its input assumptions differ from those of the existing repertoire. Follow-up exposes a repeatedly broken join between a material correction and the recommendation that should use it.

Start with the recurring difficulty and the repertoire decision: which way should remain available for which situation, which proposed change deserves a trial, and which use should be narrowed or withdrawn? A better source or a qualified failure can justify a small change; the practice need not redesign its entire repertoire.

Problem structuring and decision support is the wider practice. This pattern governs development and maintenance of its reusable ways of working. A repertoire here is a bounded set of Methods and separately identified candidate accounts with usable conditions and reasons, not a catalogue of schools, a software inventory, a training curriculum or an assertion about the whole discipline.

The gain is a practical choice for the next engagement: a practitioner can recover what a Method does, where it fits, what evidence supports that use, what alternative remains, and when to ask for another result. A small repertoire can be better than a comprehensive list that hides unsupported transfers.

Do not use this pattern merely to choose an adequate existing Method for one engagement; use PSD.6. Use PSD.14 to respond to a changed premise in one current recommendation, and PSD.16 for a conflict in the current work arrangement. Enter this pattern only when that evidence can affect the decision to retain or change a reusable Method, applicability claim or repertoire offering. Changing a document, tool, source locator or one local performance does not by itself create a new Method.

PSD.15:2 - Problem

Professional repertoires tend to harden around what their practitioners can already teach, facilitate or compute. New situations are then forced into the incumbent’s assumptions: unclear values become invented weights, unequal participation becomes apparent agreement, and a dynamic uncertainty problem becomes one fixed scenario.

The opposite failure is uncontrolled combination. Each engagement adds another technique or software assistant, but nobody identifies the reusable action, the meaning of the joins, the evidence that transfers or the conditions that defeat it. The resulting collection is larger without being more useful.

Published applications and local successes can compound the problem. A reported use is evidence of that use, not proof of general superiority. A new edition may improve a description without changing a Method. A promising variant may deserve a trial without inheriting its parent’s fit. The practitioner needs a repertoire-development decision that preserves these differences and still supports action.

PSD.15:3 - Forces

PSD.15:4 - Solution

Develop the repertoire around recurring decision-support results and the conditions that make them possible. Recover the actual Methods, compare live alternatives, and retain or change the offering with its source and evidence return. Trial a consequential change only when further evidence can change that decision and its attainable contribution warrants the burden. These are dependencies in reasoning, not a compulsory lifecycle for every engagement.

PSD.15:4.1 - Bound the repertoire question by the work it must serve

Name the practitioner group or service using the repertoire, the recurring situation, the receiving decision-support result, and the horizon over which the offering matters. The starting question might be: “How can our engagements preserve a late but material participant correction without losing the ability to produce a timely qualified recommendation?”

Recover only conditions that can change the answer: disputed or already formed question; participants and power; access to affected parties; values and protected conditions; alternatives; uncertainty; available evidence; technical and facilitation capability; decision authority; receiving Work; and follow-up need.

Use a PSD.14 result only when its evidence can change this repertoire decision under the relevant configuration and horizon. A changed mobile-deployment premise may show that the existing follow-up Method worked by returning the correct blocker. It does not by itself demonstrate a defective Method. If a supplied result is missing, stale or incompatible, use a qualified direct account or name the precise gap.

Distinguish a missing input, a failure to enact the stated Method, a support or capability problem, and a defect in the reusable way itself. A practice cannot repair absent stakeholder access simply by adding another modelling technique. Conversely, more training cannot repair a Method rule that systematically excludes the required correction.

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.

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.

PSD.15:4.3 - Compare the incumbent with a serious alternative before designing a variant

Name the current offering, a plausible competing Method, and a bounded adaptation or combination only where each is live. Compare them against the same recurring result and the actual conditions, at comparable effort where possible.

Ask what each lets participants and practitioners do, what it leaves unresolved, and where it fails. In addition to analytical adequacy, consider meaningful challenge, unequal power, facilitation burden, interpretation skill, source qualification, time to a usable return and cost of maintaining the offering. State a deliberately accepted trade-off when the richer result costs more.

Do not infer that one Method is universally better because it produces a precise score, a satisfying workshop or more alternatives. A single well-qualified Method can remain the best offering for a narrow use. Plural formulations can be necessary elsewhere; a numerical comparison can still be necessary after them.

When a change is needed, state its mechanism: which reusable action, input condition, dependency, decision rule or stop changes, what remains, and why that difference could repair the failure. Distinguish this from a change in wording, display, software, local staffing or performance. The latter may require maintenance or a new fit check without identifying another Method.

For example, replacing a paper map with a digital map while preserving attribution, challenge and unresolved-claim rules may change support and access. Replacing the challenge rule with automatic aggregation of all statements changes the reusable way and can lose dissent. The same interface change can therefore have different repertoire consequences depending on what practitioners actually do.

Use current ME.15 guidance when generic variant identity, derivation or non-variant maintenance is the live subquestion and its exact claims fit. The remaining PSD question is whether that way serves the professional decision-support use: how interpretation, participation, values, uncertainty, authority and follow-up contribute to a usable return. Generic variant maintenance does not answer that field judgement.

PSD.15:4.4 - Build a source-to-claim basis, not a popularity ranking

For every repertoire claim that can change later use, retain the source contribution and its actual limit. An instruction can describe a Method; a reported application can show that it was used; an observed interaction can illuminate a failure mechanism; a comparative study can support a bounded advantage. These are not interchangeable evidence.

A useful basis line says: this source or qualified experience supports this action or applicability claim for these conditions; this uncertainty remains; this new observation would change the offering. Include source edition, relevant locus, evidence window and original meaning where they matter. Recover contrary cases and the serious alternative, not only supportive citations.

The 2019 Smith and Shaw review provides an exploratory way to compare PSM characteristics; its classification is not an exhaustive admission rule. Kogetsidis’s 2025 application review and 2026 online review of Europe and beyond provide leads about reported applications. Their journal and search boundaries limit what they establish about practice outside that corpus. Do not rank Methods by the number or location of publications.

A recent decision-analysis synthesis such as Borgonovo et al. (2026) can identify developments in value-focused thinking, graphical modelling, uncertainty, sensitivity and information acquisition. It does not substitute for the source of a particular Method or cover every adjacent decision-support family.

Obtain missing source interpretation, domain evidence or representative evaluation through A.15.9, preserving supplier authority, and qualify actual reliance through A.10. If the decisive source contribution cannot be recovered, keep that offering conditional or return the source gap. Neither a famous school nor a new source date repairs the missing claim.

PSD.15:4.5 - Trial the claimed improvement in representative engagements

For a selected trial, turn the proposed improvement into a question that can fail. Specify the Method or status-preserved candidate, the situation represented, participant and power conditions, required capability and support, the serious comparator, the expected result, the burden accepted, and the observation that would retain, narrow or reject the proposal.

Select evidence proportionate to the claim. A walkthrough can expose an impossible join. A constructed exercise can test whether practitioners preserve an objection through a calculation. An authorized field trial can test feasibility and use in a real engagement. Broader transfer or causal-effectiveness claims need stronger and appropriately designed evidence. Do not generalize the last two from the first two.

Observe the working mechanism as well as the output: who could contribute or challenge; which material statement entered the model; where meaning changed; what was withheld; how uncertainty and protected conditions reached the recommendation; and whether the receiver could use it. The distinction between technically valid models and what people do with them is central to Franco et al.’s behavioural OR review (2021). It supports attention to intervention configuration and interaction, not one universal trial design.

Preserve competing explanations. Better results may reflect a more skilled facilitator, a different participant group, more time, an easier problem or changed support rather than the Method difference. Where those cannot be separated, report what the trial establishes and what remains unresolved; a useful feasibility result need not pretend to be a causal result.

Do not use a consequential live decision as an uncontrolled Method experiment. Establish the authority, consent, protection, observation and fallback conditions appropriate to the engagement. A prospective candidate can be investigated through a separate trial arrangement without claiming that an unadmitted candidate whole has already been enacted as a U.Method.

Retain disconfirming results. A richer Method that cannot run within the actual access or competence conditions may be a poor offering for that use even when its idealized output is better. Conversely, a failed local performance does not disprove the Method when a required condition was absent; it may instead defeat the offered applicability claim.

PSD.15:4.6 - Return a small current repertoire with differentiated dispositions

Decide what the practice can now offer, for which use and with which limits. Useful dispositions include retaining an established offering; narrowing its applicability; adding a separately identified variant for a qualified use; retaining a proposal for a bounded trial; requesting missing evidence; and withdrawing an offering from one use while preserving its history.

Keep identification separate from validation. An independently identified Method may still have unproved practical fit. A candidate account may have useful trial evidence without yet resolving its Method identity. State both rather than using one maturity label for every question.

For each action-changing entry, make the following recoverable in the simplest form that serves its next user.

A repertoire may retain alternatives without ranking them. When the actual question is declaring a selector-facing set result over already identified members, use G.5 with the exact members, outcome, ordering and basis it requires. Distinguish alternatives retained for later choice from members all included in one named joint use. A Method-family registry or selector declaration supplies neither field fit nor actual enactment and need not be rebuilt for every repertoire update.

Make the next use easy to find: which Method a practitioner should inspect for the named situation, which claim still needs evidence, or which use has been withdrawn. A large source map that gives none of these is not the promised repertoire.

PSD.15:4.7 - Preserve cultural lineage without inventing cultural continuation

Record where a reusable change came from when that relation matters: an identified source Method, a documented adaptation, a changed stopping rule, a taught practice, or another qualified source. Similar names, chronological succession and a shared diagram do not establish derivation.

Keep proposed derivation, observed local enactment, transmission to another practitioner, recognition, selection, retention and loss distinct. A source publication can make a description available without proving that anyone learned or enacted the Method. A successful trial can justify a restricted offering without showing that a professional community adopted it.

Use C.36 for an actual cultural-evolution question. Supply PSD.17 with the repertoire’s qualified variant or local evidence only when it matters to that cultural-continuation decision. Name the practitioner population, engagement/community, place and period that the evidence actually covers, and mark the unobserved links. The receiving cultural decision is not entailed or authorized by the repertoire.

This boundary applies equally to new software support and AI-assisted practice. A tool release is not cultural uptake; widespread use of a tool is not evidence that the same Method was enacted by everyone. Teaching, service change and deliberate cultural intervention require their own work and authority.

PSD.15:4.8 - Refresh the affected offering and preserve an honest stop

Maintain a responsible source and use return for the current repertoire. Reopen an entry when new evidence, a source claim, changed Method semantics, participation or authority conditions, support, qualification window or receiving need can change its offering. A new publication date or a file rename alone is not such a change.

For a changed claim, identify its exact repertoire use and the consequence: preserved, narrowed, reopened for a new trial or source result, or withdrawn from that use. Preserve independent entries and the earlier evidence for its original conditions. If applicability remains unresolved, state the uncertainty rather than assigning an unsupported negative or positive status.

A changed service rule might restrict the human career-advising branch without changing organization or AI-domain truth. A new AI configuration may invalidate evidence for a software-assisted offering without changing the manual Method. If the reusable decision-support action itself changes, identify and assess that semantic change rather than hiding it as maintenance.

Use A.10 for a known bounded reliance, and A.10.1 when a changed source requires discovering and revalidating several actual receiving uses. Invoke G.11 for an admitted currentness or refresh-planning/reporting object when its conditions obtain, such as a relied-on evidence or selected set; it does not supply the new repertoire judgement or make every local entry a refresh-orchestration problem.

Close this repertoire question when the relevant offerings, conditions, source/evidence gaps and next uses are clear. Withdraw only the defeated use, not recoverable history or other supported uses. A still-unqualified new proposal can remain visible without being offered as established practice.

PSD.15:5 - Archetypal Grounding

The cases are hypothetical. They distinguish source description, proposed Method change, constructed trial, qualified offering and later cultural evidence; they assert no actual practice-wide improvement.

PSD.15:5.1 - A late correction changes an offering, not the whole school

A public decision-support practice serves flood-investment engagements. It maintains an identified one-session inquiry Method: elicit and attribute concerns, compare the admitted alternatives with qualified inputs, record material dissent, and close the session with a bounded return. The Method presumes that all decision-bearing contributions needed for that return are available within the session. The practice has nevertheless offered it as the sole inquiry option for these engagements, including ones in which necessary input can arrive later.

The PSD.14 pump follow-up case supplies a changed mobile-deployment premise and the resulting blocker. That alone is not a Method defect: the follow-up correctly prevented an unsupported investment use. The practice retains that evidence at its actual scope.

A separate examination of the one-session offering finds the action-changing mismatch. Engagements in this service can receive a qualified access correction after the meeting, while the reusable closing rule provides no way to bring it into the same pending recommendation. The practice must not advertise that offering as sufficient for such engagements.

Three alternatives are considered. Keep the one-session Method but restrict it to uses with the necessary inputs already available; defer the whole engagement until every possible input arrives; or construct a bounded correction-and-return variant that keeps attribution and conditional analysis, permits a material qualified correction before the receiving recommendation closes, and reopens only the affected comparison.

The third proposal changes a reusable join and closing condition, not merely the calendar. Its candidate account records the parent, retained actions, changed rule, required facilitator/analyst availability and stop when a late contribution cannot be qualified in time. Independent Method identification remains separate from evidence of practical fit.

The practice runs a constructed exercise, not a public investment experiment. Both the incumbent and proposed rule are examined on the same two realistic situations: all required inputs available at the meeting, and a material access correction arriving afterward. Participants’ access, analyst time and the receiving deadline are made explicit. The test is whether the correction changes the exact affected comparison while preserving dissent and independent usable claims.

In the illustration, the incumbent gives an adequate bounded return in the first situation but leaves the second correction outside its closed result. The proposed rule preserves the correction and exposes its unresolved consequence in the second situation, at the cost of a further qualified return and analyst/facilitator time. This exercise supports the proposed join’s feasibility under those conditions, not superior public decisions or transfer to all engagements.

The repertoire result is deliberately differentiated:

No pump is chosen. The staged alternative and assistance/protection questions in the original investment case remain with their direct owners. The repertoire entry does not claim that other practitioners have received, enacted or retained the proposed variant; those cultural links remain unproved.

PSD.15:5.2 - Non-contested development advice and a new software assistant

An advisory service already supports formed development questions without a dispute workshop. Its repertoire includes a source-bounded recommendation Method: recover the recipient, holder and horizon; inspect qualified specialist results; compare only live alternatives under the declared scheme; return a warranted direction, retained set, probe, request, blocker or abstention; and keep the recipient’s choice separate.

A new drafting assistant formats the same qualified premises and flags missing fields. If the adviser still performs the same qualification, comparison and return, the changed object is support. The practice checks access, confidentiality, capability and output reliability for that support; it does not create a new Method merely because the model version changed.

A different proposal lets the assistant select a preferred development direction from its own generated ranking and omit unranked candidates. That changes the reusable comparison and stopping rule. The practice cannot import the manual Method’s evidence or call the proposal a harmless implementation detail.

The immediate repertoire decision is to retain the manual offering and withhold the stronger automated offering pending an exact candidate account, comparison basis and representative evidence. A useful trial must include an absent whole-arrangement result, an unclosed provider alternative, and an evaluation that covers configuration A while the request concerns B. Success means the return preserves the correct gap and independently useful content, not merely that the text is fluent or shorter.

The trial also has to cover the actual human professional-service conditions where present. Human career-assessment evidence does not establish an AI-holder result, and an organization’s allocation evidence does not establish a person’s learning transfer. No generic development-direction score bridges those differences.

This is repertoire work, not a recommendation for a particular client, authorization to deploy the assistant, or proof of the full opportunity-construction Method. A human or organizational recipient still makes its own later choice.

PSD.15:5.3 - A source update and a cheap non-use

A new version of a relied-on methodological source changes the conditions under which a comparison procedure may be used. The practice identifies the exact applicability claim in its repertoire. The supported entry for complete input data remains; the incomplete-data branch is narrowed and its source question reopened. Other Methods that do not use that claim remain unchanged.

If the new source only changes layout or a locator while preserving the relied-on claims, update that description or access information under its direct guidance. If one current engagement simply needs an adequate existing Method, stop repertoire development and use PSD.6. Neither situation warrants a new professional Method.

A review reporting more published applications can justify looking for a promising candidate or an unexamined domain. It does not by itself change a local offering’s evidence or justify retiring a less frequently published Method.

PSD.15:6 - Bias-Annotation

School loyalty and novelty bias pull in opposite directions. Compare the strongest applicable incumbent and the smallest useful new proposal; do not protect either by choosing an easy example. A practice’s available expertise is a real constraint, but it is not evidence that other Methods lack value.

Publication and success-reporting bias can hide failed, unpublished or culturally distant uses. Preserve the source search boundary and distinguish reported applications from representative evidence. A corpus dominated by particular journals cannot establish the absence of a practice elsewhere.

Combination bias treats more techniques as richer support. Inspect the meaning and cost of the joins. Automation bias treats a change in software as either automatically new or automatically harmless; recover whether reusable actions and stops actually changed.

PSD.15:7 - Conformance Checklist

Recognition asks whether the missing result is a reusable repertoire offering rather than an engagement choice, one source update, a support repair or a current follow-up response. One corrected applicability line can be the complete useful result.

Assurance asks whether the offered Method or candidate and its claimed use are warranted by the actual source and trial evidence. A description can identify a way without proving fit; a constructed exercise can support feasibility without proving real-world effectiveness or transfer. Consequential trials and offerings retain their direct participant, competence, independence, safety, confidentiality and authority conditions.

A failed check may narrow one offering or retain a candidate for investigation while other entries stay usable. Do not label the whole repertoire current merely because every row has a source link.

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

PSD.15:9 - Consequences

Future engagements gain a smaller, more discriminating starting point. Practitioners can reuse a Method for a supported situation, select an alternative, ask for a missing input or decline an unsupported extension. Changes become recoverable improvements or bounded experiments rather than accumulating workshop tricks.

The cost is maintaining meaningful applicability and evidence, not just names and editions. Some promising candidates remain unoffered, some broad claims narrow, and some local successes support only the conditions observed. That restraint leaves room for development without presenting uncertainty as established practice.

PSD.15:10 - Rationale

The repertoire decision remains after Method identity, generic comparison, variant maintenance and set declaration have done their work. It asks which professional ways can help this practice structure problems and support decisions under actual participation, value, evidence, authority and follow-up conditions.

This is different from choosing a Method once. A future-use offering must preserve enough source, evidence, lineage and limits to survive transfer to another practitioner or engagement. It is also different from changing a culture: making a variant available does not establish the relations through which a community learns, enacts or retains it.

A changed premise can vindicate the incumbent’s stop rather than defeat the Method. That is why development starts with the recurring failure or opportunity and the affected claim, not the mere fact that a recommendation changed.

PSD.15:11 - SoTA-Echoing

The practice question is how to develop a usable professional repertoire under heterogeneous situations and uneven evidence without turning either an incumbent school or each new technique into a universal answer. The selected line is contribution-first comparison, explicit assumptions and joins, representative testing of the claimed change, and local source/evidence refresh. It accepts the cost of maintaining differentiated offerings; a simple established Method remains preferable when it covers the use at lower effort.

PSD.15:12 - Relations

• PSD.14 supplies bounded follow-up evidence only when it can change the repertoire decision under the same relevant conditions and horizon. A local observation neither entails nor authorizes the repertoire result.
• PSD.6 chooses and combines Methods for an engagement; this pattern develops and maintains the reusable offerings and their limits. It does not require a new repertoire cycle before every selection.
• PSD.7, PSD.8–PSD.14 and PSD.16 expose participation, alternative, comparison, recommendation, follow-up and arrangement requirements that a Method offering may need to preserve. Their available descriptions are not evidence of this particular Method’s enactment or effectiveness.
• A.3.1 governs Method identification; A.3.1.MR supplies candidate recovery only under its actual source/occurrence conditions; A.3.2 governs a MethodDescription rather than admitting every multi-Method package.
• ME.15 can supply qualified generic variant, derivation and non-variant maintenance guidance. Resemblance or shared repertoire vocabulary does not by itself establish a formal Method-specialization relation.
• A.10 and A.15.9 qualify and obtain exact source or specialist results. A.10.1 and G.11 apply to their respective affected-use and currentness questions, not as substitutes for the field repertoire decision.
• G.5 declares a selector-facing result when that claim is live over identified members and grounds; it supplies neither a universal Method-family classification nor professional fit.
• C.36 governs the cultural relation claims. PSD.17 uses this repertoire as evidence or a variant for a separately bounded cultural decision; missing generation, transmission, receiving-enactment, recognition, selection, retention and loss links remain unproved.
• An unavailable, stale, out-of-scope or incompatible input calls for a qualified direct source or the exact gap. No sibling DPF, whole-language traversal or unperformed specialist result is implied by adjacency.

PSD.15:End