Guides
Plain answers to questions that come up in IT operations and leadership, each tied to a book in the 365 Technical Series.
-
How to run a blameless post-incident review
A blameless post-incident review finds what let an incident happen, not who to blame, and ends with owned actions that actually close.
-
From engineer to IT manager: a plan for your first 90 days
Listen for 30 days, set direction by day 60, lead one larger improvement by day 90. A practical plan for engineers moving into management.
-
How to build a skills matrix for an IT team
List the skills the team must cover, rate people 0 to 3 and set the coverage you need. Gaps and single points of failure then show up on one page.
-
SLA vs OLA vs SLO: what each one is and how to write them
An SLA is the promise to the customer, OLAs are the internal promises behind it, and SLOs are measured targets. How to make them add up.
-
RTO vs RPO vs MTD: how to set recovery targets
MTD is how long the business can be down, RTO must fit inside it, and RPO sets how much data you can lose. Definitions, a worked example and common mistakes.
-
Standard, normal and emergency changes: how to tell them apart
Standard changes are pre-approved, normal ones are assessed first, emergencies stop harm now. A simple risk score and how to keep the emergency route honest.
-
Incident priority matrix: how to set P1 to P4
Set incident priority from impact and urgency. A P1 to P4 matrix with example response and restore targets, and how to roll it out.
-
99.9% vs 99.99% availability: how much downtime each allows
99.9% allows about 8.76 hours of downtime a year; 99.99% allows 52.56 minutes. A table for each level, and why dependencies and maintenance spend the budget faster than expected.