Case Study · Retail & E-commerce
Incident Readiness for an Always-On E-commerce
- 4 scenariosResponse playbooks ready to use
- 2 exercisesTabletop simulations per year with the team
- RetainerContracted availability during peak periods
The challenge
An always-on e-commerce concentrates much of its revenue in a few weeks of seasonal peak. An outage or incident precisely in that window is worth far more than the same event in an ordinary month, yet the team had neither an agreed plan nor confidence it could reach support quickly.
The owners’ questions were concrete: who decides what during an incident, who can be called at midnight on a sale weekend, and how quickly the business is selling again.
Beneath those questions was a deeper one: preparing in advance costs little and predictably; improvising during the peak costs a lot and unpredictably. The choice was not whether to invest in readiness, but whether to do it with a clear head or under pressure.
My approach
With the team I wrote a small set of playbooks for the most likely scenarios — site unavailability, credential compromise, ransomware and payment fraud — with roles, decisions and escalation thresholds defined in advance, not improvised in the emergency.
An incident-response retainer made availability concrete: agreed response times and reinforced on-call windows during peak periods, so the first contact does not depend on luck.
Two tabletop exercises a year keep the plan alive: they test decisions under pressure, update the playbooks as the platform evolves, and align engineers and management on the same script before it is actually needed.