Beyond methodology choice¶
Ulrich, W. (2003). Beyond methodology choice: critical systems thinking as critically systemic discourse. Journal of the Operational Research Society, 54(4), 325-342.
Cited by¶
2 citations across 2 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Boundary Critique
- Mature practice navigates by adopting the narrowest boundary that survives critique (explicit justification for each exclusion), carrying multiple boundary alternatives in parallel during high-stakes decisions, and institutionalizing revision when excluded elements later demand attention.
This sourceRecasts critical systems thinking as ongoing critically-systemic discourse rather than one-off methodology choice; supports treating boundaries as provisional and subject to institutionalized revision.
- Mature practice navigates by adopting the narrowest boundary that survives critique (explicit justification for each exclusion), carrying multiple boundary alternatives in parallel during high-stakes decisions, and institutionalizing revision when excluded elements later demand attention.
- Reverse Engineering
- The inference of design intent, performance goals, and manufacturing constraints from observed structure and performance
This sourceUlrich beyond-methodology critical-systems-thinking discourse philosophical deepening.
- The inference of design intent, performance goals, and manufacturing constraints from observed structure and performance
Verification¶
Does it exist? Confirmed. This work's DOI resolves to a registered record, which fixes its identity. That is all it fixes.
Does it back the claim? Not recorded. Neither this nor any other of the 2 citations of this work carries a recorded support check.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:f16f71bb64d4 · see in the full table