SkillMedev Community Engagement Playbook
A course community exists for exactly two outputs: completion and testimonials. Students who feel seen finish, finished students get results, and results become the proof that sells the next cohort. The costly mistake is treating community as a feature to bolt on - an empty Slack nobody posts in signals a dead course louder than no community at all, and an unbudgeted community quietly consumes the creator's production time until the next launch slips.
This skill runs after launch-email-sequence hands over the buyers, operates against the completion target set by course-outline-architect, and feeds its testimonial harvest back to course-sales-page's proof section. That loop - community to testimonials to sales page - is what makes the second launch outperform the first.
Worked example throughout: Dana, who just closed the "Notion OS for Consultants" launch ($297) with roughly 120 students from her 8,000-subscriber list, budgeting 5 hours a week for community.
Operating procedure
Step 1: Collect the inputs
- Student count and where the audience already hangs out (check where they replied from during the launch; ask 5 buyers directly if unknown).
- The course's quick-win moment and module milestones from course-outline-architect.
- The creator's honest weekly hours available. Default and hard cap: 5.
- Course length and the completion target - this pack designs for 35 percent or better against the 10 to 15 percent industry average.
Step 2: Choose the platform - where students already are beats features
Rank candidates by one question: which platform are these students already opening daily? A feature-rich community platform they must remember to visit loses to a mediocre one already in their dock. Decision rules:
- Students live in Slack for work (Dana's consultants do): Slack or a Slack-adjacent tool wins, features be damned.
- Audience is creators/gamers already on Discord: Discord.
- Buying a dedicated tool (Circle, Skool, and kin) is right only when the cohort is large enough to sustain its own gravity - under roughly 50 active students, a dedicated platform usually reads as empty.
- Never more than one platform. Splitting 120 students across two places produces two ghost towns.
Dana picks Slack: her consultants are in it all day, and an empty-feeling Circle space would cost more momentum than Slack's weaker course features.
Step 3: Run the onboarding ritual
The first 48 hours after purchase decide whether a student ever posts. Buyers arrive from launch-email-sequence into: a welcome email, an introduce-yourself prompt, and a first-action nudge pointing at the module-1 quick win (Dana's: the working dashboard in 20 minutes).
The introduce-yourself template - structured prompts get 3-4x the responses of "say hi!":
Welcome! Copy this, fill it in, post it in #introductions:
1. Name + what kind of consulting you do
2. Your current setup, honestly (how many tools? paper? chaos?)
3. The ONE thing you want working by the end of this course
4. Something you're good at that has nothing to do with work
Dana's example:
1. Dana - productivity consulting for solo consultants
2. Recovering 6-tool juggler: Notion, Trello, Docs, Sheets, Calendly, Airtable
3. Client onboarding in under a day, every time
4. I can identify most birds in New England by song
The creator (or a student moderator, later) replies to every introduction within 24 hours during launch month. Question 4 is not filler - it is what other students reply to, and peer replies, not creator replies, are what make a community self-sustaining.
Step 4: Install the weekly cadence
Three recurring beats, same day and time every week, so students stop wondering whether anything is happening:
- Office hours - 45 minutes live, weekly during the cohort's first 8 weeks, biweekly after. Collect questions in a thread beforehand so silence can't kill the session; record and post every one.
- Wins thread - Monday: "What's one thing that worked this week - however small?" The creator seeds it with a student win spotted during the week. This thread is also the testimonial radar (Step 6).
- Accountability check - Thursday: "Which lesson are you on, and what's the one action you'll finish by Sunday?" This maps directly to the one-action-per-lesson design from course-outline-architect, and its silent students are the churn early-warning list.
Step 5: Enforce the creator-time budget - 5 hours a week, capped
Community effort past about 5 hours a week cannibalizes course improvement and the next launch. Dana's allocation:
Office hours (run + prep) 1.5 hrs
Replies, batched 2x/day 30 min 1.0 hr (never ambient all-day checking)
Cadence posts + win-spotting 1.0 hr
Testimonial harvest + DMs 0.5 hr
Slack (buffer / member care) 1.0 hr
Total 5.0 hrs
Leverage tactics, in deployment order: (1) batch replies to two windows a day - ambient checking is how 5 hours becomes 20; (2) turn every question answered twice into a pinned FAQ post; (3) at month two, invite 2-3 of the most active students to be moderators with a real perk (free next course, or a lifetime license); (4) let non-urgent threads sit 24 hours - peer answers appearing before creator answers is the health signal, not a failure.
Step 6: Harvest testimonials at the moments they occur
Testimonials are perishable - enthusiasm peaks at the moment of a win and decays within days. Watch four harvest moments:
- The module-1 quick win (Dana's 20-minute dashboard) - first-impression quotes.
- The mid-course milestone (Dana's Module 4: a client portal live for a real client) - concrete-result quotes.
- Course completion - transformation-story quotes.
- Any unprompted wins-thread post with a number in it ("saved 4 hours this week") - the strongest of all.
At each moment, act within 48 hours: a short DM - "That win you posted is exactly what future students need to hear. Up for a 15-minute chat about it?" - then route the conversation itself to testimonial-capture-interview, which owns the questions, consent, and formats. Deliver finished testimonials to course-sales-page's proof section before the next launch. Target from a 120-student cohort: 10-15 usable testimonials, of which 3-5 carry specific numbers.
Deliverable
A one-page community operating plan: the platform decision with its reasoning, the onboarding ritual with the introduce-yourself template, the three-beat weekly cadence with days and times, the 5-hour time budget with allocations and leverage tactics, and the four testimonial-harvest moments with the DM script and the testimonial-capture-interview handoff.
Do NOT
- Do not pick a platform for its features over its ambient presence in students' lives. The best platform is the one already open.
- Do not launch a community with no cadence and hope conversation emerges. Empty communities actively damage the course's perceived value.
- Do not let community time float uncapped. Past 5 hours a week it is eating the next launch.
- Do not answer every question instantly and forever. Creator omnipresence trains dependence and prevents the peer-to-peer culture that makes the community durable.
- Do not wait until launch prep to ask for testimonials. Months-old enthusiasm produces vague praise; harvest within 48 hours of the win.
- Do not run the testimonial interview ad hoc in DMs - route it to testimonial-capture-interview so consent and specifics are captured properly.
Quality bar
- One platform, chosen by where students already are, with the reasoning written down.
- Every new student gets the structured introduce-yourself prompt and a reply within 24 hours during launch month.
- Three weekly beats scheduled at fixed times; office hours never cancelled silently.
- The time budget totals 5 hours or less and names at least two leverage tactics in use.
- All four harvest moments have an owner and the 48-hour DM rule; testimonials with numbers flow to course-sales-page before the next launch.
- Completion is tracked against the 35 percent target, with the accountability thread as the early-warning system.
Escalation and routing
The testimonial conversation, consent, and formats: testimonial-capture-interview. Structural fixes when completion lags despite an active community (lessons too long, milestones unclear): course-outline-architect. Quizzes that give the accountability check teeth: quiz-generator. Turning community proof into the next campaign: course-sales-page and launch-email-sequence.