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 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 06:15:20 UTC

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

Anti-patternRepair
Monitor implementation of what was merely recommendedObtain the later decision and implementation evidence separately; state unknown status when they are absent.
Use an indicator list as the whole arrangementName its claim, interpreting owner, timing, receiving use and failure return.
Trigger an action automatically from a thresholdEstablish the direct operational authority and response rule separately; otherwise return the qualified reconsideration question.
Rerun the whole engagement after every new versionInspect changed claim content and actual reliance; preserve independently usable results and reopen only affected contributors.
Reuse an A-specific evaluation for configuration BRetain the historical A result and obtain B’s exact qualification.
Interpret a missed observation as no changeReturn the gap and its consequence for reliance, with the responsible receiver.
Call later improvement proof that the advice workedObtain the direct causal or effectiveness result; chronology and satisfaction alone do not supply it.
Keep follow-up alive without an owner or end conditionEstablish the actual service or observation obligation, or close with an honest bounded return.