home / skills / gtmagents / gtm-agents / executive-kpi-briefings

executive-kpi-briefings skill

safe

/plugins/business-intelligence/skills/executive-kpi-briefings

This skill helps executives and teams generate concise weekly KPI briefs from BI insights, outlining drivers, implications, actions, and owners.

npx playbooks add skill gtmagents/gtm-agents --skill executive-kpi-briefings

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

Files (1)

SKILL.md

1.1 KB

---
name: executive-kpi-briefings
description: Template pack for summarizing BI insights for ELT/board stakeholders.
---

# Executive KPI Briefings Skill

## When to Use
- Preparing weekly/monthly ELT updates with BI insights.
- Translating dashboards into succinct decision memos.
- Coordinating follow-up actions after KPI reviews.

## Framework
1. **Headline & Signal** – lead with KPI delta, direction, and confidence.
2. **Driver Analysis** – highlight top drivers, segments, or anomalies.
3. **Implications** – spell out impact on goals, customers, or investments.
4. **Actions & Owners** – list next steps, DRIs, due dates, and guardrails.
5. **Appendix** – link to dashboard tabs, methodology, and deeper data.

## Templates
- 1-page KPI memo (headline, context, actions).
- Slide template for ELT/board readouts.
- Follow-up tracker with ownership + status fields.

## Tips
- Keep narratives under 200 words unless deeper context is requested.
- Pair with `build-exec-dashboard` and `plan-bi-roadmap` for consistent storytelling.
- Capture questions/decisions in a log to feed future prioritization.

---

Overview

This skill provides a production-ready template pack for summarizing BI insights into concise ELT and board-ready briefings. It turns dashboard signals into decision-focused memos, slide readouts, and follow-up trackers to help leadership act faster. The pack is optimized for revenue, GTM, and customer success metrics with reusable structures and clear ownership fields.

How this skill works

The skill inspects KPI deltas, segment drivers, and anomaly signals and organizes them into a five-part briefing: Headline & Signal, Driver Analysis, Implications, Actions & Owners, and Appendix. It produces a 1-page memo, a slide readout, and a follow-up tracker populated with proposed owners, due dates, and guardrails. Templates are designed to be paired with execution dashboards and BI roadmaps for consistent storytelling.

When to use it

Weekly or monthly ELT KPI updates to summarize BI trends.
Translating dashboards into one-page decision memos for board meetings.
Preparing slide readouts for executive review or investor updates.
Coordinating follow-up actions and owner tracking after KPI reviews.
Documenting decisions and questions to prioritize future BI work.

Best practices

Lead with a clear headline stating the KPI delta, direction, and confidence level.
Limit the narrative to ~200 words for the main memo; use appendix for detail.
Highlight top 2–3 drivers or segments rather than full metric dumps.
Always attach a follow-up tracker with DRIs, due dates, and success guardrails.
Link back to source dashboards and methodology in the appendix for auditability.

Example use cases

Weekly revenue brief: headline delta, driver breakdown by region, implications for quota coverage, next steps with owners.
Churn signal memo: summarize customer cohorts causing lift, root-cause hypotheses, mitigation actions, and data links.
Product launch readout: capture early adoption KPIs, top performing channels, recommended reallocation of GTM spend.
Board slide pack: 3-slide executive summary, supporting appendix links, and a tracker for board requests.

FAQ

How long should the executive memo be?

Keep the core memo under 200 words; include deeper analysis in an appendix if needed.

What fields should the follow-up tracker include?

Include action, DRI (directly responsible individual), due date, status, and guardrail/acceptance criteria.