All examples for Proactive Risk Communicator

Basic Team Risk Triage

Simple baseline case with three common project risks (vendor delay, capacity, QA). Shows how the skill prioritizes by impact and provides appropriate communication guidance for each level.

Input

What you provide to the skill

We have three risks: delayed vendor delivery, reduced team capacity, and minor QA issues. When should we tell leadership?

Output

What the skill generates for you

RISK ASSESSMENT & COMMUNICATION PLAN

HIGH PRIORITY (Communicate Now)

RISK: Reduced Team Capacity

  • Urgency: 🔥🔥 HIGH
  • Impact: Timeline delivery, project commitments, team morale
  • Communicate to: Direct manager, project stakeholders, resource planning

DRAFT COMMUNICATION:

Subject: Team Capacity Impact - Action Needed
Team capacity reduced, affecting current sprint commitments.
Impact assessment needed:
- Which deliverables are at risk?
- Timeline adjustments required?
- Resource reallocation options?
Requesting meeting this week to:
- Review project priorities
- Adjust sprint scope if needed
- Identify mitigation strategies
Please advise on stakeholder communication approach.

MEDIUM PRIORITY (Include in Regular Updates)

RISK: Delayed Vendor Delivery

  • Urgency: 🔥 MEDIUM
  • Action: Monitor timeline impact, maintain vendor communication

DRAFT STATUS UPDATE:

MONITORING: Vendor delivery delayed. Following up daily with vendor for revised timeline. Assessing downstream impact on project schedule. Will escalate if delay extends beyond X days or blocks critical path.

ESCALATION TRIGGER: If delay impacts customer commitments or blocks multiple workstreams, elevate to HIGH priority immediately.


LOW PRIORITY (Monitor Only)

RISK: Minor QA Issues

  • Urgency: ❄️ LOW
  • Impact: Within normal variance for development cycles

RECOMMENDATION:
Don’t escalate. Minor QA issues are expected during development. Handle at team level with standard QA process.

ESCALATE IF:

  • Issues become patterns (3+ sprints)
  • Customer-facing bug escapes to production
  • QA issues cause release delays
  • Team raises concerns about product quality trends

COMMUNICATION TIMELINE

THIS WEEK: Team capacity reduction (immediate discussion with manager)

WEEKLY UPDATE: Vendor delivery status (if timing becomes clearer)

DON’T MENTION: Minor QA issues (team-level resolution)


KEY MESSAGE

“Flagging team capacity change that may affect commitments. Monitoring vendor delay for potential schedule impact. QA issues are within normal range and being handled by the team.”