When to activate
Quarterly (start 4 weeks before quarter) or annually (Q4 planning). Input: product roadmap, previous quarter's sentiment analysis, AMA attendance trends, industry event calendar, team capacity. Output informs content scheduling, promotion strategy, and member engagement targets.
When NOT to use
Not for reactive response to trending topics (use crisis-responder for that). Not as a rigid mandate; flexibility is essential because community interests evolve. Not to over-schedule events that burn out team capacity.
Planning Checklist
Execute in order:
- Gather inputs — Collect: product roadmap (features, timelines), past quarter sentiment data, previous event attendance rates, team capacity (hours/week available), industry calendar (conferences, seasonal trends), member-requested topics
- Identify content pillars — 3–5 core themes aligned with product and community values (e.g., best practices, customer stories, industry news, product updates, community wins)
- Schedule feature announcements — Map product launches to announcement dates (typically launch + 1 week for beta, 2 weeks for GA). Build hype train: teaser → announcement → deep dive → office hours
- Plan AMA schedule — Target 2–4 AMAs/quarter. Invite product leaders, customers, or external experts. Schedule 3–4 weeks out for promotion. Book 1-hour slots + async Q&A window
- Identify seasonal moments — Look for holidays, industry milestones, annual events, and create tie-in content (e.g., "New Year new goals" challenge, "Year-in-review" thread)
- Create content calendar grid — Week-by-week breakdown: theme, primary content type (thread, AMA, poll, event), owner, promotion start date, success metric
- Build promotion timeline — For each major initiative: announce 3 weeks prior, reminder 1 week prior, daily reminder day-of, debrief post-event
- Estimate lift metrics — Based on past quarters, project: attendee count, engagement rate, new member signups, power user engagement
Content Pillar Examples
- Product Updates: New features, roadmap previews, beta launches
- Best Practices: How-to guides, framework discussions, tool recommendations
- Customer Stories: Member spotlights, wins, use cases, case studies
- Industry News: Curated news, trend analysis, thought leadership
- Community Wins: Member milestones, feature requests shipped, challenges completed
Calendar Template
# Content Calendar — Q3 2026
**Capacity:** 8 hours/week for content + moderation
**Key Goals:** 15% new member signup, 12% engagement rate, 3 major product launches
**Team:** [Names and responsibilities]
---
## July 2026
### Week 1 (Jul 1–7)
- **Theme:** Summer kickoff
- **Content:** "What are you building this summer?" thread
- **Event:** None
- **Owner:** [Name]
- **Promotion:** Auto-pin in #introductions
- **Metric:** 50+ new threads by Jul 7
### Week 2 (Jul 8–14)
- **Theme:** Feature spotlight
- **Content:** Beta launch announcement for [Feature X]
- **Event:** AMA with product lead — Thursday 2pm ET
- **Owner:** [Name]
- **Promotion:**
- Announce beta — Jul 8
- AMA reminder — Jul 10, Jul 12, Jul 14 morning
- **Metric:** 100+ AMA attendees, 30 questions
### Week 3 (Jul 15–21)
- **Theme:** Best practices
- **Content:** "Getting started with [Feature X]" guide thread
- **Event:** None
- **Owner:** [Name]
- **Promotion:** Feature in newsletter, pin in #announcements
- **Metric:** 50+ saves, 10+ thank-you reactions
### Week 4 (Jul 22–31)
- **Theme:** Community wins + Holiday pivot
- **Content:** Member spotlight: [User X's story]
- **Event:** None
- **Owner:** [Name]
- **Promotion:** Direct DM to featured member's network
- **Metric:** 5+ new connections made
---
## August 2026
[Similar structure for remaining weeks]
---
## Success Metrics by Content Type
| Content Type | Target Engagement | Success Threshold |
|---|---|---|
| **Feature Announcement** | 200+ views, 40+ reactions, 20+ replies | >30% of active members see it |
| **AMA** | 80+ attendees, 30+ questions | >90% of questions answered |
| **Spotlight** | 150+ views, 30+ reactions | 1 new connection per spotlight |
| **Guide/How-To** | 120+ views, 25+ saves | Linked in 3+ future threads |
| **Poll** | 200+ votes | >40% of WAU participate |
---
## Promotion Timeline Template
For each initiative:
- **T-3 weeks:** Announce at community meeting or in #announcements. Share guest name/topic. Invite early registration.
- **T-2 weeks:** Send email to member segment (e.g., "Interested in X? Don't miss this AMA")
- **T-1 week:** Reminder post in main channel. Include registration link.
- **T-2 days:** Final reminder in #announcements
- **T-1 day:** Daily post with time zone conversions
- **T-0:** Live event + async Q&A window
- **T+1:** Debrief + recording + key takeaways thread
---
## Example: Q3 2026 Calendar Snapshot
### Major Initiatives
| Initiative | Type | Date | Owner | Target Attendees | Promo Start |
|---|---|---|---|---|---|
| Feature X launch AMA | AMA | Jul 11 | [PM name] | 100+ | Jun 20 |
| Customer story: [Company] | Spotlight | Jul 28 | [CM name] | 150+ views | Jul 14 |
| Getting started guide | Guide | Aug 4 | [Name] | 50+ saves | Jul 21 |
| Feature Y beta launch | Announcement | Aug 18 | [PM name] | 200+ views | Jul 28 |
| Annual community survey | Poll | Sep 10 | [CM name] | 40% participation | Aug 20 |
| Year-end planning workshop | Workshop | Sep 24 | [Name] | 75+ attendees | Sep 1 |
---
1---2name: content-calendar-planner3description: Drafts quarterly or annual content calendar aligned with product roadmap, community interests, and seasonal engagement patterns. Includes AMA dates, event themes, feature announcements, and content pillars. Returns interactive calendar in markdown with promotion timeline.4---56## When to activate78Quarterly (start 4 weeks before quarter) or annually (Q4 planning). Input: product roadmap, previous quarter's sentiment analysis, AMA attendance trends, industry event calendar, team capacity. Output informs content scheduling, promotion strategy, and member engagement targets.910## When NOT to use1112Not for reactive response to trending topics (use crisis-responder for that). Not as a rigid mandate; flexibility is essential because community interests evolve. Not to over-schedule events that burn out team capacity.1314## Planning Checklist1516Execute in order:17181. **Gather inputs** — Collect: product roadmap (features, timelines), past quarter sentiment data, previous event attendance rates, team capacity (hours/week available), industry calendar (conferences, seasonal trends), member-requested topics192. **Identify content pillars** — 3–5 core themes aligned with product and community values (e.g., best practices, customer stories, industry news, product updates, community wins)203. **Schedule feature announcements** — Map product launches to announcement dates (typically launch + 1 week for beta, 2 weeks for GA). Build hype train: teaser → announcement → deep dive → office hours214. **Plan AMA schedule** — Target 2–4 AMAs/quarter. Invite product leaders, customers, or external experts. Schedule 3–4 weeks out for promotion. Book 1-hour slots + async Q&A window225. **Identify seasonal moments** — Look for holidays, industry milestones, annual events, and create tie-in content (e.g., "New Year new goals" challenge, "Year-in-review" thread)236. **Create content calendar grid** — Week-by-week breakdown: theme, primary content type (thread, AMA, poll, event), owner, promotion start date, success metric247. **Build promotion timeline** — For each major initiative: announce 3 weeks prior, reminder 1 week prior, daily reminder day-of, debrief post-event258. **Estimate lift metrics** — Based on past quarters, project: attendee count, engagement rate, new member signups, power user engagement2627## Content Pillar Examples2829- **Product Updates:** New features, roadmap previews, beta launches30- **Best Practices:** How-to guides, framework discussions, tool recommendations31- **Customer Stories:** Member spotlights, wins, use cases, case studies32- **Industry News:** Curated news, trend analysis, thought leadership33- **Community Wins:** Member milestones, feature requests shipped, challenges completed3435## Calendar Template3637```markdown38# Content Calendar — Q3 20263940**Capacity:** 8 hours/week for content + moderation41**Key Goals:** 15% new member signup, 12% engagement rate, 3 major product launches42**Team:** [Names and responsibilities]4344---4546## July 20264748### Week 1 (Jul 1–7)49- **Theme:** Summer kickoff50- **Content:** "What are you building this summer?" thread51- **Event:** None52- **Owner:** [Name]53- **Promotion:** Auto-pin in #introductions54- **Metric:** 50+ new threads by Jul 75556### Week 2 (Jul 8–14)57- **Theme:** Feature spotlight58- **Content:** Beta launch announcement for [Feature X]59- **Event:** AMA with product lead — Thursday 2pm ET60- **Owner:** [Name]61- **Promotion:** 62 - Announce beta — Jul 863 - AMA reminder — Jul 10, Jul 12, Jul 14 morning64- **Metric:** 100+ AMA attendees, 30 questions6566### Week 3 (Jul 15–21)67- **Theme:** Best practices68- **Content:** "Getting started with [Feature X]" guide thread69- **Event:** None70- **Owner:** [Name]71- **Promotion:** Feature in newsletter, pin in #announcements72- **Metric:** 50+ saves, 10+ thank-you reactions7374### Week 4 (Jul 22–31)75- **Theme:** Community wins + Holiday pivot76- **Content:** Member spotlight: [User X's story]77- **Event:** None78- **Owner:** [Name]79- **Promotion:** Direct DM to featured member's network80- **Metric:** 5+ new connections made8182---8384## August 20268586[Similar structure for remaining weeks]8788---8990## Success Metrics by Content Type9192| Content Type | Target Engagement | Success Threshold |93|---|---|---|94| **Feature Announcement** | 200+ views, 40+ reactions, 20+ replies | >30% of active members see it |95| **AMA** | 80+ attendees, 30+ questions | >90% of questions answered |96| **Spotlight** | 150+ views, 30+ reactions | 1 new connection per spotlight |97| **Guide/How-To** | 120+ views, 25+ saves | Linked in 3+ future threads |98| **Poll** | 200+ votes | >40% of WAU participate |99100---101102## Promotion Timeline Template103104For each initiative:105106- **T-3 weeks:** Announce at community meeting or in #announcements. Share guest name/topic. Invite early registration.107- **T-2 weeks:** Send email to member segment (e.g., "Interested in X? Don't miss this AMA")108- **T-1 week:** Reminder post in main channel. Include registration link.109- **T-2 days:** Final reminder in #announcements110- **T-1 day:** Daily post with time zone conversions111- **T-0:** Live event + async Q&A window112- **T+1:** Debrief + recording + key takeaways thread113114---115116## Example: Q3 2026 Calendar Snapshot117118### Major Initiatives119120| Initiative | Type | Date | Owner | Target Attendees | Promo Start |121|---|---|---|---|---|---|122| Feature X launch AMA | AMA | Jul 11 | [PM name] | 100+ | Jun 20 |123| Customer story: [Company] | Spotlight | Jul 28 | [CM name] | 150+ views | Jul 14 |124| Getting started guide | Guide | Aug 4 | [Name] | 50+ saves | Jul 21 |125| Feature Y beta launch | Announcement | Aug 18 | [PM name] | 200+ views | Jul 28 |126| Annual community survey | Poll | Sep 10 | [CM name] | 40% participation | Aug 20 |127| Year-end planning workshop | Workshop | Sep 24 | [Name] | 75+ attendees | Sep 1 |128129---