TPM Incident Bridge (Sev-2)

Free Review to certify

TPM Incident Bridge (Sev-2)

Bridge eng and stakeholders during a sev-2 API latency incident — timeline, comms, follow-ups.

Skills you'll learn

Incident timeline Dual-track comms Demo call Permanent fix Blameless postmortem

~120 min · +65 pts

SCENARIO: CareerAck Path Finder API p95 jumps from 400ms to 4.5s during evening peak. Students complain in Circles. Mentors ask if demo tomorrow is safe.

Template: /assets/templates/tpm-pack/06-incident-bridge.md
Rubric: /assets/templates/tpm-pack/RUBRIC.md

Must produce:
1) Incident timeline (detect → mitigate → resolve) with owners
2) Internal status for eng/leads (facts, hypotheses, next check-in)
3) External/student-facing note (honest, no blame theater)
4) Decision: keep / postpone tomorrow's mentor demo
5) Permanent fix + prevention items with due dates
6) Blameless postmortem outline

Submit: bridge pack + reflection on the demo decision.

Environment setup (start here)

Sev-2 bridge drill. Use 06-incident-bridge.md for timeline, dual comms, demo call, follow-ups.

Browser only

Pick your OS and follow from step 1:

Windows macOS

1) Copy 06-incident-bridge.md.
2) Separate facts vs guesses in timeline and updates.
3) Decide keep/postpone demo; list fix/prevention with dates.
4) Submit + reflection.

Same as Windows.

How do I know it worked?

Demo decision is explicit; prevention items have owners and due dates.

Common issues

Do not invent a root cause mid-incident — label hypotheses.