playbooks

home / skills / gtmagents / gtm-agents / usage-health-scorecard

usage-health-scorecard skill

/plugins/product-led-growth/skills/usage-health-scorecard

This skill helps you monitor activation, engagement, and monetization health across cohorts, surfacing alerts and owners to optimize product health.

npx playbooks add skill gtmagents/gtm-agents --skill usage-health-scorecard

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

Files (1)
SKILL.md
1.2 KB
---
name: usage-health-scorecard
description: Framework for monitoring activation, engagement, and monetization guardrails.
---

# Usage Health Scorecard Skill

## When to Use
- Tracking activation/retention metrics for self-serve and hybrid customer cohorts.
- Monitoring the impact of PLG experiments on core product health.
- Sharing health snapshots with product, growth, and CS leads.

## Framework
1. **Metric Groups** – activation, engagement, collaboration, monetization, support load.
2. **Segmentation** – persona, plan, cohort, region, product area.
3. **Thresholds** – traffic light ranges for each metric with warning/critical bands.
4. **Alerting** – notification rules for drops, anomalies, or experiment impacts.
5. **Action Registry** – log remediation steps, owners, due dates, and results.

## Templates
- Scorecard layout (metric, current, target, delta, owner).
- Dashboard wireframe with spark lines + annotations.
- Action tracker for follow-up tasks linked to health changes.

## Tips
- Pair with `launch-in-app-experiments` to watch guardrails post-launch.
- Include qualitative signals (support tags, NPS) to contextualize telemetry.
- Archive snapshots to tell longitudinal stories in QBRs.

---

Overview

This skill provides a production-ready framework for monitoring activation, engagement, and monetization guardrails across self-serve and hybrid customer cohorts. It delivers a consistent scorecard structure, segmentation guidance, and alerting patterns to help product, growth, CS, and revenue teams spot risks and prioritize remediation. The package includes templates for scorecards, dashboard wireframes, and an action registry to close the loop on issues.

How this skill works

The skill organizes metrics into core groups—activation, engagement, collaboration, monetization, and support load—and applies segmentation by persona, plan, cohort, region, and product area. It defines traffic-light thresholds (normal, warning, critical) per metric, wires up alerting rules for drops and anomalies, and records remediation in an action registry with owners and due dates. Templates produce a scorecard layout and dashboard wireframes so teams can rapidly deploy monitoring and share consistent health snapshots.

When to use it

  • Tracking activation and retention for self-serve or hybrid cohorts
  • Monitoring the impact of product-led growth (PLG) experiments on core health
  • Providing regular health snapshots to product, growth, and customer success leads
  • Detecting and responding to sudden drops in monetization or engagement
  • Preparing longitudinal narratives for quarterly business reviews

Best practices

  • Define metric groups and segmentation up front so comparisons are meaningful
  • Use traffic-light thresholds with explicit warning and critical bands per cohort
  • Combine quantitative telemetry with qualitative signals (support tags, NPS)
  • Archive periodic snapshots to show trends and experiment impact over time
  • Keep an action registry with owners, deadlines, and post-remediation outcomes

Example use cases

  • Daily scorecard email for growth and CS teams highlighting cohorts in warning or critical states
  • PLG experiment rollout with real-time alerts on activation drop-offs and rollback triggers
  • Revenue ops dashboard that ties monetization guardrails to expansion and churn signals
  • Post-incident review using archived scorecard snapshots to quantify customer impact
  • QBR slides built from exported scorecard snapshots showing trend and action history

FAQ

How do thresholds get set?

Set thresholds by cohort using historical baselines and business targets; use warning bands to prompt investigation and critical bands for immediate action.

Can I include qualitative signals?

Yes—include support tags, NPS, and qualitative feedback alongside telemetry to provide context and prioritize remediation.