All examples for Proactive Risk Communicator

Weekly Executive Update Triage

Realistic multi-risk scenario before Friday executive update. Demonstrates prioritization of revenue gaps, retention risks, vendor issues, and customer concerns with ready-to-send communications.

Input

What you provide to the skill

Key engineer might leave, API reliability down to 95% (SLA 99%), Q2 revenue at 85% target with 3 weeks left, design delayed 1 week, customer Acme hasn’t responded to renewal in 2 weeks. Executive update Friday. Prioritize what to communicate now.

Output

What the skill generates for you

RISK ASSESSMENT & COMMUNICATION PLAN

HIGH PRIORITY (Communicate Now)

RISK: Q2 Revenue Gap (85% of Target)

  • Urgency: 🔥🔥🔥 CRITICAL
  • Impact: Financial target miss, board expectations unmet
  • Communicate to: CEO, CFO, Sales lead

DRAFT COMMUNICATION:

Subject: Q2 Revenue Status - Action Needed



At 85% of Q2 revenue target with 3 weeks remaining.



Key question: Can we close the 15% gap in 3 weeks, or do we need to reset Q2 expectations?



Requesting meeting tomorrow to:

- Review pipeline for acceleration opportunities

- Decide on board communication approach



Timeline: Need decision by Wed to prep board materials if needed.

RISK: Key Engineer Retention

  • Urgency: 🔥🔥 HIGH
  • Impact: Project delivery at risk, knowledge loss
  • Communicate to: CTO, CEO

DRAFT COMMUNICATION (to CTO):

Subject: Retention Risk - Key Engineer



Flagging retention concern: Key engineer may be interviewing.



Impact if they leave:

- Current project delivery: Significant delay

- Knowledge transfer: 3-4 weeks minimum

- Team velocity: Reduced until backfill



Recommendation: Immediate 1:1 to understand what's driving this. Happy to provide project impact details.



Can we connect today or tomorrow?

MEDIUM PRIORITY (Friday Update)

RISK: API Reliability (95% vs 99% SLA)

  • Urgency: 🔥 MEDIUM
  • Action: Daily monitoring, vendor escalation active

DRAFT STATUS UPDATE:

MONITORING: API vendor at 95% uptime last week (SLA: 99%). Escalated with vendor account team, monitoring daily. Evaluating backup options if pattern continues. No customer impact yet.

RISK: Customer Non-Response (Acme)

  • Urgency: 🔥 MEDIUM
  • Action: Sales follow-up, not exec-level yet

RECOMMENDATION:
Slack sales lead: “Acme renewal email sent 2 weeks ago, no response. Worth a call? Happy to join if useful.”

LOW PRIORITY (Monitor Only)

RISK: Design Delay (1 Week)

  • Urgency: ❄️ LOW
  • Impact: Within normal variance

RECOMMENDATION:
Don’t escalate. One-week delay is normal. Escalate only if extends to 2+ weeks or blocks critical path.

COMMUNICATION TIMELINE

TODAY: Revenue risk (email CEO/CFO), Retention risk (Slack CTO)

FRIDAY UPDATE: API reliability monitoring, Acme renewal (if sales confirms concern)

DON’T MENTION: Design delay (too minor for exec attention)

View all examples for Proactive Risk Communicator

About This Skill

Assess product risks and generate stakeholder communications before issues become crises. Prioritizes risks as HIGH/MEDIUM/LOW, drafts escalation messages, and recommends monitoring approaches.

View Skill Details

More Examples

Launch Steering Committee Dashboard

Edge case with multiple launch-blocking risks requiring Red/Yellow/Green status for steering committee. Shows how to frame critical decisions, present options, and recommend specific actions with deadlines.

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.

View all examples