The Lurking Protocol and Community Mapping

Learning objectives

• Execute a structured lurking protocol before posting in a new community.
• Complete a community map covering culture, norms, and pain points per subreddit.
• Synthesize Modules 1.1-1.4 into one operational reference.
• Finalize the 20-subreddit ICP map for the Stage Project.

Prerequisites: Lesson 1.4.1.

Core concepts

Lurking is not passive warm-up, it's the research method that makes everything else work. Skipping it is the most common reason well-intentioned founders get their first post removed: they optimized for what they assumed the community valued instead of what actually gets upvoted there.

A structured protocol covers four things per subreddit. Tone: read the top 20-30 posts, technical and terse, casual and meme-heavy, or long-form discussion? Match this register or read as an outsider (Lesson 1.1.1's failure mode). Recurring pain points: what does this community complain about repeatedly? This is market research hiding in plain sight, the raw material for "soft mention," embedding your product in a personal narrative about solving exactly this pain rather than announcing it cold. Format norms: long structured write-ups, short direct answers, or specific flairs? Mod presence: how active and strict, based on visible removals or pinned rules threads?

This is where the AMA insight (Lesson 1.1.1) and trust argument (Lesson 1.1.3) close the loop. The highest-leverage promotional format across every case study reviewed is the AMA, explicitly conversational, giving standing permission to discuss your product. One documented example: a founder's "I built a dashboard after my own analytics nightmare" AMA in r/ecommerce drew 127 upvotes and 43 threaded questions, achievable only because the founder had lurked enough to frame it around the community's real pain points.

Community mapping formalizes this into your Stage Project deliverable: 20 subreddits, each with a fit score, self-promotion policy, tone/format note, and at least one recurring pain point observed directly from real threads. This is not busywork, Stage 2's content calendar and Stage 3's soft-mention comments both pull from it directly. Treat it as living; revisit as norms shift and your read sharpens with more lurking.

Video lessons

Supporting reading

• Brands That Failed Hard on Reddit AMAs, SEJ (https://www.searchenginejournal.com/brands-failed-hard-reddit-amas-can-learn/169693/), revisit for the failed-vs-successful AMA contrast.
• Reddit Marketing Case Study: 12 Wins [2026], ReddiReach Blog (https://www.reddireach.com/blog/reddit-marketing-case-studies-2026), the r/ecommerce AMA case and comparable examples.
• Reddit for Business: Complete 2026 Marketing Guide, Foundation Inc. (same publisher) (https://foundationinc.co/lab/reddit-b2b-brands), revisit for factoring mod strictness into your final map.

Exercise

Run the four-part lurking protocol on 2 subreddits from your shortlist you haven't deeply reviewed yet. Document all four elements.

Assignment (Stage Project component)

Complete your 20-subreddit ICP map: name, approximate size, self-promotion policy, tone/format notes, one documented pain point per subreddit, fit score 1-5.

Claude workflow

• Skill idea: a community map synthesizer normalizing raw lurking notes across 20 subreddits into one consistent document, flagging missing fields.
• Automation: none for the lurking itself, human judgment on real threads can't be shortcut. Claude's role is organizing your own notes afterward.

Expected outcomes

• 2 additional subreddits mapped via the full protocol.
• Completed, consistently-formatted 20-subreddit ICP map ready for submission.
• Can explain how this map will be used operationally in Stage 2 and beyond.