Platforms & Products
The training I wish had existed the first time I was handed a global outage.
The problem
Most engineering organizations are still improvising incident command the first time the pager goes off at 3am, and the cost of that improvisation is paid in minutes of downtime and years of team attrition.
Incident command is a learnable skill with a fifty-year body of practice behind it. It just was not written down for software.
ICS principles translated to production engineering, severity triage, escalation decision trees, stakeholder and executive communication during an active incident, the runbook patterns that hold up under pressure, and blameless postmortem workflows that produce durable corrective actions instead of theater.
Engineering decisions
No vendor pitch.
The moment incident training becomes a funnel for a tool, it starts teaching the tool instead of the discipline.
Reliability & Automation
One person cannot watch a production fleet around the clock. So the machine takes the first action, and the interesting part is everything that stops it.
Security & Response
Everybody has detection. Nobody has anybody to read it. That is not a problem you hire your way out of, and it is not a problem you buy another product to fix.
Security & Response
The AI never writes a command. It picks a number off a list, so the worst a hostile input can do is make it pick a different approved action.
If your team is drowning in toil, alert noise, or incidents that never quite close. That is the work I do.
Get in touch