playbooks

home / skills / gtmagents / gtm-agents / visualization-patterns

visualization-patterns skill

/plugins/analytics-pipeline-orchestration/skills/visualization-patterns

This skill helps design dashboards and narratives for GTM stakeholders by applying visualization patterns and accessibility guidelines.

npx playbooks add skill gtmagents/gtm-agents --skill visualization-patterns

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

Files (1)
SKILL.md
1.2 KB
---
name: visualization-patterns
description: Use when designing dashboards, reports, and narratives for GTM stakeholders.
---

# Analytics Visualization Patterns Skill

## When to Use
- Planning a new dashboard or updating existing visualizations.
- Coaching teams on self-serve analytics adoption.
- Auditing visual design, accessibility, and narrative clarity.

## Framework
1. **Audience & Story** – clarify persona, decision cadence, and key questions.
2. **Layout & Hierarchy** – organize tiles by funnel (overview → drill-down → diagnostic), highlight KPIs.
3. **Chart Selection** – match metric type to chart (trend, composition, comparison, distribution).
4. **Accessibility** – color contrast, labels, tooltips, mobile/responsive considerations.
5. **Narrative & Actions** – annotate insights, embed CTA buttons or playbook links.

## Templates
- Dashboard wireframe grid with KPI slots.
- Metric dictionary (definition, source, owner, refresh schedule).
- Adoption checklist (stakeholder review, enablement session, feedback form).

## Tips
- Keep hero KPIs at top-left with trend vs target.
- Use consistent color palettes for good/bad variance.
- Embed documentation or Loom walkthroughs directly in BI tool when possible.

---

Overview

This skill provides a production-ready set of visualization patterns for designing dashboards, reports, and narratives aimed at GTM stakeholders. It standardizes layout, chart choice, accessibility, and storytelling so analytics deliver clear decisions and actions. Use it to accelerate dashboard design, improve adoption, and reduce revision cycles.

How this skill works

The skill guides you through a practical framework: define the audience and decision cadence, structure layout by funnel (overview → drill-down → diagnostic), and select charts that match metric types. It includes templates for dashboard wireframes, a metric dictionary, and an adoption checklist, plus concrete tips for KPI placement, color conventions, and embedding documentation.

When to use it

  • Planning a new dashboard or redesigning an existing report for GTM teams
  • Coaching sales, marketing, or customer success teams on self-service analytics
  • Auditing dashboards for visual clarity, accessibility, and narrative flow
  • Preparing stakeholder reviews or enabling adoption sprints
  • Defining metric ownership, refresh cadence, and data provenance

Best practices

  • Start with audience and story: clarify persona, decision cadence, and top questions
  • Place hero KPIs top-left with trend vs. target and clear context
  • Organize tiles by funnel: overview → drill-down → diagnostic for fast root-cause work
  • Match chart type to metric: trend, composition, comparison, or distribution
  • Ensure accessibility: color contrast, labels, tooltips, and mobile responsiveness

Example use cases

  • Design an executive revenue dashboard that highlights weekly trends and top drivers
  • Create a campaign performance report for marketing with clear attribution and lift visuals
  • Build a customer health view for success managers with risk indicators and drill-downs
  • Audit an existing BI workspace to improve consistency, documentation, and adoption
  • Run an enablement session using the adoption checklist and embedded walkthroughs

FAQ

How do I choose the right chart for a metric?

Map metric intent to chart form: use line charts for trends, stacked bars or treemaps for composition, grouped bars for comparisons, and histograms or boxplots for distributions.

What belongs in a metric dictionary?

Include definition, data source, transformation logic, owner, refresh schedule, and any known caveats to ensure consistent interpretation.