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 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 09:50:10 UTC

OPS.5:6 - Bias-Annotation

Bias or pressureHow it distorts admissionCountermeasure
visibility and rank biasThe top visible item appears authorized and ready.Test identity, evidence, permission, authority, and start conditions separately.
sunk-commitment pressureEarlier planning or public promise is used to force admission.Recover the actual commitment parties, conditions, authority, and current status.
utilization pressureEvery available person, rig, tool, or model is filled immediately.State the bounded receiving result and explicit-start limit; preserve deliberate non-start.
automation biasA model recommendation or generated artifact is treated as admission or Work.Require a separate admission result, authorized starter, performance evidence, and later result evidence.
urgency leakageAge or consequence language becomes automatic admission order.Leave priority and commitment revision to OPS.7; use only the current admission criteria here.
silent-rejection pressureDeferred or rejected demand disappears from the account.Preserve identity, disposition, reason, retry or return, and residual demand.
source-school anchoringA familiar board, backlog, buffer, or WIP rule supplies the whole Method.Adopt only the bounded mechanism that changes this decision and keep its limits explicit.