playbooks

home / skills / gtmagents / gtm-agents / stakeholder-ops

stakeholder-ops skill

/plugins/customer-feedback-orchestration/skills/stakeholder-ops

This skill coordinates multi-team approvals and governance for feedback programs, ensuring clear accountability, timely updates, and structured action tracking.

npx playbooks add skill gtmagents/gtm-agents --skill stakeholder-ops

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

Files (1)
SKILL.md
1.4 KB
---
name: stakeholder-ops
description: Use to coordinate approvals, communications, and accountability across
  teams for feedback programs.
---

# Stakeholder Operations Guide Skill

## When to Use
- Launching surveys, betas, or listening tours that require multi-team approvals.
- Routing insights to product, CS, marketing, and exec stakeholders with clear accountability.
- Ensuring follow-up communications and governance rituals stay on track.

## Framework
1. **Stakeholder Map** – list involved teams, decision rights, and expectations per stage.
2. **Approval Workflow** – define checkpoints (brief sign-off, launch approval, readout review) with timelines.
3. **Communication Plan** – specify audiences, channels, frequency, and owners for updates.
4. **Action Tracking** – set up shared trackers with status, blockers, and success metrics.
5. **Governance Rituals** – outline cadences (weekly syncs, monthly reviews) plus escalation paths.

## Templates
- RACI chart for research + activation workflows.
- Approval checklist with required artifacts (brief, QA results, comms plan).
- Meeting agenda + notes template to keep stakeholders aligned.

## Tips
- Keep stakeholder rosters fresh; note backups for vacations or org changes.
- Automate reminders linked to due dates via project/workflow tools.
- Pair with `insight-synthesis` outputs to ensure narrative consistency.

---

Overview

This skill coordinates approvals, communications, and accountability across teams for feedback programs. It provides a practical framework, templates, and operational guidance to route insights, manage sign-offs, and keep follow-up actions on track. Use it to reduce bottlenecks and ensure clear ownership across GTM, product, and ops stakeholders.

How this skill works

The skill inspects program requirements and generates a stakeholder map, approval workflow, communication plan, action tracker, and governance cadence. It produces RACI charts, approval checklists, and meeting agendas tailored to launches, surveys, betas, or listening tours. It can also suggest automation points for reminders and link outputs to insight synthesis artifacts to maintain narrative consistency.

When to use it

  • Launching surveys, betas, or customer listening tours that need multi-team approvals
  • Routing findings and recommendations to product, CS, marketing, and exec stakeholders with clear accountability
  • Coordinating readouts, launch approvals, and post-project follow-up actions
  • Setting up recurring governance rituals or escalation paths for feedback-driven initiatives

Best practices

  • Maintain a living stakeholder map with backups for vacations and org changes
  • Define clear approval checkpoints and required artifacts up front (brief, QA, comms plan)
  • Use shared action trackers with status, blockers, owners, and success metrics
  • Automate reminders tied to due dates using your project or workflow tool
  • Pair outputs with insight-synthesis templates to keep messaging consistent

Example use cases

  • Preparing a beta launch that needs legal, product, support, and marketing sign-offs
  • Running a customer feedback tour and routing insights to product and customer success with owners and deadlines
  • Coordinating a cross-functional readout and ensuring post-readout actions are tracked and closed
  • Establishing a monthly governance ritual to review research outcomes and escalation items

FAQ

What artifacts will the skill produce?

It generates a stakeholder map, approval workflow, communication plan, action tracker template, RACI, approval checklist, and meeting agenda/notes template.

How does it reduce approval bottlenecks?

By defining checkpoints, required artifacts, timelines, and owners up front, and by recommending automated reminders and escalation paths to keep approvals moving.