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

Anti-pattern	Why it fails	Repair
Count every board item as ready supply.	Some items lack prerequisites or use another service.	Recover membership and missing-input populations.
Treat commitment as buffer membership.	A promise does not establish eligibility or physical protection.	State the two relations separately.
Size a “never empty” buffer from averages.	A mean relation does not establish the shortage tail.	Qualify replenishment scenarios and consequences through OPS.10.
Improve the metric by moving its start boundary.	The customer can wait just as long outside the reported queue.	Preserve the end-to-end origin and show local waiting separately.
Use one pooling or batch rule everywhere.	Compatibility, failure, setup and service objectives differ.	Compare the concrete alternative under the receiving operation’s conditions.