Operational Excellence

Operational excellence is the part of the job nobody puts on a slide: patching discipline, backup verification, monitoring built as a system rather than a pile of alerts. In a production LNG environment there is no such thing as a purely technical incident, and it took me a good two years to properly believe that rather than just repeat it.

Day to day it means proactive monitoring across server health, messaging, replication, and backup validation. It means patch and change management where the rollback plan exists before the change does, and where somebody has actually asked what depends on this. It means chasing root causes instead of managing symptoms, and coordinating across teams at an hour when nobody wants to be coordinating anything. From 2019 the standard was explicit: zero business incidents, written as an architectural commitment rather than an operations KPI.

Crisis is where that discipline gets audited whether you want it or not. When WannaCry hit in May 2017 the patch programme I had been building stopped being theory. Two fronts at once: reboots sequenced across the whole server estate, and short factual updates to supervisors so nobody had to guess what was already protected. When a second ransomware variant turned up weeks later we reused the playbook instead of inventing a new one, which is the only reason it was a bad week rather than a bad quarter.

Architecture that ignores any of this doesn't survive contact with production. The early-morning troubleshooting is what lets you design something a team can actually run.