Library / Operations Management Principles Framework
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:16:27 UTC · snapshot created 2026-10-03 05:17:06 UTC · last check 2026-10-03 05:16:56 UTC

OPS.19:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternFailureRepair
Maximize the visible resource.Local utilization consumes service, recovery, cash, or acceptance margin elsewhere.Compare the resource choice with every material protected result and moved burden.
Treat a shared timeline as proof that distinct Work wholes are parts or successive steps of one process.Overlap and separate Work identities are lost behind unsupported succession or part relations.Recover each Work identity and the exact temporal or part relation actually used.
Balance everything in one score.Unlike subjects, horizons, and uncertainties disappear behind weights.Keep each consequence explicit and apply a grounded decision rule.
Let the dashboard define the situation.Records and representations replace the operation and its missing facts.Recover subjects, evidence, omissions, and current relations before relying on the display.
Map the enterprise before choosing.Modeling cost grows while the exposed decision remains unresolved.Select only structures that can reverse the current choice.
Treat a feasible model as authorization.Another holder’s permission or professional judgment is bypassed.Obtain or return the exact authority-bearing result.
Call the reconfiguration a Method improvement.One operating allocation decision silently changes Method identity.Open OPS.16 only when reusable Method semantics and a bounded evidence question are current.
Call one successful continuation cultural adoption.Local use becomes an unsupported population claim.Use OPS.20 for the independently supported population and cultural predicate. Current grounds can suffice; new intervention and later evidence are conditional on the claim or selected work.