Matt Blair

Matt Blair

I read that you learn more from a poor example than from a correct one. I don't believe this but that means my site will be a success.

3-Minute Read

When something breaks in production—maybe a server crashes or a deployment goes sideways—it’s tempting to point fingers and hunt for the person “at fault.” But that only breeds fear and discourages honest discussion. A blameless postmortem flips the script: it treats every outage as a chance to learn how our systems and processes can improve, rather than a moment for shame.

Setting up an on-call roll

My lessons learned

3-Minute Read

On-call rotations are more than “who picks up the phone”—they’re a critical way to balance incident response, customer support, and operational health without burning out your team. Below is a template you can adapt, illustrated with examples from my time leading a device-management on-call rotation at a fast-growing tech company.

Decoding the Origins of CAN Reports

A SitRep in three parts

3-Minute Read

In the realm of incident management, accurate and swift communication is vital. Different organizations adopt various strategies to ensure efficient communication during emergencies. One such strategy that has been gaining traction is the utilization of CAN reports, a mnemonic that stands for “Conditions, Actions, Needs.” Let us delve deeper into the intricacies and origins of this unique reporting format.

Recent Posts

Categories

About

This theme was developed for Hugo.