Tell us about a time you had to respond quickly to an unexpected change?

While managing a midsize e‑commerce site launching a seasonal campaign, our primary payment gateway experienced an outage two hours before peak traffic. I led the incident response.

First 10 minutes: I convened the cross‑functional team (engineering, product, ops, customer support) in a short war‑room call, clarified the impact (checkout failures), and set a 15‑minute cadence for updates. I delegated: engineering to assess fallback options, support to prepare customer messaging, and product to prioritize which orders we could accept manually.

Next 30 minutes: Engineering confirmed our backup gateway was functional but not integrated for the specific promotion. I approved a minimal, risk‑controlled change: route new checkouts to the backup gateway and flag orders using the promotion for manual verification. Engineers implemented a configuration switch and smoke‑tested the flow. Customer support drafted a short, transparent notice for site banners, FAQs, and social channels explaining some temporary payment disruption and an estimated resolution time.

Next 30–60 minutes: With the fallback live, checkout success rate returned to acceptable levels. I coordinated with finance to monitor transactions and with operations to prepare a manual reconciliation process for flagged orders. We pushed the customer message sitewide and trained support reps with a concise script for incoming queries.

After stabilization: I ran a short retrospective with the team to document root causes, update our runbooks, and schedule the permanent integration of the backup gateway. We also added automated health checks and an alerting playbook to reduce response time in future incidents.

Outcome: The quick, structured response restored sales within an hour with minimal customer impact. The incident produced concrete improvements to our availability planning and cross‑team incident procedures.