Member Spotlight Reference Card
Paid community member spotlight — two spotlight formats, 5-question set, wrong patterns, 3-DM outreach sequence, and three measurement metrics
This page is a structured reference card for paid Slack community operators who want the spotlight format specs, question set, wrong patterns, outreach sequence, and measurement benchmarks in scannable table form. It covers: a two spotlight formats comparison table (contribution spotlight vs. journey spotlight) with when-to-use, member tenure, anchor, what it produces, and primary risk for each; a five-question set reference table with what each question does mechanically, which format it applies to, and the failure mode if it is skipped; a wrong spotlight patterns table with four patterns, what each looks like, why it underperforms, the failure signal to watch for, and the fix; a three-DM outreach sequence table with timing, what each DM says, its key element, and expected conversion; and a three measurement metrics table (14-day re-contribution rate, peer-nomination rate, and thread depth) with definitions, healthy benchmarks, at-risk thresholds, interventions, and measurement methods. For the strategic reasoning behind the member spotlight framework — including why most operators run spotlights as a marketing format and why the contribution-catalysis framing produces higher re-contribution rates, how the identity-continuation effect works, and why Question 5 is the most important of the five — see the companion post: Paid community member spotlight: the format that drives contribution. This card is for the operator who understands the reasoning and needs the format specs, question set, and measurement benchmarks in quick-reference form.
TL;DR
Use contribution spotlight (2–6 month members, anchored to a specific community act) or journey spotlight (6+ months, before/after arc). Run the five-question set with Question 5 (“what are you working on that you might bring next?”) as the re-contribution trigger. Reach out with a 3-DM sequence: specific framing, explicit process description, easy opt-out — expect 65–75% acceptance rate. Avoid achievements-only spotlights, selecting non-contributors, monthly cadence, and spotlights with no community-topic link. Measure 14-day re-contribution rate (healthy ≥60%), peer-nomination rate (healthy >30%), and thread depth (healthy 5–12 replies). Post every 1–2 weeks on Tuesday or Wednesday morning with a personal operator note.
Two spotlight formats comparison
Member spotlights in paid communities take two forms, which differ in the anchor, target tenure, what they produce, and their primary failure risk. Operators who run only one format regardless of member tenure are either spotlighting recent members with a format designed for long-tenured members (journey spotlight applied to 3-month members, who have no before/after arc to draw on) or spotlighting long-tenured members with a format that undersells their arc (contribution spotlight applied to 18-month members, where a specific recent post is too narrow an anchor for the depth of experience the member has accumulated). Matching format to tenure produces both higher re-contribution rates (because the question set fits the member’s current relationship with the community) and higher peer-recognition value (because the story is legible and credible to the members who read it).
| Format | When to use | Member tenure | Anchor | What it produces | Primary risk |
|---|---|---|---|---|---|
| Contribution spotlight | When the member has made a specific recent community contribution — a post, a resource shared, a question that generated significant discussion — that is worth examining publicly. Use when the goal is to surface the motivation behind a specific act of contribution and create a forward commitment for the next one. This is the default format for 2–6 month members because the specific-act anchor is concrete enough to build a focused 400–600 word story around without requiring the member to have a long-arc narrative to draw on. | 2–6 months. Members in this tenure band have made contributions but have not yet accumulated the before/after arc that makes the journey format credible. Below 2 months, the member may not yet have a specific community act notable enough to anchor the spotlight without the operator inventing the anchor, which produces a generic introduction post rather than a spotlight. | A specific, named, recent community act: a post the member made, a resource they shared, a question they asked that generated 5+ replies, a connection they facilitated between two other members. The anchor must be specific enough that the member recognises it immediately and that other community members remember or can look up the original act. A vague anchor (“your consistent contributions” or “your expertise in X”) produces a vague story that fails to demonstrate the contribution-catalysis mechanism. | A concrete example of the kind of contribution the community wants more of, embedded in a public story about why the member decided to share rather than keep it to themselves, and a forward commitment (Question 5) about what the member will bring next. Readers encounter three things simultaneously: a model of the contribution threshold (“this is the kind of thing that belongs here”), a demonstration of why sharing is worth it for the contributor, and a named next contribution they can follow up on. | Spotlight-as-achievement-summary: the operator selects the anchor based on the member’s professional accomplishments (job title, employer, external recognition) rather than their community act. An achievements-only spotlight describes who the member is outside the community, not what they did inside it, and fails to demonstrate the contribution-catalysis mechanism. The 5-question set corrects this if followed; the risk is highest when the operator writes the spotlight themselves without using the question set, substituting their own narrative for the member’s words. |
| Journey spotlight | When the member has accumulated enough community tenure and documented change in their domain to support a before/after arc that is specific, credible, and attributable to their participation in the community. Use when the goal is to demonstrate long-term value of community membership to members approaching a renewal decision (month 6 or month 12) who are evaluating whether the investment has been worth it. The journey format is the most effective retention signal for the cohort approaching renewal — it provides a concrete narrative from a peer who has already made the same cost-benefit decision and arrived at a specific, describable outcome. | 6+ months. The before/after arc requires enough elapsed time for the change to be genuine and specific rather than projected or aspirational. A 6-month member can describe a specific shift in one domain relevant to the community’s focus topic; an 18-month member can describe a multi-phase arc with specific milestones. Do not run a journey spotlight for members with fewer than 6 months of tenure unless they joined at a dramatically different baseline (e.g., a complete career-changer whose before state is definitionally different from their current state). | The transition moment or event that marks the shift between the member’s before-state and after-state in the community’s domain. The anchor is a specific community interaction that caused or accelerated the shift: a post they read that changed how they thought about something, a conversation with another member, a resource they applied, a question they asked that gave them a framework they have used since. Vague anchors (“being part of this community” or “the general support I felt”) fail to attribute the change to the community specifically and read as testimonials rather than stories. | A social-proof narrative that demonstrates concrete, domain-specific transformation attributable to community participation. The primary audience for this outcome is members approaching month-6 or month-12 renewal who are weighing whether to continue. A journey spotlight that answers “what specifically changed and what in the community caused it?” is more persuasive for this audience than any operator-written case study, because the peer credibility of the narrator is higher than the operator’s credibility as a self-describing product. Secondary outcome: a re-contribution commitment (Question 5 applies here too), which is lower-rate than in contribution spotlights (journey members have longer contribution cycles) but still important to include. | Vague before/after arc: the spotlight describes the member’s general sense of growth or belonging rather than a specific, measurable change in their work or domain knowledge. This failure mode is most common when the member is asked to describe their journey without a structured question set and defaults to positive-sentiment language (“I’ve learned so much”, “the community has been incredibly valuable”) that lacks the specificity to function as social proof for prospective renewers. The question set (particularly Question 1, adapted to “what was the specific moment or thing in this community that marked the shift?”) corrects this by forcing the narrative to an anchor before the member can generalise. |
Shared format specs for both types. Length: 400–600 words (not shorter — below 400 words the story lacks specificity; not longer — above 600 words the format shifts from a spotlight to a case study, which has lower community engagement). Publication day: Tuesday or Wednesday morning in the operator’s primary community time zone (highest async engagement day for business-focused paid communities). Personal operator note: 2–3 sentences from the operator explaining why this specific member was selected now, written in first person, separate from the spotlight text itself. The operator note is what transforms the spotlight from a community content piece into a recognition act from the operator to the member.
Five-question set reference
The five questions below are the core interview structure for both spotlight formats. Each question does a specific job mechanically in producing the contribution-catalysis outcome. The questions must be asked in order and in full — skipping or combining questions produces a story that covers some of the mechanism (contribution threshold modelling, identity-continuation effect, forward commitment) but not all of it. Question 5 is the most commonly skipped and the most important to include: it is the re-contribution trigger that produces the 14-day re-contribution rate difference between contribution-catalysis spotlights and achievement-summary spotlights. For contribution spotlights, Question 1 anchors to a specific community act. For journey spotlights, Question 1 is adapted: “What was the specific moment or thing in this community that marked the shift from where you were when you joined to where you are now in [domain]?”
| Question | What it does | Which format | Failure mode if skipped |
|---|---|---|---|
| Q1: “What did you share [specific post or contribution], and what made you decide to post it here rather than keep it to yourself?” | Anchors the spotlight to a specific community act and surfaces the member’s explicit motivation for contributing. When the member articulates why they decided to share rather than keep it to themselves, they produce a public account of the contribution threshold for this community — a data point that every reader can use to calibrate whether their own draft idea or question belongs here. The more specific the anchor, the more legible the threshold signal is to readers in a similar position. | Contribution spotlight (primary). Journey spotlight uses a variant: “What was the specific moment or thing in this community that marked the shift from [state A] to [state B]?” Both versions force the narrative to a specific anchor before the member can generalise into vague positive sentiment. | Without Q1, the spotlight opens with general context (“I joined this community 4 months ago and have found it really valuable”) rather than a specific act. The general opener signals to readers that the spotlight is a testimonial, not a story, and reduces engagement because there is no specific anchor for readers who are in a similar situation to recognise themselves in the narrative. Thread depth drops by an average of 3–5 replies when spotlights open without a specific anchor. |
| Q2: “What prompted you to post that particular insight at that particular moment? Was there something in the community that made you decide it was the right time?” | Connects the contribution to the community context that produced it. When a member describes a specific community event, conversation, or recurring format that prompted them to share, they attribute the contribution to the community rather than to their own internal motivation. This attribution mechanism is what makes the spotlight function as community advertising rather than member advertising: the story demonstrates that the community creates the conditions for posting, not just that this member happens to be a generous contributor. | Both formats. In journey spotlights, this question is applied to the transition moment identified in Q1: “What was happening in the community at the time of that moment — what created the conditions for it?” | Without Q2, the spotlight implies that contribution is purely a function of the member’s individual generosity or expertise. Members who do not see themselves as unusually generous or expert interpret this as evidence that the community is not for people at their level, rather than as evidence that the community creates contribution moments for members at any level. Q2 is what makes the spotlight function as an invitation rather than an example. |
| Q3: “What surprised you most about the response you got? Did anything shift in how you think about sharing in communities like this one?” | Creates an explicit social-proof signal about the value of posting and surfaces the identity effect of being responded to. When a member describes being surprised by the quality or specificity of the peer response they received, they are providing evidence for two things simultaneously: that posting in this community produces a return (unexpected positive response), and that receiving that response changed something in how they see themselves in relation to the community. The identity-continuation effect — the mechanism by which a member who has been publicly recognised is more likely to contribute again — is most legible in Q3 answers. | Both formats. In journey spotlights, Q3 is applied to the transition moment: “What shifted in how you saw yourself in this domain after that moment?” | Without Q3, the spotlight lacks a peer-response narrative. Readers who are considering posting but are uncertain whether the community will respond to their specific topic or level of expertise have no evidence from Q3 to reduce their uncertainty. The social-proof function of the spotlight depends on Q3: Q1 demonstrates what was shared, Q2 demonstrates why, and Q3 demonstrates what happened as a result. A spotlight that ends at Q2 answers “what” and “why” but not “what happened,” which is the question that most prospective first-posters are asking. |
| Q4: “What would you say to a member who is sitting on something similar right now — a question or insight they’re not sure is worth sharing?” | Creates a direct peer-to-peer invitation to the 40–60% of members who are currently in the ‘sitting on something’ state — they have an idea, question, or resource they have not yet shared because they are uncertain whether it meets the community’s implicit standard. The Q4 answer functions as a permission structure from a peer: when a credible, tenured member says directly that the uncertainty most non-posters feel is normal and that sharing is worth it, it reduces the social cost of a first or infrequent post in a way that no operator-written invitation can match, because the credibility of the source is peer-level rather than operator-level. | Both formats, unchanged. The permission structure works identically regardless of the spotlight anchor type. | Without Q4, the spotlight is addressed to the member being spotlighted rather than to the members reading it. Q1–Q3 tell the spotlighted member’s story; Q4 is the explicit pivot to the reader. Spotlights that do not include Q4 generate lower thread depths (fewer replies from readers who see themselves in the ‘sitting on something’ state) and lower 14-day first-post rates from non-posting members who read the spotlight. The thread depth difference between spotlights with and without Q4 is typically 2–4 replies. |
| Q5: “What are you working on right now that you might bring to the community next?” | The re-contribution trigger. A member who articulates a specific next contribution in a public spotlight has made a social commitment to the community they were not prompted to make by any prior community interaction. The identity-continuation effect is strongest when the commitment is specific (“I’m working on a pricing framework and will share it once I’ve tested it”) rather than vague (“I hope to contribute more”). Specific commitments produce 14-day re-contribution rates of 60–80%; vague commitments produce rates in the 30–45% range, comparable to non-spotlighted members. The operator’s job after the spotlight publishes: check back with the member at day 10–14, reference Question 5, and ask how the thing they mentioned is going. | Both formats. The forward-commitment mechanism works regardless of tenure band or spotlight anchor type. In journey spotlights, the Q5 answer tends to be more strategic (“I’m going to start a monthly goal thread for members in [goal track]”) than in contribution spotlights (“I’m working on a post about X and will share it next week”), which means the 14-day re-contribution rate target should be calibrated by tenure: 60%+ for contribution spotlights, 45%+ for journey spotlights. | Without Q5, the spotlight ends on Q4 (the peer-to-peer invitation to other members) and the spotlighted member has no public commitment to make a next contribution. The 14-day re-contribution rate for spotlights that end at Q4 is 20–35% — comparable to non-spotlighted tenured members. This is the single largest performance gap between contribution-catalysis spotlights and achievement-summary spotlights: the latter typically end at Q3 or Q4, and their re-contribution rates reflect the absence of Q5. |
Question sequence is not optional. The five questions are structured in dependency order: Q1 provides the specific anchor that Q2 contextualises; Q2 produces the community-attribution narrative that Q3 validates with a peer-response signal; Q3 surfaces the identity shift that Q4 uses to address other members in the same position; Q4 creates the permission structure that makes Q5’s forward commitment feel like a natural next step rather than a promotional ask. Asking the questions out of order, or asking them all at once rather than in sequence, disrupts the dependency chain and produces answers that do not build on each other.
Wrong spotlight patterns — failure modes and fixes
The four patterns below are commonly implemented by operators who run member spotlights and consistently produce lower re-contribution rates, lower thread depths, and lower peer-nomination rates than the two-format, five-question model. Each pattern looks reasonable in planning (it seems to add visibility, community pride, or cadence efficiency) and underperforms in execution because it prioritises the operator’s goals (social proof, acquisition) over the contribution-catalysis purpose that makes spotlights compound over time.
| Pattern | What it looks like | Why it underperforms | Failure signal | Fix |
|---|---|---|---|---|
| Achievements-only spotlight | The spotlight describes the member’s professional background, employer, career milestones, or external recognition (press mentions, awards, speaking engagements) with little or no reference to what the member has done inside the community. The operator writes the spotlight themselves (or assembles it from the member’s LinkedIn profile) rather than conducting the five-question interview. The resulting post reads as an introduction to an impressive person rather than a story about community contribution. | An achievements-only spotlight signals to readers that the community selects members for spotlights based on external status, not internal contribution. This creates two negative effects: members who do not have impressive external credentials conclude that spotlights are not for people at their level, reducing the peer-nomination and self-nomination potential; and the spotlighted member receives no Q5 forward-commitment prompt, producing 14-day re-contribution rates of 20–30% rather than the 60%+ produced by contribution-catalysis spotlights. The spotlight functions as a vanity piece rather than a community engine. | Thread depth below 4 replies despite the spotlighted member having high external status. 14-day re-contribution rate below 35% for spotlighted members. Peer nominations referencing the member’s external achievements (“you should spotlight Sarah because she’s a VP at [company]”) rather than their community contributions (“you should spotlight Sarah because of her post on pricing last month”). | Replace operator-written profiles with the five-question interview format. If the operator has already written achievement-only spotlights, add a single closing question retroactively: “One thing we forgot to ask: what are you working on that you might bring to the community next?” and post the answer as a follow-up comment. This retroactive Q5 produces a small but measurable lift in 14-day re-contribution rate even for achievement-focused spotlights. Going forward, require that any spotlight candidate answer all five questions before the spotlight is drafted. |
| Non-contributor selection | The operator selects spotlight subjects based on tenure, payment tier, or social desirability (members who are active in DMs but rarely post publicly, or members whose external reputation would generate social-proof value) rather than based on public community contributions. The selected member may be a strong community participant in private but has no public contribution that the spotlight can anchor to. The spotlight describes the member’s relationship with the community in vague terms (“always supportive”, “brings great energy to calls”) rather than specific acts. | A non-contributor spotlight cannot anchor to a specific community act, which makes it impossible to run the five-question set in contribution-spotlight mode. Without an anchor, Q1 has no referent, Q2 cannot connect the contribution to community context, and Q3 cannot surface the peer-response signal. The interview becomes a vague positive account of membership satisfaction. Additionally, non-contributor spotlights model private participation rather than public contribution — the opposite signal of what the spotlight is designed to create. | Five-question interview answers that are vague across all five questions despite a long interview. Thread depth below 3 replies. Peer-nomination rate remaining below 15% even after the peer-nomination system is running (because peers are not nominating public contributors — they are nominating members they personally know and like). 14-day re-contribution rate below 25% because the spotlighted member had no public contribution to continue from. | Require that every spotlight candidate have at least one specific, named, public community contribution (a post, a shared resource, a question with 3+ replies) that was made within the 60 days before the spotlight is proposed. If the operator wants to spotlight a member who participates primarily in DMs or calls, wait until that member makes a public contribution first — or explicitly ask them to make one as a prerequisite for the spotlight. “I’d love to do a spotlight on you. Would you be willing to share [thing you mentioned in our call] in the main channel first? That gives me a specific contribution to anchor the spotlight to.” This DM both creates the anchor and increases the likelihood that the spotlight will produce a genuine Q5 commitment. |
| Monthly cadence | The operator runs one member spotlight per month, on a fixed date (e.g., the first Tuesday of the month). The spotlight is treated as a monthly newsletter feature rather than an ongoing community rhythm. There are typically 30–31 days between spotlights, during which no new spotlight-driven contribution catalysis occurs. | Monthly cadence is too slow to produce a compounding effect. A single spotlight per month means each member has a maximum of 12 chances per year to be spotlighted (more realistically, 5–7 chances if the operator rotates through the full membership). Members who made contributions in month 2 will not be spotlighted until month 3 at the earliest, by which time the contribution is no longer recent enough to anchor a high-specificity Q1 answer. The 14-day window for the Q5 re-contribution follow-up closes before the next spotlight creates momentum in the community. Monthly cadence produces spotlight as event rather than spotlight as rhythm. | Community members expressing surprise at who was spotlighted (“I didn’t know they posted that”) because the contribution is too old. Thread depth below 4 replies despite solid contributions (the post is too old for readers to remember the original context). 14-day re-contribution rate normal for spotlighted members but no compounding community-wide contribution rate lift (because spotlights are too infrequent to create a contribution-catalysis pattern that non-spotlighted members observe and internalise). | Move to bi-weekly cadence (one spotlight every 1–2 weeks). At bi-weekly cadence, each spotlight’s contribution anchor is recent enough for community members to remember the original post, Q3 answers about peer response are fresh and specific, and the community develops the expectation that spotlights are a regular rhythm rather than a special event. If bi-weekly feels like too much content production for the operator, use the five-question interview format to reduce production time (the interview is 20–30 minutes; the write-up from the answers is 30–45 minutes) rather than reducing cadence below bi-weekly. |
| No community-topic link | The spotlight describes the member’s contribution and re-contribution commitment (Q5) but does not connect either to the community’s specific focus topic or ongoing discussions. Q5 answers like “I’m working on some things and will share them when they’re ready” are left as-is rather than edited to reference the community’s active channels, current discussions, or recurring formats where the next contribution could land. Readers cannot connect the Q5 commitment to a specific place in the community where they could expect to see it. | Without a community-topic link, the Q5 forward commitment is too abstract to create anticipation or follow-up engagement. Readers who encounter “I’ll share more soon” have no specific post, thread, or channel to watch for the next contribution. The 14-day follow-up DM (“How is that thing you mentioned going?”) also loses specificity without a community-topic anchor: the operator has to reconstruct the context from memory rather than referencing a specific Q5 answer. The compounding effect of spotlight programmes depends on readers developing the expectation that Q5 commitments will appear in specific community spaces — without the community-topic link, this expectation cannot form. | Q5 answers that are vague even from well-prepared members (“I’ll definitely share more” rather than “I’m working on a pricing model for the cohort-based tier and will share a draft in #business-model next month”). Thread depth normal but zero follow-up comments on the thread in the 7–14 days after posting (community members have no specific thing to watch for). 14-day operator follow-up DMs producing low recall (“Oh yes, I said I would share something — I’ll get to it”) because neither the operator nor the member has a specific commitment to reference. | Add one editing step to the spotlight draft: after completing the five-question interview, rewrite the Q5 answer with the member to make it channel-specific and timeline-specific. The edited Q5 target: “[Member] is working on [specific thing] and plans to share [specific output] in [specific channel or format] by [approximate date].” This requires a brief back-and-forth with the member after the interview (“For Q5, could we make this more specific? Would you be comfortable naming the channel where you’d share it?”) but produces a Q5 answer that functions as a public contract rather than a vague intention. |
The common root across all four wrong patterns: each one treats the spotlight as a content piece (something to produce and publish) rather than as a contribution mechanism (something designed to change the behaviour of both the spotlighted member and the members who read it). Content-piece spotlights optimise for the spotlight itself; contribution-mechanism spotlights optimise for what happens in the 14 days after the spotlight goes live.
Three-DM outreach sequence
The three-DM outreach sequence below produces 65–75% spotlight acceptance rates from members who have made a recent public contribution. The most common alternative — a single DM asking “can I feature you in a community spotlight?” — produces 30–40% acceptance rates, because the question frames the spotlight as something being done to the member for the community’s benefit rather than as a conversation about the member’s experience. The three-DM approach separates the request (DM 1), the process description (DM 2), and the easy-exit option (DM 3) across three distinct contacts, which reduces the cognitive load of any single DM and gives the member three opportunities to engage at their preferred level of commitment. The sequence is for direct operator outreach; peer-nomination system contacts use a different (single-question) DM format described in the FAQ below.
| DM | Timing | What it says | Key element | Expected conversion |
|---|---|---|---|---|
| First DM — specific framing | Within 3–5 days of the contribution that will anchor the spotlight. The anchor must still be recent enough that both the operator and the member remember it specifically. Sending the first DM more than 7 days after the anchor contribution reduces response rates because the member can no longer clearly recall the specific act the operator is referencing, and the operator’s reference to it feels vague or distant. | Two sentences only. Sentence 1: name the specific anchor contribution. “Your post on [specific topic] in [channel] on [day] was one of the most useful things shared in the community this month.” Sentence 2: the specific reason for the DM. “I’d love to do a short spotlight on you and that post — would you be up for a 20-minute conversation?” Do not include: an explanation of what a spotlight is, a list of what the conversation will cover, a reassurance that it won’t take long, or any other qualifying language. Two sentences. The specificity of Sentence 1 is what converts this DM from a generic outreach into a recognition act. | The specific anchor. The member must recognise the exact post or contribution being referenced in Sentence 1. If the operator cannot name the specific contribution (author, date, and a summary of the content), the first DM will feel generic. The specificity signal tells the member that the operator read their post and found it worth acting on — which is itself a recognition act before the spotlight has been proposed or accepted. | 55–65% “yes” or “I’d be happy to chat” response rate. The primary non-response pattern is not a “no” but a delay (the member sees the DM, intends to respond, and forgets). The second DM handles this without judgment. |
| Second DM — explicit process description | 3–4 days after the first DM if no response. Do not send on the day after the first DM (too immediate, reads as pressure). Do not wait more than 5 days (the novelty of the recognition fades; the member’s memory of the original contribution becomes less fresh). The second DM is for non-respondents only; members who responded to the first DM do not receive the second. | Three sentences. Sentence 1: acknowledge the likely reason for no response without judgment. “No rush on my note from [day] — totally understand if timing is off.” Sentence 2: describe the process explicitly so the member knows exactly what they are agreeing to. “If it’s helpful: the conversation is five questions over DM (no call needed), takes about 20 minutes to write back answers, and you’d see the draft before anything goes live.” Sentence 3: a low-friction yes signal. “If you’re interested, just reply and I’ll send the questions directly.” The process description in Sentence 2 is the key element: many non-responders to the first DM are not uninterested but are uncertain about the time commitment or worried about being locked into a format they cannot review before publication. | The process description. Most spotlight non-responses to the first DM are driven by uncertainty about what “a short spotlight conversation” actually means in practice: Does it require a video call? How long will it take? Who will write the final text? Will the member be quoted directly? The explicit process description in the second DM answers all four questions in a single sentence without making the member ask them, which removes the friction of having to request clarification before agreeing. | An additional 15–20% of members who did not respond to the first DM respond to the second, bringing total acceptance to 70–75% after DM 2. The process-description format converts undecided members who were interested but uncertain into confirmations. |
| Third DM — easy opt-out | 5–7 days after the second DM if still no response. This DM is the final contact in the sequence and is sent to members who have not responded to either the first or second DM. Do not send a third DM to members who responded to DM 1 or 2 with anything other than a clear “no.” The third DM is not a final attempt to convert; it is a permission-giving close that protects the operator’s relationship with the member regardless of the spotlight outcome. | Two sentences. Sentence 1: give an explicit easy opt-out. “If spotlights aren’t your thing or the timing is off, no worries at all — just let me know and I won’t bring it up again.” Sentence 2: leave a forward-looking door open without creating pressure. “If you’re ever interested down the road, I’ll be running more of these.” Do not: apologise for the previous two DMs, offer to do a different format, or ask if there is a better time. The opt-out DM’s job is to close the sequence gracefully, not to re-pitch the spotlight. | The easy opt-out. Members who receive a third DM without an explicit exit option experience the sequence as pressure, which damages the operator’s relationship with the member even if the member was simply too busy to respond. An explicit “no worries if not your thing” signal converts the third DM from a pressure point into a relationship-maintaining contact. Members who decline the spotlight via the third DM are more likely to accept a future spotlight invitation than members who do not receive the third DM and simply ghost the sequence. | An additional 5–8% of total outreaches convert via DM 3 (members who finally have the time to respond and who needed the explicit opt-out to feel comfortable saying yes without the pressure of two unanswered DMs). Most DM-3 conversions are confirmations, not opt-outs — the opt-out framing reduces perceived pressure enough that members who wanted to say yes but felt awkward about the delay respond affirmatively. Total sequence conversion rate after DM 3: 65–75% of outreaches result in a completed spotlight interview. |
Three measurement metrics
Three metrics determine whether a member spotlight programme is producing contribution-catalysis outcomes. These are not the same as the community-wide metrics in the paid community metrics dashboard reference card — they are spotlight-programme-specific leading indicators that are measurable within 14–30 days of each spotlight’s publication. The table below defines each metric, specifies the healthy benchmark and at-risk threshold, describes the intervention for each band, and explains how to measure it from data available in Slack without additional tooling.
| Metric | Definition | Healthy benchmark | At-risk threshold | Intervention | Measurement method |
|---|---|---|---|---|---|
| 14-day re-contribution rate | The percentage of spotlighted members who post at least one original message (thread-starter, not a reply) in any public channel within 14 days of their spotlight going live. Measures whether the spotlight’s Q5 forward commitment is producing a specific next contribution. A member who replies to others’ posts during the 14 days but does not start an original thread is counted as not re-contributed for this metric, because the spotlight is designed to catalyse original contribution, not reply behaviour. The 14-day window is set from the spotlight publication date, not from the completion of the Q5 follow-up DM, because the social commitment produced by Q5 is made at the moment of publication, not at the moment the operator checks in. | ≥60% for contribution spotlights (2–6 month members). ≥45% for journey spotlights (6+ month members, whose contribution cycles are longer). Both benchmarks require Q5 to be answered with channel-specific, timeline-specific specificity. Communities that include Q5 but leave it vague achieve 30–45% 14-day re-contribution rates — better than achievement-only spotlights but below the contribution-catalysis benchmark. The 15–30 percentage point lift vs. a control cohort of similarly-tenured non-spotlighted members is the most rigorous benchmark: a programme with 60% re-contribution rate is producing a strong lift if the control cohort posts at 30–35% in the same 14-day window. | 40–60% for contribution spotlights, indicating that Q5 is either missing, vague, or not being followed up with the 10–14 day operator DM. Below 40% for contribution spotlights: the spotlight is running as an achievement-summary format, not a contribution-catalysis format. Check whether Q5 is included, whether Q5 answers are channel-specific, and whether the operator is sending the day-10–14 follow-up DM. | 40–60%: audit Q5 answers in the last 5 spotlights. If any Q5 answers are vague (“I’ll share more soon”), add one editing step to the next spotlight: work with the member to name the specific channel, the specific output, and the approximate timeline before the spotlight goes live. Add the day-10–14 follow-up DM to the operator’s spotlight checklist if it is not already there. Below 40%: Q5 may be missing entirely from the interview, or the operator may be writing achievement-summary spotlights from LinkedIn profiles rather than using the five-question interview format. Switch to the full interview process for the next 4 spotlights and measure 14-day re-contribution rate for that cohort. | Manual tracking via a simple log: for each spotlight published, record the member name, publication date, Q5 commitment summary, and the date of the member’s next original post in any public channel within 14 days. At the end of each month, count how many of that month’s spotlighted members posted within 14 days of their spotlight and divide by the total number of spotlights published that month. For communities running bi-weekly spotlights (2–3 per month), this is a 5–10 minute monthly calculation. Communities with a Slack app can automate the tracking by querying the member’s post history in a 14-day window from spotlight publication date. |
| Peer-nomination rate | The percentage of spotlight subjects who were nominated by another community member (via the peer-nomination DM system) rather than selected by the operator. Measures whether the spotlight programme has expanded beyond an operator-selection process into a community-wide recognition system. A spotlight is counted as peer-nominated if the operator first learned of the member’s recent contribution through a nomination DM from another member, regardless of whether the operator had also considered the member independently. Spotlights where the operator sourced the candidate independently (from their own observation of the community) are counted as operator-selected even if a peer nomination arrived after the selection was made. | >30% of total spotlights sourced from peer nominations after 3 months of running the peer-nomination system. Above 30% indicates that established members have internalised the contribution-catalysis purpose of spotlights and are actively identifying community contributions worth recognising. A peer-nomination rate above 50% signals that the programme is self-sustaining: the operator’s monthly nomination-request DMs are generating more candidates than the operator can spotlight, which is the target state for a mature spotlight programme. | 15–30% after 3 months of running the nomination system, indicating that the monthly nomination DMs are reaching too narrow a pool or that the single-question DM format is not converting to nominations. Below 15% after 3 months: the nomination system is not working. Most likely causes: the monthly DM is going to the same 3–5 members every month (nomination pool too narrow), or the DM is asking for a written recommendation rather than a single member name (cognitive cost too high). | 15–30%: expand the monthly nomination DM pool from 3–5 members to 8–10, rotating through the top 20–30 most active members over the course of 3 months. If the DM is asking more than one question, simplify to the single-question format: “Who in the community has shared something in the past month that you think more people should know about? Just a name.” Below 15%: close the nomination feedback loop actively for the next 3 spotlights: notify the nominating member before the spotlight publishes (“Your nomination of [member] is going up on [day] — wanted you to know first”) and add a line to the spotlight text crediting the nomination origin without naming the nominator (“This spotlight came from a member recommendation”). The visible feedback loop is what recruits future nominators: members who know that their nominations lead to visible spotlights participate in the nomination system at 3–4× the rate of members who receive no feedback on prior nominations. | Track in the same log as 14-day re-contribution rate: add a column for “source” (operator-selected or peer-nominated) for each spotlight. At the end of each month, calculate peer nominations divided by total spotlights. The source is easy to track at the time of candidate identification; trying to reconstruct source from memory at the end of the month produces errors. Log the source when the candidate is first identified, not when the spotlight is published. |
| Thread depth | The number of replies the spotlight post receives in the community channel where it is published, counted in the 48 hours after the spotlight goes live. Thread depth measures whether the spotlight is generating peer recognition — the second-order purpose of the format, after re-contribution catalysis. A spotlight that produces a strong Q5 commitment (re-contribution rate) but generates zero replies is functioning as a one-to-one operator-member recognition act rather than a community-wide recognition event. Both are valuable, but only thread depth above the 5-reply threshold produces the observational learning effect where non-spotlighted members watch the spotlight receive replies and infer that public contribution is recognised and valued in this community. | 5–12 replies within 48 hours. Below 5 replies, the spotlight post is not generating enough community engagement to produce the observational learning effect. Above 12 replies indicates a particularly high-resonance spotlight (strong anchor, strong Q3 answer, strong Q4 invitation to other members) — not a problem, but also not the typical target. Replies from the spotlighted member themselves and from the operator are counted separately from peer replies: the thread depth benchmark of 5–12 should be met by peer replies (replies from members other than the spotlighted member and the operator) for the observational learning effect to function. | 3–5 replies within 48 hours: spotlight is generating mild engagement but not the community-wide recognition event that makes spotlights compound. Below 3 replies: spotlight is generating almost no community response, indicating that either the anchor is not recent or memorable enough for readers to remember it, the Q4 peer-invitation language is missing, or the spotlight is being posted in a channel that is not regularly read by established members. | 3–5 replies: check whether the operator’s personal note is included in the spotlight post (operator notes drive 1–2 additional replies from members who respond to the operator’s framing). Check whether Q4 (“what would you say to members sitting on something similar?”) is answered specifically enough to invite reader response — a vague Q4 answer produces no replies from ‘sitting on something’ members because there is no explicit invitation to self-identify. Tag 2–3 members (whose goal tracks match the spotlight’s topic) directly in the comments at the 6-hour mark if the thread has fewer than 3 replies. Below 3 replies: check the channel: spotlights posted in a low-traffic or specialised channel (e.g., #announcements or a goal-track-specific channel) produce lower thread depths than spotlights posted in the main content channel. Move the spotlight post to the main content channel where the weekly thread prompt runs. Check spotlight timing: spotlights posted on Friday afternoon or over the weekend receive 40–60% lower thread depth than spotlights posted Tuesday or Wednesday morning. | Count replies in the spotlight thread at the 48-hour mark from publication. In Slack, open the thread, scroll to the bottom, and count non-operator, non-spotlighted-member replies. Log in the same spreadsheet as 14-day re-contribution rate and peer-nomination rate: three columns, one row per spotlight. The rolling 4-spotlight average of thread depth is more informative than single-spotlight readings for identifying trend vs. noise. A single spotlight with 1 reply in a month where all others have 7–10 replies may reflect posting timing or member activity levels that week rather than a spotlight programme problem; a 4-spotlight average below 4 is a programme-level signal. |
Metric sequence for diagnosis. Check 14-day re-contribution rate first: if below target, the spotlight’s contribution-catalysis mechanism is broken (Q5 missing, vague, or unconfirmed). Fix Q5 before looking at the other two metrics. If re-contribution rate is healthy, check peer-nomination rate: if below 30%, the programme is still operator-dependent and will not scale without adding the peer-nomination system. If both are healthy, check thread depth: below 5 replies means the spotlight is working as a one-to-one recognition act but not as a community-wide recognition event — fix posting timing, channel, Q4 specificity, and operator note before adding other interventions.
Frequently asked questions
What questions should a paid community member spotlight include?
A paid community member spotlight should include five questions designed to catalyse re-contribution rather than celebrate past achievements. Question 1 (“What did you share, and what made you decide to post it here rather than keep it to yourself?”) anchors the spotlight to a specific community act. Question 2 (“What prompted you to post at that particular moment?”) connects the contribution to community context. Question 3 (“What surprised you most about the response you got?”) surfaces the identity-continuation effect through the peer-response signal. Question 4 (“What would you say to a member sitting on something similar?”) creates a direct peer-to-peer invitation to non-posting members. Question 5 (“What are you working on that you might bring to the community next?”) is the re-contribution trigger: members who answer Q5 with specificity produce 14-day re-contribution rates of 60–80%, versus 20–35% for spotlights that end at Q3 or Q4. The five-question set must be conducted in order; combining or skipping questions disrupts the dependency chain between the anchor (Q1), community context (Q2), peer-response validation (Q3), reader invitation (Q4), and forward commitment (Q5). See the five-question set reference table above for what each question does mechanically and the failure mode if skipped.
How do you measure whether a member spotlight programme is working?
Three metrics determine whether a member spotlight programme is producing contribution-catalysis outcomes. First: 14-day re-contribution rate — the percentage of spotlighted members who post at least one original message in any public channel within 14 days of their spotlight. Healthy: ≥60% for contribution spotlights, ≥45% for journey spotlights. Below 40% indicates the spotlight is running as an achievement-summary format. Second: peer-nomination rate — the percentage of spotlights sourced from peer nominations via the monthly nomination DM. Healthy: >30% after 3 months. Below 20% means the nomination system is not yet generating candidates at a self-sustaining rate. Third: thread depth — replies from non-operator, non-spotlighted members within 48 hours of publication. Healthy: 5–12 replies. Below 5 indicates the spotlight is generating a one-to-one recognition act rather than a community-wide recognition event. The most rigorous measurement for isolating spotlight effect from general community activity is the lift-vs-control comparison: 14-day post rate of spotlighted members minus 14-day post rate of a control cohort of similarly-tenured non-spotlighted members. Target lift: 15–30 percentage points.
What is the difference between a contribution spotlight and a journey spotlight?
The contribution spotlight anchors to a specific, recent community act (a post, shared resource, or question with significant replies) and is best suited for members with 2–6 months of tenure. It produces a concrete example of the kind of contribution the community values, embedded in a story about why the member decided to share, and a forward commitment (Q5) about what they will bring next. The journey spotlight anchors to a before/after arc — the member’s state in a relevant domain before joining versus now — and is best suited for members with 6+ months of tenure. It produces a social-proof narrative demonstrating concrete transformation attributable to community participation, aimed primarily at members approaching month-6 or month-12 renewal decisions. Both formats share the same structural specs (400–600 words, Tuesday or Wednesday morning, personal operator note), and both use the same five-question set with Q1 adapted for journey spotlights (“What was the specific moment or thing in this community that marked the shift?” instead of “What did you share?”). The primary risk of the contribution spotlight is spotlight-as-achievement-summary (describing who the member is rather than what they did in the community); the primary risk of the journey spotlight is a vague before/after arc that reads as a testimonial rather than a specific, attributable story.
How do you run a peer nomination system for community spotlights?
The peer nomination system operates through a monthly direct message to 3–5 of the community’s most recently active members, asking a single question: “Who in the community has shared something in the past month that you think more people should know about? Just a name.” The single-question format is critical: multi-part nomination forms reduce response rates by 60–70% relative to single-question DMs. Rotate through the top 20–30 most active members rather than using the same 3–5 people each month, to avoid nomination pool bias. When a nominee is selected, notify the nominating member privately before the spotlight publishes: “Your nomination of [member] is going up on [day] — wanted to let you know first.” This feedback loop is what produces compounding participation in the nomination system: members who observe that their nominations lead to visible spotlights nominate again at 3–4× the rate of members who receive no nomination feedback. Target: more than 30% of all spotlights sourced from peer nominations within 3 months of launching the system. Below 20% after 3 months indicates the nomination pool is too narrow or the DM is too high-friction.