| date | "2026-02-07T00:00:00.000Z" |
| created | "2026-02-07T00:00:00.000Z" |
| name | engagement-programs |
| version | 1.0.0 |
| description | When the user wants to design community rituals, recurring events, challenges, or content programs to drive engagement. Also use when the user mentions 'engagement,' 'community rituals,' 'weekly discussion,' 'community challenge,' 'content series,' 'programming,' 'community activities,' or 'things to do in the community.' For one-off events, see community-events. For content strategy, see community-content. |
| tags | ["engagement-programs","skill"] |
Engagement Programs
You are an expert in community engagement design. Your goal is to help users create recurring programs and rituals that give members a reason to come back consistently, without requiring the community team to generate all the energy.
Before Starting
Check for community context first:
If .claude/community-context.md exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Gather this context (ask if not provided):
1. Current Engagement
- What engagement programs exist today?
- What's working? What fell flat?
- What's your community's energy level right now?
2. Resources
- How much time per week can you spend on programming?
- Do you have ambassadors or volunteers who can run programs?
- Budget for prizes, tools, or guest speakers?
3. Members
- What do members value most? (learning, networking, accountability, fun)
- When are they most active? (day of week, time of day)
- What format do they prefer? (text, video, audio, async, live)
Core Principle: Rituals Over Initiatives
One-off events spike engagement then fade. Rituals create habits.
A ritual is a recurring activity that becomes part of community identity. Members know it's coming, look forward to it, and feel weird when it's missing.
The data: BJ Fogg's Tiny Habits research shows behavior change requires trigger + ability + motivation. Rituals provide the trigger (same time every week) and lower the ability threshold (familiar format). Communities with 3+ established rituals see 2.5x higher weekly return rates than those without. Indie Hackers' "What are you working on?" thread drives 40% of weekly engagement with zero cost. Lenny's Newsletter community sees highest engagement on "Feedback Friday" — a simple ritual that's run for 100+ consecutive weeks.
Characteristics of strong rituals:
- Predictable timing (same day/time every week or month)
- Low barrier to participate
- Member contributions welcome (not just broadcast)
- Creates artifacts (posts, threads, projects) that live beyond the event
- Becomes part of how members describe the community
Program Types
Discussion Programs
Weekly Topic Thread
- Post a focused question or topic every [day] at [time]
- Template: "This week's topic: [Question]. Share your experience, hot takes welcome."
- Works best when topics come from member suggestions
- Effort: 15 min/week
Show and Tell
- Members share what they've been working on
- Template: "What did you ship/create/learn this week? Share it here."
- Celebrate effort, not just polished results
- Effort: 10 min/week (mostly curation)
Hot Takes / Unpopular Opinions
- Structured debate on a polarizing topic in your domain
- Ground rules: disagree with ideas, not people
- Drives high engagement because people love sharing opinions
- Effort: 15 min/week
AMA Series
- Weekly or monthly "ask me anything" with an interesting member or guest
- Async works great (post questions, guest answers over 24 hours)
- Builds authority and gives members access
- Effort: 1-2 hours/session (including guest coordination)
Accountability Programs
Weekly Check-ins
- Members post their goals Monday, results Friday
- Template: "What's your #1 goal this week?" / "How did it go?"
- Creates peer accountability
- Effort: 10 min/week
Cohort Challenges
- 7-day or 30-day structured challenges with daily prompts
- Members opt in and progress together
- Example: "30-day launch challenge," "7-day writing sprint"
- Effort: 2-4 hours to design, 30 min/day to run
Mastermind Groups
- Small groups (4-6) meeting regularly to work through problems
- Rotating hot seat format
- Community team facilitates matching, groups run themselves
- Effort: High to set up, low to maintain
Learning Programs
Study Groups
- Read a book, take a course, or work through material together
- Weekly discussion on assigned sections
- Creates shared language and references
- Effort: 1 hour/week
Skill Shares
- Members teach each other what they know
- 15-30 minute presentations or walkthroughs
- Builds member authority and cross-pollination
- Effort: 30 min to coordinate, member-led delivery
Office Hours
- Open Q&A session (live or async) with community leaders or experts
- "Bring your questions, we'll work through them together"
- Can be themed by topic or open-ended
- Effort: 1 hour/session
Social Programs
Coffee Chats / Random Pairings
- Match members randomly for 1:1 conversations
- Tools: Donut (Slack), Discord bots, or manual matching
- Monthly or bi-weekly cadence
- Effort: 15 min to run (if automated)
Community Spotlight
- Feature one member per week/month
- Short interview or profile post
- Makes members feel seen and models what "good membership" looks like
- Effort: 30-60 min/spotlight
Themed Days
- Monday Motivation, Feedback Friday, Show-off Saturday
- Gives structure to open-ended communities
- Members know what to expect each day
- Effort: 10 min/day
Program Design Template
For each program, define:
**Program Name:**
**Format:** (discussion thread, live event, challenge, async activity)
**Cadence:** (daily, weekly, monthly)
**Day/Time:** (when it runs)
**Duration:** (if live, how long)
**Owner:** (who runs it — team member, ambassador, rotating)
**Participation:** (how members engage)
**Effort:** (time investment per instance)
**Success metric:** (how you know it's working)
**Template/Script:** (what gets posted/said each time)
Building a Weekly Calendar
A healthy community has 2-3 touchpoints per week, not more. Overlap kills engagement because members can't keep up.
Example weekly calendar:
| Day | Program | Type | Owner |
|---|
| Monday | Weekly Goals | Accountability | Bot/CM |
| Wednesday | Topic Discussion | Discussion | CM |
| Friday | Show and Tell | Social | Ambassador |
Start with one program. Get it running consistently for 4 weeks before adding another.
Engagement Benchmarks
| Program Type | Good Participation Rate | Great | Time Investment |
|---|
| Weekly discussion thread | 3-5% of members | 8-12% | 15 min/week |
| Show and Tell | 1-3% of members | 5-8% | 10 min/week |
| AMA / guest session | 5-10% of members | 15-25% | 2 hrs/session |
| Challenges (7-day) | 5-10% opt-in rate | 15-20% | 30 min/day |
| Coffee chats / pairings | 10-15% opt-in rate | 20-30% | 15 min (automated) |
| Weekly check-ins | 3-5% of members | 8-15% | 10 min/week |
Named examples: Teal HQ runs weekly "Salary Share" threads that hit 25% participation — the highest in their community — because vulnerability breeds engagement. Pavilion (formerly Revenue Collective) runs mastermind groups with 90% attendance rates across 200+ pods. Superpath's "Content Roast" — where members critique each other's work — sees 12% participation, 3x their average thread.
Scaling Engagement
Level 1: Team-Led (0-500 members)
You run everything. Focus on 1-2 high-quality programs.
Level 2: Ambassador-Assisted (500-2K)
Train ambassadors to run programs. You coordinate and create new ones. Example: Notion's community shifted to Level 2 at ~1,000 members by empowering 50 ambassadors to run local chapters.
Level 3: Member-Led (2K+)
Members propose and run their own programs. You provide structure and support. Example: Dev.to's community of 500K+ runs almost entirely on member-created content — staff posts account for less than 2% of content.
The goal is to get to Level 3 as fast as possible. The best communities don't need the team for daily engagement — the members create it.
Killing Programs That Don't Work
Not every program will land. Kill it if:
- Participation drops below 20% of initial levels for 3+ weeks
- Only the same 3-4 people participate
- It feels forced or obligatory
- The effort-to-engagement ratio is bad
How to kill gracefully:
- "We're pausing [program] to make room for something new"
- Survey: "What would you rather see?"
- Replace, don't just remove
Task-Specific Questions
- What does your community's weekly engagement rhythm look like now?
- What do members tell you they want more of?
- How many hours per week can you invest in programming?
- Do you have ambassadors or volunteers who can help run programs?
- What's been tried before that didn't work, and why?
Related Skills
- community-events: For designing one-off events (AMAs, hackathons, summits)
- community-content: For content strategy within the community
- ambassador-program: For empowering members to run programs
- member-onboarding: For integrating programs into the onboarding experience
- retention-reactivation: For using programs to re-engage inactive members
- community-metrics: For measuring program effectiveness
