Event Programming Reference Card
Paid community event programming — event format selection matrix, frequency decision table, contribution structure checklist, first-30-day programming arc, and event measurement metrics
This page is a structured reference card for paid community operators building or auditing their event programming. It covers: an event format selection matrix for six formats — structured peer review, co-working session, themed expert-member exchange, webinar-style presentation, operator Q&A, and social event without contribution structure — mapping each to what it produces (peer relationships vs. content consumption), required contribution structure, relationship-formation mechanism, session design requirements, and which member lifecycle stage each format serves best; an event frequency decision table for three cadence types — two-to-three per month, weekly, and monthly or less — with culture type produced, attendance pattern, member familiarity accumulation rate, between-session contact rate, content vs. relationship primary driver, and churn risk at 90 days; a contribution structure checklist for four session components — pre-session preparation requirement, structured contribution opening, peer-to-peer interaction format, and specific commitment closing — with what each component does, the failure version most operators actually build, the norm it establishes, and the behavioral signal that indicates it is working; a first-30-day programming arc for three components with what to do, when in the 30 days, what it produces, the failure version, and success metric; and an event measurement table for three behavioral metrics with measurement method, healthy benchmark, at-risk threshold, what below-threshold indicates about which session design component is failing, and the highest-leverage intervention for each. For the conceptual framework behind these tables — why events as a product produce audience culture rather than peer culture, the distinction between relationship-producing and content-producing session formats, and how event frequency determines whether a community builds a relationship retention moat or a content-delivery subscription — see the companion post: Paid community event programming: designing sessions that build peer relationships. This card is for the operator who understands the reasoning and needs the format matrix, frequency table, contribution structure checklist, first-30-day arc, and measurement metrics in quick-reference form.
TL; DR
Most paid community operators treat events as the main product when they are actually the delivery mechanism for the community’s primary product — peer relationships and expertise exchange. The distinction determines session design in ways that compound over time: a community that treats events as the product designs them to maximize attendance and content quality; a community that treats events as the relationship delivery mechanism designs them to maximize member-to-member interaction, contribution activation, and commitment signaling. Table 1 gives the event format selection matrix for six formats — which ones produce peer relationships and which produce content without relationships. Table 2 gives the frequency decision table showing how cadence type produces culture type. Table 3 gives the contribution structure checklist for the four session components that distinguish relationship-producing sessions from passive attendance. Table 4 gives the first-30-day programming arc for new-member integration. Table 5 gives the event measurement framework for three behavioral metrics. If you can only do one thing: run one session with a structured contribution opening — the 15–20 minutes at the start of the session where every member’s prepared contribution is made visible to the group before open discussion begins. That single structural change is the highest-leverage modification to session design because it establishes the session norm that makes everything else in Tables 3–5 possible.
Table 1 — Event format selection matrix
Six formats organized by what each produces: the three that consistently produce peer relationships (green rows) and the three that produce content consumption without peer-relationship formation (remaining rows). The distinction is structural, not motivational — the three relationship-producing formats require a contribution structure that makes every member’s work visible to specific peers before open discussion begins; the three content-producing formats have no such requirement and therefore have no mechanism for peer-relationship formation.
Design principle: The relationship-formation mechanism in each format operates before the session opens, not during it. Pre-session preparation is what makes the session produce peer relationships rather than parallel consumption of the same content by individual members who happen to be in the same room.
| Event format | What it produces | Required contribution structure | Relationship-formation mechanism | Session design requirements | Member lifecycle stage it serves best |
|---|---|---|---|---|---|
| Structured peer review | Peer relationships: each reviewer’s work becomes visible to the group; each member-under-review receives expert observations from peers rather than operator alone; mutual intellectual investment forms before the session begins | Pre-session submission (member shares work sample 48–72h in advance); each attendee prepares specific observations before the session opens; no submission = no contribution opening slot | Mutual intellectual investment — the reviewer has studied the member’s work and the member has studied the reviewer’s observations; the relationship is formed through this pre-session labor exchange before the first word is spoken in the session | ≤6 members per session; designated reviewer for each submitted work; 15-minute per-submission format (5 min presenter context, 10 min structured peer response); no open discussion until all reviewers have spoken; operator holds open discussion to member-to-member exchange | Days 30–90: after activation but while still consolidating peer relationships; high-churn-risk members at days 45–60 benefit most because the format creates a named peer relationship in a single session |
| Co-working session | Peer relationships through shared context of each other’s current professional situation; familiarity accumulates across sessions as members develop knowledge of each other’s specific work and constraints | Each member arrives with a specific piece of work in progress and a 2-minute check-in prepared (what they are working on, where they are stuck, what they want to move in the session); no work in progress = no check-in slot | Repeated exposure to peers’ professional situations in motion — the specific work, the specific constraint, and the specific resolution at the session close; this builds mutual knowledge of each other’s professional situation that generalizes beyond the session | 45–75 minutes; structured 2-minute check-in round at open (all members speak); 30–45 minutes work block (silent or low-voice); 5-minute close round (one update per member on what moved); no unstructured chat during work block; operator does not facilitate during work block | Days 14–60 for early relationship formation; ongoing for members at any stage — the format scales because the contribution structure is low-stakes (arriving with work is the only requirement) |
| Themed expert-member exchange | Shared reference points: members observe applied expertise in response to their specific situations and discuss together afterward; produces relationship through shared intellectual experience rather than through direct member-to-member labor exchange | Pre-session: members submit specific situations (not general questions) for expert response; expert selects 3–5 for the session; submitting members prepare to add context when their situation is addressed; non-submitters prepare one observation on each selected situation | Members observe each other’s professional situations described to an expert and the expert’s specific response to each; the shared observation creates common intellectual ground between members who otherwise know nothing specific about each other’s work | Expert responds to submitted situations only (no prepared presentation); 7–10 minutes per situation (expert response + member context + group observation); 15-minute open group discussion at close; no general Q&A format; operator explicitly hands closing discussion to member-to-member exchange | All lifecycle stages; most valuable in days 14–45 for exposing new members to peer situations and providing early contribution structure that does not require prior peer relationships |
| Webinar-style presentation | Content consumption: individual learning without peer-to-peer relationship formation; members receive the same content independently and have no mechanism to develop mutual knowledge of each other’s professional situations | None required: contribution is optional (live chat participation, Q&A at end); most members attend passively; the format creates no accountability for preparation | None: members observe the same content individually; no mechanism creates mutual knowledge between members; post-session peer contact requires a relationship that the format itself does not produce | Presentation format with operator-or-expert speaker; Q&A at end; no member contribution required before or during; optional live chat; session can scale to any number of attendees without format modification | Appropriate for prospects (before join) and days 0–14 when members have not yet established peer relationships; not appropriate as the primary recurring format for established members where peer-relationship retention is the goal |
| Operator Q&A | Content consumption and operator-member relationship strengthening; does not produce peer-to-peer relationships; members who attend repeatedly develop a stronger relationship with the operator, not with each other | None required: member questions are optional and reactive; the session can proceed without any member questions if the operator has prepared content; no preparation accountability | None between members: operator-member relationship is the only relationship the format enables; members who attend the same operator Q&A sessions do not develop mutual knowledge of each other’s professional situations | Operator responds to questions submitted in advance or asked live; open format; no member preparation required or requested; participation depends entirely on member willingness to ask publicly | Appropriate as supplement at any stage; highest value in days 0–30 when members have not yet identified which community relationships are most useful to them; not appropriate as primary recurring format for a community with peer-relationship retention goals |
| Social event without contribution structure | Pleasant experience; proximity familiarity if members attend repeatedly; does not produce the mutual intellectual investment that becomes peer relationship; social events produce liking without the specificity that makes a peer relationship durable | None: participation is voluntary and unstructured; the absence of contribution structure is the defining characteristic of the format; any contribution structure added converts it to a different format type | Proximity without shared work context: members meet but have no mechanism to develop mutual knowledge of each other’s professional situations; liking without specificity produces acquaintance, not peer relationship | Optional participation; unstructured; any time format; scales to any size; no session design requirements because there is no contribution structure to design | Supplementary at any stage; useful for new members (days 0–14) needing low-stakes exposure before contributing; not appropriate as the primary recurring format; the format’s absence of contribution structure is what makes it low-stakes and what prevents it from producing peer relationships |
Table 2 — Event frequency decision table
Three cadence types organized by what each produces in terms of community culture, member familiarity, and 90-day churn risk. The relationship between event frequency and culture type is causal rather than correlational: cadence determines how quickly peer familiarity accumulates between the same members, which determines whether between-session contact is natural (high familiarity) or forced (low familiarity), which determines whether renewal decisions are driven by peer relationships (not replicable elsewhere) or content quality (replicable by alternatives).
The compounding effect: Peer familiarity accumulates at a rate determined by how many times the same members attend the same session within a 60-day window. Weekly cadence produces higher total session count but lower familiarity per member pair because attendance concentration is lower. Two-to-three-per-month cadence produces lower total session count but higher familiarity per member pair because the same core attends consistently.
| Cadence type | Culture type produced | Attendance pattern | Member familiarity accumulation rate | Between-session contact rate | Content vs. relationship primary retention driver | Churn risk at 90 days |
|---|---|---|---|---|---|---|
| Two–three per month | Relationship culture: between-session familiarity accumulates fast enough to produce peer contact without the attendance-dilution effect of weekly cadence; members who attend both sessions in a given month see the same peers twice in 30 days | Consistent per member: fewer sessions means members attend a higher proportion; 60–70% of the member base has a stable attendee core they share; no-show rate is lower because sessions are less frequent and feel more consequential | Fast: 2–3 sessions per month with a consistent attendee core produces mutual familiarity within 45–60 days; members who have attended 4–6 sessions with the same peers have sufficient mutual knowledge to initiate between-session contact naturally | Moderate–high: members who have attended 4+ sessions with consistent peer overlap initiate between-session contact naturally — Slack DM, external collaboration, referral behavior; between-session contact rate rises sharply after the second month | Relationship: at renewal, members cite specific peers, not specific sessions or content topics; peer relationships are not available from content alternatives; the community becomes the container for peer relationships that exist nowhere else | Low (10–20%) for members who have attended at least 4 sessions with consistent peer overlap; moderate (25–35%) for members who have attended fewer than 3 sessions in their first 45 days — the at-risk group is identifiable and intervention is possible before the renewal decision |
| Weekly | Audience culture: members attend when the content is compelling, skip when it is not; the cadence is fast enough to sustain habit but the attendance concentration is too low to produce the peer familiarity that generates between-session contact | Variable by topic quality: the same 30–40% of members attend consistently; 60–70% attend opportunistically based on session topic relevance; a member who misses 2–3 consecutive weeks does not feel they have missed peer relationships — they have missed content | Slow despite high frequency: attendance concentration is too low — most members rarely attend the same session as the same peer twice across a 60-day window; high session count does not compensate for low per-member pair familiarity accumulation | Low: between-session contact requires a stronger peer relationship than audience culture produces; members who do not share a stable session attendance core have insufficient mutual knowledge to initiate contact between sessions | Content: members will cite “the sessions” when asked about value but will not cite specific peer relationships; content alternatives become competitive at renewal because the community’s retention moat is content quality, not peer-relationship exclusivity | High (35–55%) for members who do not attend consistently; moderate (15–25%) for consistent attendees who have content alternatives; the cadence prevents the community from developing the peer-relationship retention moat that makes renewal decisions non-comparative |
| Monthly or less | Event culture: each session is a standalone event; between-session familiarity does not accumulate because the gap is too long to maintain peer momentum; each session effectively re-introduces members to each other rather than advancing prior familiarity | Variable: members plan around sessions but the 30-day gap is long enough for members to drift; no stable peer attendance core forms because the interval between shared sessions is long enough to reset familiarity to near-zero | Very slow: members who see each other once per month accumulate 6 sessions of shared context per year — insufficient for peer relationship formation in most community types; 6 sessions of monthly contact produces acquaintance, not peer relationship | Very low: the 30-day gap produces relationship entropy — familiarity gained in one session decays before the next session; between-session contact is rare because there is insufficient mutual knowledge to make contact feel natural rather than forced | Events: members value the sessions as events, not as peer-relationship infrastructure; renewal decisions are driven by anticipated event quality in the next period; if the next period’s events look less compelling, there is no peer-relationship retention moat to offset the downgrade in content appeal | High (30–50%): in the first 90 days, members attend 3 sessions maximum at monthly cadence — insufficient for peer relationship formation; the renewal decision at day 90 is made on event quality alone; operators at monthly cadence are competing against alternative event subscriptions on content quality without a peer-relationship advantage |
Table 3 — Contribution structure checklist
Four session components that distinguish relationship-producing from content-producing sessions. The components are sequential dependencies: the structured contribution opening requires the pre-session preparation requirement to function; the peer-to-peer interaction format requires the structured contribution opening to provide content for member-to-member exchange; the specific commitment closing requires the peer-to-peer interaction format to have produced the peer familiarity that makes commitments feel binding. Removing any component reduces the effectiveness of the components that follow it.
Sequencing note: Operators who add only the commitment closing (Table 3, row 4) without the preparation requirement and contribution opening (rows 1–2) find that commitment completion rates remain below 40% because there is no peer-relationship accountability backing the commitment. The components compound — start from row 1 and add each in sequence.
| Session component | What it does | Failure version most operators actually build | The norm it establishes | Behavioral signal that it is working |
|---|---|---|---|---|
| Pre-session preparation requirement | Ensures every member arrives with a specific contribution — work sample, situation description, or prepared observation on another member’s submission — eliminating the cold-start problem where the first 10–15 minutes of a session are spent waiting for members to think of something to say or share | Open-ended “come with something to share” invitation without a defined format or submission deadline; result is that 20–30% of members arrive with something prepared and 70–80% arrive hoping the session structure will carry them; the contribution opening cannot function without preparation because there is nothing to make visible | Sessions are contribution events, not consumption events: members who do not prepare cannot participate in the contribution opening; the pre-session preparation requirement is the structural signal that changes member behavior from passive attendance to active contribution before they enter the session | Pre-session submission rate above 80% after two consecutive sessions; members who miss a submission deadline message the operator proactively before the session rather than silently not submitting; submitted contributions include specific situations or work samples rather than general topic suggestions |
| Structured contribution opening | Allocates the first 15–20 minutes of the session to making every member’s prepared contribution visible to the group before open discussion begins; prevents the first 3–5 members who speak from setting the agenda for the session while 60–70% of attendees remain passive observers | Starting with “who wants to go first?” or a round-robin that allows members to pass; result is that the contribution opening becomes a smaller version of the open-discussion phase, dominated by the same vocal minority who participate in any unstructured session; the 70% who would not volunteer are still not contributing | Every member contributes before anyone discusses: contribution is the entry condition for discussion, not something that some members do while others listen; this norm is established in the first two sessions and is extraordinarily difficult to dislodge afterward — the operator who runs sessions without a structured opening for the first eight sessions cannot add one in session nine without member resistance | All members contribute during the opening, including members who have not spoken in previous sessions; the quality of contributions increases across sessions as members learn what prepared contributions look like from peers; members who submit strong preparations begin receiving direct Slack messages from peers who observed their opening contribution |
| Peer-to-peer interaction format | Structures the open-discussion phase so that member-to-member interaction is the default rather than member-to-operator interaction; shifts the operator’s role from facilitator-expert who responds to each contribution to interaction-enabler who holds space for member exchanges and intervenes only when exchanges stall | Open discussion format where the operator responds to each member’s contribution before other members have spoken; result is a hub-and-spoke dynamic where every exchange runs through the operator rather than between members; members learn to direct contributions to the operator, not to each other; this is the single most common session design failure in paid communities | Members respond to each other’s contributions directly by name; the operator’s silence during a member-to-member exchange signals that peer interaction is the intended mode, not a deviation from it that the operator needs to redirect; the operator’s role is to ask questions that open member-to-member exchange when exchanges stall, not to supply the answer directly | Members direct responses to each other by name without the operator prompting them to do so; member-to-member exchanges run for 3+ minutes without operator intervention; members who knew each other before the session develop identifiably deeper exchange with members they met through the structured opening |
| Specific commitment closing | Allocates the last 5 minutes of the session to each member stating one specific, verifiable commitment for the period before the next session — the mechanism that converts session familiarity into between-session peer accountability and creates an organic reason for members to contact each other outside the session | Ending with “great session everyone” or a vague “keep working on what we discussed”; result is that sessions feel productive but produce no between-session contact and no accountability anchor for the next session; the session is a complete unit that leaves no open loop requiring follow-up | The session is not complete until each member has committed to a specific action; the commitment is public, which makes it binding to the degree that peer relationships have formed; at the next session’s opening, commitments from the prior session are reviewed before any new contribution opening begins — the review is what makes the commitment norm durable across sessions | Members state specific, measurable commitments (not “I’ll keep working on the project” but “I’ll have the first section drafted by Thursday and post it in #working-drafts before the next session”); commitment completion rate at the next session’s opening check-in exceeds 65% after 4–6 sessions; members message each other between sessions referencing their commitments |
Table 4 — First-30-day programming arc
Three programming components for new-member integration across the first 30 days. The arc addresses the new-member’s primary problem in the first month: they have not yet developed the peer relationships that make the contribution structure feel natural rather than performative. The three components build peer relationships intentionally rather than waiting for organic formation, which is too slow to prevent early churn in the days 30–60 window when most paid community cancellations happen.
Timing dependency: The pairing component (row 2) should overlap with the structured introduction session (row 1) so that the new member’s established-member pair is present when the new member makes their community introduction. This gives the pairing relationship a specific shared reference point from day one: the pair has observed the new member’s professional situation in the same session context, which makes the between-session contact task in row 2 natural rather than cold.
| Programming component | What to do | When in the 30 days | What it produces | Failure version | Success metric |
|---|---|---|---|---|---|
| Structured introduction session | A session within the first two weeks where new members present their professional situation in a defined format (current work, named challenge, one specific outcome they want from the community) to a group that includes established members; established members respond with specific connection offers referencing the new member’s stated situation — not generic welcomes, but specific offers (“your challenge on X sounds like what I worked through with Y — I can send you the framework I used”) | Within the first two weeks; not the very first session the new member attends, since they have not yet understood enough about the community’s contribution norms to frame their introduction in terms the community finds useful; the second or third session they attend is the right timing | New member’s first peer relationships in the community are with established members who have responded specifically to their stated situation; the introduction session creates a named-peer connection before the new member has attended enough sessions to form peer relationships organically through repeated co-presence | General welcome in #introductions channel (no format, no established-member response obligation, no session); or a group welcome call where 15+ new members introduce themselves with no established-member participation; neither produces named peer connections because neither includes a mechanism for an established member to respond specifically to the new member’s situation | Each new member can name at least one established member who responded to their specific situation within 48 hours of the introduction session; the established member’s response references something specific from the new member’s introduction (not a generic welcome) |
| New-member pairing with established member | Pair each new member with an established member (60+ days tenure, consistent session attendance, has contributed at least once to a peer’s specific situation) for at least two sessions in the new member’s first 30 days; the pair should have a between-session contact task — not generic “check in with your buddy” but “review each other’s pre-session submissions before the next session and send one specific observation by [date]” — creating a reason for contact outside the session | First pairing within the first week; second pairing contact task within 48 hours of the introduction session so that the established member partner is activated immediately after the new member’s introduction; the pairing should span at least two sessions within the 30-day window to produce more than a single shared-context reference point | New member has at least one established-member peer who knows their professional situation in detail; the between-session contact task converts passive pairing into actual contact, which is the foundation of peer relationship; a pair that has made one specific task-driven contact is categorically different from a pair that has been introduced and left to self-organize | Assigning a “buddy” with no defined contact task and no session overlap; result is that the buddy and new member are nominally connected but rarely speak because there is no mechanism that creates a specific reason for contact; by day 14, the pairing has produced zero between-session contact and neither member is aware that the relationship was supposed to produce anything | New member and established-member pair have had at least one direct exchange outside the session by day 30; the exchange references the between-session contact task (verifiable from Slack DM thread or contribution-thread reply data); the established member attends at least one of the two sessions where the new member is using the contribution structure for the first time |
| First-30-day contribution commitment | During the new member’s first session or immediately after, ask them to make a specific contribution commitment for their first 30 days — not “participate in sessions” but “prepare a pre-session submission for each of the three sessions in my first month and post it in #pre-session by the deadline”; frame it as the community’s expectation for new members rather than a personal goal, so the commitment has a social dimension from the start | Day 0–7: the commitment should be made before the member has had time to settle into a passive consumption pattern; a member who attends their first three sessions without a contribution commitment is unlikely to adopt the contribution structure voluntarily in session four | The new member’s first 30 days are defined by contribution behavior rather than attendance behavior; members who make and keep a specific contribution commitment in their first 30 days have 2.5–3× higher renewal rates than members who attend the same number of sessions without a contribution commitment, because contribution behavior produces the peer relationships that drive renewal | Asking new members to “join us for sessions” or “explore the community at your own pace” without a specific contribution commitment; result is that new members self-select their engagement level, and members who default to passive attendance have no mechanism converting them to contributors before the day-30–60 churn window arrives | First-30-day contribution commitment completion rate above 70%; members who complete the commitment make a second contribution in days 31–60 at 3× the rate of members who did not make a commitment; by day 30, committed members can name at least two peers whose work they understand — the clearest behavioral indicator that peer relationships have formed |
Table 5 — Event measurement metrics
Three behavioral metrics for measuring whether events are producing peer relationships rather than just attendance. All three metrics measure member behavior outside the session or after it, not behavior during the session. The distinction is important: session attendance and in-session participation are the most accessible metrics but the least informative about whether the session is producing the peer relationships that drive retention. The three metrics below are harder to collect but are the actual leading indicators of renewal behavior.
Measurement priority: Run the metrics in order. If the 48h post-session contact rate (row 1) is below threshold, address it before measuring the named-peer rate (row 2) or commitment completion rate (row 3), because low post-session contact is the upstream cause of the low named-peer and low commitment-completion rates that follow.
| Metric | Measurement method | Healthy benchmark | At-risk threshold | What below-threshold indicates (which session component is failing) | Highest-leverage intervention |
|---|---|---|---|---|---|
| Peer-to-peer interaction rate in 48h post-session | Count member-to-member messages (DM threads, contribution-channel replies where both initiator and responder attended the session) in the 48 hours immediately after each session; divide by the number of unique member pairs who attended the session; record as a percentage of attendee pairs that exchanged at least one message in the window | 25–40% of attendee pairs exchange at least one message or reply in the 48h post-session window; for communities with a structured commitment closing, the benchmark is higher (35–50%) because commitments create a specific reason for post-session contact that members can act on immediately | Below 15% of attendee pairs; or a declining trend of more than 5 percentage points across three consecutive sessions even if still above 15%; declining trend on a metric that should be stable or rising indicates a structural problem, not a bad-session anomaly | Missing commitment closing (Table 3, row 4) — the 48h post-session window is when commitment-based contact occurs; if there is no commitment structure, there is no organic reason for contact immediately after a session ends; secondary: missing peer-to-peer interaction format (Table 3, row 3) — hub-and-spoke dynamic means members developed no member-to-member exchange to continue after the session | Add the commitment closing to the next session (5 minutes at end; each member states one specific action for before the next session; the operator reviews commitments at the opening of the following session); if this does not move the metric within 2 sessions, audit the peer-to-peer interaction format in the open discussion phase — record and review whether exchanges are running through the operator or between members |
| Member-named-peer rate at 30 and 60 days | At the 30-day and 60-day marks after join, ask each member individually (operator Day 30 and Day 60 check-in message) to name two specific peers whose work they understand and who understand theirs; record the proportion who can name two peers at each mark — this is the named-peer rate; do not prompt with names; the member must produce the names without a list to choose from | 60-day named-peer rate of 60–75% (at least 6 in 10 members can name two peers who know their professional situation by day 60); 30-day named-peer rate of 30–45% (lower because peer relationship formation requires multiple sessions; the 30-day rate is useful as a leading indicator of the 60-day rate rather than as an absolute benchmark) | 60-day named-peer rate below 40%; or no improvement from the 30-day rate (indicating that the second month of membership is not producing new peer relationships for the member, which means the contribution structure is not functioning as a peer-formation mechanism) | Missing new-member pairing (Table 4, row 2) — members who reach 60 days without a named-peer connection have not had a structured mechanism to develop a specific peer relationship; secondary: missing structured introduction session (Table 4, row 1) — members who were never exposed to a formatted peer-introduction process lack the specific established-member responses that create named connections in the first two weeks | Run the structured introduction session (Table 4, row 1) for members currently at 30–60 days who cannot name two peers; pair those members with an established member (Table 4, row 2) with a specific between-session contact task (not a generic buddy assignment); if the 60-day rate does not improve within one cohort cycle, audit the contribution opening format — named-peer rate below 40% at 60 days usually indicates the sessions are running without the structured contribution opening that makes members’ situations visible to each other |
| Commitment completion rate at subsequent session opening check-in | At the opening of each session, before any new contributions are shared, the operator reads the commitment each member made at the close of the previous session and asks for a one-sentence update; record the proportion of commitments completed as stated — not partially completed or completed late — this is the commitment completion rate; partial completion and late completion are tracked separately as secondary signals | Above 65–70% for sessions where peer relationships have formed sufficiently that commitments feel socially binding; 40–55% in the first 4–6 sessions as the commitment norm is establishing; below 40% after session 6 indicates the accountability norm has not formed and commitments are being made as a session-closing social performance rather than as genuine behavioral commitments | Below 40% after session 4; or a declining trend across three consecutive sessions even if above 40%; declining rate after session 4 indicates that the commitment norm is eroding rather than establishing, which is a leading indicator of declining peer relationships across the member base | Missing pre-session preparation requirement (Table 3, row 1) — if the preparation requirement norm is absent, commitment completion has no peer-accountability backing; commitments feel like private goals rather than contributions the community is watching for; secondary: insufficient peer-to-peer interaction in session (Table 3, rows 2–3) — members who have not formed peer relationships do not feel the social cost of a missed commitment that peer-relationship members feel | Move the commitment completion check to the very first agenda item of each session (before the contribution opening, not after); this signals to the group that prior commitments matter before any new session content begins; if completion rate does not improve within 3 sessions, reduce commitment scope (ask for smaller, more achievable commitments until the norm establishes, then increase scope across 4–6 sessions); do not skip the check even when completion rates are low — skipping the check teaches members that commitments have no consequence |
Frequently asked questions
What events work best for paid communities?
The events that work best for paid communities are those that produce peer relationships between members, not events that primarily deliver content from operator to member. The three formats that consistently produce peer relationships are structured peer review (each member prepares a specific work sample in advance and receives observations from specific peers, creating mutual intellectual investment before the session begins), co-working sessions (members arrive with specific work in progress and share structured check-ins at open and close, accumulating familiarity with each other’s professional situations across multiple sessions), and themed expert-member exchanges (members submit specific situations rather than general questions, and the expert responds to submitted situations rather than delivering a prepared presentation, giving members shared reference points for peer discussion). The formats that do not produce peer relationships — webinar-style presentations, operator Q&A sessions, and social events without contribution structure — are appropriate as supplements but should not be the primary recurring format when peer relationships are the primary retention driver. The single design decision that distinguishes relationship-producing from content-producing sessions is the contribution structure: a preparation requirement, a structured contribution opening that makes every member’s preparation visible before open discussion, a peer-to-peer interaction format in open discussion, and a specific commitment closing. Sessions without a contribution structure produce pleasant experiences; sessions with one produce the peer accountability that drives between-session contact and renewal.
How often should a paid community run events?
Two to three events per month is the cadence that consistently produces relationship culture in paid communities — peer familiarity accumulates fast enough to produce between-session contact without the attendance-dilution effect of weekly cadence. Weekly events produce audience culture: attendance varies by topic quality, the same 30–40% of members attend consistently while 60–70% attend opportunistically, and members develop content loyalty rather than peer relationships. At weekly cadence, a member who misses two or three consecutive weeks does not feel they have missed peer relationships; they have missed content, which can be replaced by a recording or an alternative source. Monthly events produce event culture: each session is standalone with no peer-familiarity accumulation between sessions, and renewal decisions are driven by anticipated event quality rather than current peer relationships. Two to three events per month at a consistent cadence builds the attendee core that makes peer familiarity accumulate: members who attend both sessions in a given month see the same peers twice in 30 days, producing cross-session familiarity that generates between-session contact by the second month. At a two-per-month cadence, a consistently attending member has seen the same core peer group four times in 60 days — enough for peer relationships to form for the 60–70% of the member base who attend consistently. That peer-relationship core is what makes renewal decisions resistant to content alternatives.
How do you get members to participate actively in community events?
Active participation in community events is determined by session design before the session begins, not by facilitation techniques during it. The four structural decisions that produce active participation are: (1) a pre-session preparation requirement — a defined format for what each member should bring and a submission deadline 48–72 hours in advance, so members arrive with a specific contribution rather than hoping the session structure will draw something out of them; (2) a structured contribution opening — the first 15–20 minutes are allocated to making every member’s prepared contribution visible to the group, so contribution is the entry condition for discussion; (3) a peer-to-peer interaction format in open discussion — the operator’s role shifts to enabling member-to-member exchange rather than responding to each contribution before other members speak; if the operator responds to each member first, the session develops a hub-and-spoke dynamic where every exchange runs through the operator rather than between members; and (4) a specific commitment closing — the last five minutes are allocated to each member stating one specific, verifiable commitment for before the next session, creating a reason for between-session contact and a public accountability anchor at the next session’s opening. The most common error is trying to increase participation through enthusiasm or open-ended prompts during the session rather than through structural changes made before it begins. No facilitation technique reliably converts a passive-format session into an active one; structural changes to the pre-session preparation requirement and the contribution opening are the only interventions with consistent evidence for increasing participation rates.
What is the ideal paid community event structure?
The ideal paid community event structure has four phases: (1) pre-session preparation requirement (48–72 hours before the session, each member submits a specific contribution — work sample, situation description, or prepared observation on another member’s submission); (2) structured contribution opening (the first 15–20 minutes of the session, where every member’s prepared contribution is made visible to the group in a defined format before open discussion begins); (3) peer-to-peer interaction phase (30–45 minutes where the operator enables rather than leads member-to-member exchange; the operator’s silence during member exchanges signals that peer interaction is the intended mode); and (4) specific commitment closing (the last 5 minutes, where each member states one specific, verifiable commitment for before the next session, and the operator states explicitly that commitments will be reviewed at the next session’s opening). Session length: 60 minutes for groups of 6–10 members; 75–90 minutes for 10–16 members; beyond 16, split into parallel sessions rather than extending time, since the contribution opening cannot be completed in reasonable time at that scale. The most common structural error is running the session in reverse: starting with open discussion (where vocal members set the agenda while others listen) and ending with optional sharing. The contribution opening must precede discussion because it is what makes discussion peer-to-peer rather than operator-led — members respond to each other’s contributions rather than volunteering topics into a void.