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

Anti-pattern	Failure	Repair
Total demand is below total hours, so the deadline is safe.	Timing, precedence or incompatible capability can prevent a schedule.	Recover the actual resource windows and a feasible witness.
Use mean utilization as a service guarantee.	The wait distribution and relevant tail remain unknown.	State the intended service criterion and select a suitable analysis.
Treat a scenario as a probability.	No occurrence model or calibrated data supplies that probability.	Label the conditional result and return the missing probabilistic basis.
Treat every person or machine-hour as interchangeable.	Capability, configuration and access differ.	Compare usable service capacity by the relevant class.
Count repeats as additional delivered results.	Attempts and accepted outputs have different identities.	Keep load and result populations separate.
Buy capacity before establishing the limiting mechanism.	The added resource may not change completion.	Use OPS.9 where the treatment basis is unresolved.