Platform Engineering Academy · Resource

Troubleshooting Runbook

An evidence-led sequence for triage, diagnosis, recovery and prevention.

01

Define impact and scope

Apply this section specifically to Platform Engineering Academy. Record assumptions, commands, screenshots, decisions, validation results and rollback evidence where relevant.

  • □ State the objective and expected outcome.
  • □ Identify dependencies, risk and failure signals.
  • □ Execute the smallest safe validation step.
  • □ Capture evidence that another engineer can review.
02

Collect facts before changes

Apply this section specifically to Platform Engineering Academy. Record assumptions, commands, screenshots, decisions, validation results and rollback evidence where relevant.

  • □ State the objective and expected outcome.
  • □ Identify dependencies, risk and failure signals.
  • □ Execute the smallest safe validation step.
  • □ Capture evidence that another engineer can review.
03

Test the lowest-risk hypothesis

Apply this section specifically to Platform Engineering Academy. Record assumptions, commands, screenshots, decisions, validation results and rollback evidence where relevant.

  • □ State the objective and expected outcome.
  • □ Identify dependencies, risk and failure signals.
  • □ Execute the smallest safe validation step.
  • □ Capture evidence that another engineer can review.
04

Recover with rollback ready

Apply this section specifically to Platform Engineering Academy. Record assumptions, commands, screenshots, decisions, validation results and rollback evidence where relevant.

  • □ State the objective and expected outcome.
  • □ Identify dependencies, risk and failure signals.
  • □ Execute the smallest safe validation step.
  • □ Capture evidence that another engineer can review.
05

Capture root cause and prevention

Apply this section specifically to Platform Engineering Academy. Record assumptions, commands, screenshots, decisions, validation results and rollback evidence where relevant.

  • □ State the objective and expected outcome.
  • □ Identify dependencies, risk and failure signals.
  • □ Execute the smallest safe validation step.
  • □ Capture evidence that another engineer can review.

Quality standard

Reusable by someone who was not present.

A strong resource removes ambiguity. It states prerequisites, decision points, commands, validation, rollback and ownership clearly enough for another engineer to execute safely.