TPM Risk Register for Impatient Stakeholders

Free Review to certify

TPM Risk Register for Impatient Stakeholders

Hold ≥2 red risks and write a status that demands decisions — no activity theater.

Skills you'll learn

Risk register Dependency mgmt Status communication Escalation judgment Stakeholder mgmt

~115 min · +60 pts

SCENARIO: Mentors and an internal sponsor are impatient. Two risks are already RED (DeepSeek quota instability; one eng on leave next week). They keep asking "are we on track?"

Template: /assets/templates/tpm-pack/03-risk-status.md
Rubric: /assets/templates/tpm-pack/RUBRIC.md

Must produce:
1) Risk register ≥6 rows with likelihood, impact, owner, mitigation, trigger
2) At least TWO red risks with explicit escalation path
3) Dependency map (API vendor, design, mentor calendar, infra)
4) One weekly status to an impatient stakeholder: RAG, wins, DECISION ASKS, next week
   — Ban: lists of meetings attended or "busy" language
5) Escalation rule: when local vs when escalate

Submit: register + status + reflection on one risk you actively managed.

Environment setup (start here)

Fill 03-risk-status.md. ≥2 red risks and a status that asks for decisions — no busy theater.

Browser only

Pick your OS and follow from step 1:

Windows macOS

1) Open 03-risk-status.md + RUBRIC.md.
2) Keep the two given reds; add ≥4 more.
3) Write decision asks with A/B + recommendation.
4) Submit register + status + reflection.

Same as Windows.

How do I know it worked?

Status has RAG + at least one decision ask table — not a meeting list.

Common issues

Delete any sentence that only says you were busy.