The word 'managed' has been stretched until it means almost nothing. A vendor who sends you a monthly uptime report is 'managed'. So is one who watches a dashboard and opens a ticket when it turns red. Neither is what an enterprise actually needs when a payment system stalls on a Friday night.
Outcomes, not tickets
The first question to ask a managed provider is simple: when something breaks, who is accountable for it being fixed? Not who logs the incident — who owns the outcome. If the answer is 'we escalate to you', the service is monitoring with extra steps.
We run operations the way we would run our own: the team that builds a system is on the hook for keeping it healthy. Accountability that survives the handover is the entire point.
Runbooks are the product
An on-call engineer woken at 3am should not be improvising. Every system we operate ships with runbooks for its known failure modes — the symptoms, the checks, the safe remediation, and the line at which a human escalates. The runbook is not documentation that gathers dust; it is the operational product, rehearsed and revised after every incident.
SLOs make the contract honest
Vague promises of 'high availability' help no one. Service-level objectives turn reliability into a number both sides can see, argue about, and improve. A good SLO does three things:
- Names the thing users actually care about — a successful checkout, not a server's ping
- Sets a target that leaves room for planned, deliberate risk
- Comes with an error budget, so 'good enough' is defined rather than felt
The 3am test
Every managed-operations engagement we run has to pass one test: at 3am, with the principals asleep, does the system look after itself and its users without anyone guessing? If the answer is yes, the dashboards, runbooks, and SLOs have done their job. If it is no, we have more work to do before we have earned the word 'managed'.
Managed operations is not a tier of support. It is a transfer of responsibility — and it only counts if the responsibility actually moves.
Begin a conversation → about the systems you depend on.