Document how to run and recover a system.
What it really is
On the surface, Writing runbooks can look like a single technique you either know or you don't. The real skill underneath is owning an outcome end to end — from build, to production, to the customer actually getting value — and that's the part that actually transfers from one situation to the next. Here it shows up as a concrete, repeatable habit: document how to run and recover a system.
Why it matters
Ideas are cheap; shipped, working outcomes are rare. A Delta is the person a team trusts to carry something across the line.
What good looks like
- You take a thing all the way to done, not just to "works on my machine."
- You scope to the smallest valuable version and ship it.
- You follow through and close the loop without being chased.
Where it overlaps
This is a cross-cutting skill: it also draws on Technical Communication. The points you earn here count toward Writing runbooks's global total and toward its primary capability, Delivery Ownership.
Common trap
Declaring victory at code-complete and leaving the last mile to someone else.
How to practice
The rep: Document how to run and recover a system.
Do it on a real problem, not a hypothetical — under the kind of pressure where it's tempting to skip. Land it and you earn the Runbook Writer badge. Repeat it until it stops feeling like a technique and starts feeling like instinct.