playbooks

home / skills / gtmagents / gtm-agents / risk-playbooks

risk-playbooks skill

/plugins/product-launch-orchestration/skills/risk-playbooks

This skill helps identify launch risks, assign owners, and coordinate mitigations across product, GTM, and support teams.

npx playbooks add skill gtmagents/gtm-agents --skill risk-playbooks

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.6 KB
---
name: risk-playbooks
description: Use when identifying launch risks, mitigation plans, and escalation owners.
---

# Launch Risk Playbooks Skill

## When to Use
- Pre-launch risk assessments and go/no-go criteria.
- During launch week to monitor escalations and coordinate mitigations.
- Post-launch retros to capture lessons and update future playbooks.

## Framework
Launch risk governance combines categorical coverage with a repeatable execution cadence. Use the following building blocks to keep Tier 1+ launches on track.

### Risk Categories
1. **Product & Reliability** – feature readiness, bugs, infrastructure load, rollback paths.
2. **Go-to-Market** – messaging accuracy, asset approvals, channel readiness, partner alignment.
3. **Compliance & Legal** – policy reviews, privacy terms, licensing, regional constraints.
4. **Support & Success** – staffing levels, escalation handoffs, enablement coverage.
5. **External Factors** – competitor moves, macro events, press sentiment, supply chain.

### Execution Process
1. Identify risks w/ likelihood + impact scoring.
2. Assign owners, mitigation steps, triggers, fallback actions.
3. Maintain real-time risk log during war-room standups.
4. Capture resolution notes + update future tiering guidelines.

## Templates
- Risk register (description, likelihood, impact, owner, mitigation, status).
- Escalation playbook (trigger, communication plan, action tree).
- Lessons learned tracker feeding future launches.

## Tips
- Pre-populate risk banks per tier to accelerate planning.
- Tie mitigations to instrumentation/alerts to catch issues early.
- Share summaries with execs daily during Tier 1 launches.

---

Overview

This skill provides a structured playbook for identifying launch risks, assigning mitigation plans, and naming escalation owners. It combines categorical risk coverage with a repeatable execution cadence to keep Tier 1+ launches on track. Use it to standardize pre-launch checks, wartime coordination, and post-launch learning.

How this skill works

The skill organizes risks into five core categories and surfaces likelihood+impact scoring for each item. It creates a living risk register, attaches owners and triggers, and generates escalation playbooks with clear communication and action trees. During launch, it supports a real-time war-room log and captures resolution notes to refine future playbooks.

When to use it

  • Pre-launch assessments and go/no-go decision-making for major releases.
  • Launch week coordination to monitor escalations and run war-room standups.
  • Immediate incident response when a trigger threshold is crossed.
  • Post-launch retrospectives to capture lessons and update risk tiers.
  • Preparing stakeholder briefings and daily executive summaries during high-risk launches.

Best practices

  • Pre-populate a risk bank by tier so common issues are ready to assess quickly.
  • Score every risk with likelihood and impact to prioritize focused mitigation.
  • Assign a single escalation owner and define fallback owners for each trigger.
  • Tie mitigations to monitoring and alerts so detection precedes escalation.
  • Keep real-time notes in a central risk log and update status in standups.

Example use cases

  • Evaluating product readiness and rollback plans before a global feature launch.
  • Coordinating GTM teams when messaging, assets, or partner alignment are at risk.
  • Defining legal and compliance checkpoints for region-specific rollouts.
  • Staffing and escalation planning for support during a high-traffic campaign.
  • Running a post-mortem to incorporate lessons into the next launch playbook.

FAQ

How do I prioritize which risks to address first?

Rank risks by combined likelihood and impact, then focus on high-impact, high-likelihood items and any single points of failure.

Who should be named as an escalation owner?

Choose the person with operational authority to act on the issue immediately, and list a secondary owner in case of unavailability.