Severity Isn’t an Input – it’s an Outcome
Severity is not a category. It’s a consequence.
When systems are placed under plausible stress, structural limits reveal themselves. Pre-defining severity narrows what testing is allowed to teach us.
Plausibility is the constraint.
Severity is the signal.
Testing Fatigue: When Tabletop Exercises Stop Teaching Us Anything.
Why tabletop exercises often confirm what we already believe — and how testing becomes rehearsal rather than discovery when assumptions go unchallenged.
Fear of Fail-over: What Really Holds IT Teams Back in ITDR
Failover plans often exist. Testing schedules are agreed. Yet hesitation persists. This article explores why technical capability alone is not enough — and how organisational confidence, incentives, and perceived risk quietly shape whether recovery is ever truly exercised.