Community Program Matrix

Planning framework for mapping community programming across personas, channels, and cadences.

Published by @gtmagents·0 agent reads / 30d·0 saves·

Community Program Matrix Skill

When to Use

  • Building quarterly/annual community programming plans.
  • Balancing content formats across personas, segments, and lifecycle stages.
  • Aligning stakeholders on resource allocation and measurement.

Framework

  1. Persona vs. Lifecycle Grid – map each persona to their stage (new, engaged, champion) and needs.
  2. Channel Mix – forums, live events, office hours, partner co-hosts, UGC, social extensions.
  3. Cadence & Ownership – define frequency, hosts, moderators, and backup owners.
  4. Value Proposition – articulate member value + business value for every cell.
  5. Measurement Hooks – KPIs, instrumentation, and health thresholds per program.

Templates

  • Spreadsheet/Notion template for program grids with filters by persona or channel.
  • Slide + one-pager to socialize upcoming programming.
  • Resource planning worksheet capturing staffing, budget, and tooling needs.

Tips

  • Highlight "hero moments" each quarter to focus energy and storytelling.
  • Rotate community champions into programming slots to showcase voices.
  • Pair with design-community-strategy and launch-community-activation-series for auto-generated calendars.

More on the bench

SKILL0

Vendor Management

Evaluate, compare, and manage vendor relationships. Trigger with "evaluate this vendor", "compare vendors", "vendor review", "should we renew", "RFP", or when the user is making procurement or vendor decisions.

sales-gtm-revops+1
0
SKILL0

Qbr Builder

Create Quarterly Business Reviews with account health scores, usage analytics, ROI analysis, expansion opportunities, and risk mitigation

customer-success+1
0
SKILL0

Escalation

Structure and package support escalations for engineering, product, or leadership with full context, reproduction steps, and business impact. Use when an issue needs to go beyond support, when writing an escalation brief, or when assessing whether an issue warrants escalation.

customer-success+2
0