What to Fix First When Your Mitigation Friction Scoring Misses Real-World Delays
You built a mitigaing frical scored model. It looks solid on the dashboard — green bars, low frical score, a promise that your group can contain a breach in under 15 minute. Then a real incident hits. And reality laughs. In routine, the method breaks when speed wins over documentation: however small the adjustment looks, the pitfall is that the next person inherits an invisible assumption, and the fix takes longer than the original task would have. Phones ring unanswered. VPN handshakes stall. The on-call engineer is on a plane. Your beautiful score? Useless. This is not a failure of math. It is a failure of imagination — the model missed the delay that actual matter. But here is the good news: you can fix it without rebuilding from scratch. You just call to know which lever to pull initial.