Skip to content

Incident response · Delivery under pressure

Software Delivery Case Studies

Real leadership is easiest to judge from what happened when something broke. Each of these carries the same structure: the situation, what I ruled out and why, the call I made and what it cost, and what stayed changed afterwards.

Delivery incidents resolved

11 documented
Infrastructure

Database Failure Under Load: A Production Incident Response

Critical

A live client's production database stopped answering at peak traffic. I ruled out capacity, traced it to slow queries and lock contention, killed the blocking statements while traffic was live, and left read replicas, indexes and caching behind: zero downtime recovery, 80% query performance improvement.

Read the full incident
Revenue Risk

Payment Gateway Failure During Launch: Two Hours to Zero Lost Transactions

High

A Stripe SDK update moved the API version and blocked every transaction mid-launch. I restored the revenue path with a fallback inside an hour, fixed the integration second, and added version monitors: 2-hour resolution, zero lost transactions.

Read the full incident
Delivery Risk

Sprint Velocity Dropped 40% Mid-Sprint: What To Do About It

High

Team output dropped 40% mid-sprint against a hard deadline. I ruled out underperformance and ruled out adding capacity, ran rapid 1-on-1s to surface what the group format was hiding, and rebuilt the delivery mechanics: delivered on deadline, velocity held 6+ months.

Read the full incident
Stakeholder

Managing Scope Creep with Clients: Three Weeks of Requests in the Final Delivery Week

High

A client asked for three weeks of new features during the final delivery week. I documented the agreed scope against the requests with the delivery cost of each item attached, shipped the contracted work on date, and moved the rest into a phased plan — the relationship held and Phase 2 was signed immediately after.

Read the full incident
Live Incident

A Production Outage During a Traffic Spike: 55 Minutes to Restore Service

Critical

A marketing campaign drove traffic the app could not absorb and it went partially down. I stood up an incident channel with named owners in ten minutes, protected the critical path by degrading everything else, and ran the client on a 30-minute update cadence — service was restored within 55 minutes.

Read the full incident
Release Blocker

A Release Blocked by Cross-Team Dependencies 24 Hours Before Go-Live

Critical

Cross-team dependency failures blocked a launch-ready release 24 hours before go-live. I mapped the chain, split the release into a core with no external dependencies and a deferred remainder, and validated it in a war-room — the core shipped on time with zero rollback.

Read the full incident
Client Escalation

Handling an Enterprise Client Escalation: Visibility Over Damage Control

High

A high-value client escalated over repeated delays and a communication breakdown. I chose full visibility over damage control — weekly executive syncs, shared dashboards, and named owners on both sides — and the account renewed and expanded.

Read the full incident
Quality Control

A Definition of Done Checklist for Software Teams, Written After Three Bad Sprints

Medium

Defect rate climbed for three consecutive sprints. I rebuilt the Definition of Done and moved the quality gate before the merge instead of after it, accepting slower throughput to bring leakage back down.

Read the full incident
Cloud Infrastructure

AWS ECS Deployment Failure Recovery: Restoring a Silent Production Outage in 35 Minutes

Critical

An ECS deployment completed without raising an error while the container never came up, taking a critical microservice down during business hours. I rolled back before diagnosing further, giving up the live failure state to get service restored in 35 minutes.

Read the full incident
Infrastructure

Production VPS Performance Tuning: From 4.2s to 0.6s Under 3x the Load

High

A production VPS started dropping requests under moderate traffic. Profiling showed the ceiling was configuration and unindexed queries rather than hardware, and tuning took average response time from 4.2s to 0.6s.

Read the full incident
AI & Automation

Automating Project Status Reports With AI Without Giving Up Accountability

Medium

Manual reporting was consuming 12+ hours per week across the team. I built an OpenAI-powered agent on top of ClickUp data to draft stakeholder reports and kept a human sign-off step, cutting weekly reporting time by 80%.

Read the full incident

Not an incident

This one is here because it is the evidence behind the 7 to 20 figure on the homepage. It is a scaling story, not a recovery, so it is not counted among the incidents above.