Back to Closing Cloud Skills Gaps Before Go-Live
Go-Live Readiness
A certification tells you someone read about the platform. It does not tell you whether a named person on your team can run this exact task, on this exact stack, when something breaks at 2 a.m. Score that, then close it, before cutover.
Free
Six categories, one question each, and a score you cannot fake without producing a name.
A five-page PDF built around the Go-Live Readiness Scale v1, covering deploy, rollback, failover, restore, triage, and credential rotation. Each category gets a named person, not a rating, scored 0 to 4 for a total out of 24, sorted into a red, yellow, or green band.
Get the DiagnosticMost go-live checklists ask how confident the team feels. Confidence is not the thing that fails at 2 a.m. on launch night.
This diagnostic asks a narrower, harder question. Who on your team has personally done this exact task, on this exact stack, in the last 90 days. A blank next to a task name is not a data problem. It is the thing the diagnostic exists to surface.
The score is only useful the day you are honest about the blanks.
Paid
A four-phase protocol that starts exactly where the diagnostic ends, turning named gaps into rehearsed capability.
| File | Format | What It's For |
|---|---|---|
| The Go-Live Readiness Sprint | Word (.docx) | The four-phase workbook. Build the runbook, gap-map the team, design drills, and work through a staging environment decision list. Includes the one-drill fast path for teams inside two weeks of cutover. |
| Go-Live Gap Tracker | Excel (.xlsx) | Scores the same six categories as the free diagnostic and calculates total score, coverage percentage, and readiness band automatically. |
| Readiness Gap Diagnostic | The free diagnostic, bundled in so the archive stands on its own. |
Every file ships editable. Tailor the runbook, the drills, and the staging decision list to your own stack, team size, and tooling before you run it.
The free diagnostic and the paid Sprint use the same scale. Score your six categories in the free PDF, then paste those same rows straight into the Sprint's Gap Tracker under matching category names. Nothing gets retyped. The diagnostic tells you where the gaps are; the Sprint is what closes them before cutover.
Fit
You are a migration lead, VP Engineering, or eng manager with a cloud cutover inside the next six weeks, and you need a straight answer to whether the team can operate the platform under pressure, not whether they have heard of it.
You already run regular game days or DR drills on this exact platform, or your go-live is more than a few months out. This protocol is built for a short clock. A team with months to prepare should build broader depth instead.
