> For the complete documentation index, see [llms.txt](https://lumeon.gitbook.io/lumeon-archive/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lumeon.gitbook.io/lumeon-archive/unsorted/circle-feed-guide.md). # Circle Feed Guide ***Tend the Rhythm. Trust the Culture.***

{% tabs %} {% tab title="What" %} ^{**What it is**} A practical reference guide for anyone stewarding a Circle feed within Collective Canopy. It covers the weekly posting rhythm, post categories, writing and engagement principles, common pitfalls, and what to do when things go quiet. Circle-agnostic: the principles apply to any circle regardless of domain. {% endtab %} {% tab title="Why" %} ^{**Why it exists**} The feed is where circle culture is built or lost. A well-tended feed creates belonging, sparks exchange, and keeps practice alive between gatherings. A neglected feed signals abandonment. A performative feed signals inauthenticity. This guide helps Core Team members find the rhythm between those extremes: consistent without being rigid, warm without being forced, structured without being scripted. {% endtab %} {% tab title="How" %} ^{**How it works**} Read the full guide once when you step into a Core Team role. It takes about 12 minutes. Then use it as a reference you return to when you need to recalibrate. Each section is self-contained so you can jump to what is relevant. Look for the tip boxes throughout for quick, actionable guidance and the dropdown sections for deeper examples and context when you want them. {% endtab %} {% endtabs %} ## **Introduction** #### The feed is the heartbeat of your circle. Not the Commons, not the quests, not the gatherings. The feed. It is where members show up between the structured activities. It is where culture is established through hundreds of small interactions: a question asked, a failure shared, a resource passed along, a moment of recognition between two people who have never met in person. Your job as a Core Team member is not to fill the feed with content. It is to create the conditions where members want to contribute. That means posting with consistency and intention, responding with care, modeling the tone you want to see, and knowing when to step back and let the community carry itself. This guide gives you the tools to do that well. It is not a content calendar or a social media playbook. It is a set of principles and practical patterns that work across any circle, at any stage of maturity. Some of what follows will feel obvious. Some of it will only click after you have been stewarding for a few weeks and encounter the exact situation described. Both are fine. The single most important thing to remember: the feed is a garden, not a stage. You are tending conditions for growth, not performing for an audience. Some weeks the garden is lush. Some weeks it is quiet. Both are natural. Your consistency through both is what builds trust. ## **Why the Feed Matters**

#### **The feed is often treated as the least important part of a community platform. The real work, people assume, happens in the quests, the gatherings, the Commons. The feed is just the space in between.** #### **That assumption is wrong. The feed is where belonging is built.**

#### **Where Belonging Is Built** Quests are individual. Gatherings are periodic. The Commons is a reference layer. But the feed is continuous. It is where a member opens the app on a Wednesday afternoon and sees someone else working through the same challenge they are. It is where a question posted at midnight gets a thoughtful reply by morning. It is where a new member reads three months of conversation and thinks: these are my people. Research on community health consistently shows that the single strongest predictor of long-term member retention is not content quality or event frequency. It is the feeling of being seen and responded to by peers. The feed is where that happens. Every reply, every reaction, every honest post met with recognition rather than silence is a micro-moment of belonging. Enough of those and the member stays. Too few and they drift. {% hint style="info" %} **💡 The 2-Post Minimum** If your team can only commit to two feed posts per week, make them Monday (First Breath) and Wednesday (Midline Check). These two posts maintain the circle's heartbeat at minimal effort. Monday gives members something to commit to. Wednesday gives them a reason to pause and check in. Everything else is valuable but these two are essential. {% endhint %}

#### **Your Highest-Leverage Minutes** For Core Team members, feed stewardship is not a secondary task you do when the "real work" is done. It is foundational infrastructure. The 10 minutes you spend crafting a thoughtful Monday post or replying to a member's field report are among the highest-leverage minutes you will invest in your circle's health. This does not mean you need to post constantly, respond to everything, or manufacture activity. Forced engagement is worse than silence because it teaches members that the feed is performative rather than real. What it means is that you show up with consistency, set a rhythm members can rely on, and treat the feed as a space worthy of the same care you give to your quests and gatherings. {% hint style="info" %} 🔍 **Reflection** Think about a community you have been part of where you felt genuinely welcomed and seen. What was happening in the feed or equivalent space? What made you want to come back? What would have made you leave? The answers to those questions are your most reliable compass for stewarding this feed. {% endhint %}

📂 The Evidence Behind Feed-First Culture

Community platforms like Mighty Networks, Circle, and Discord have published internal research showing that communities with consistent weekly posting rhythms retain 40-60% more members over six months compared to communities with sporadic activity. The key variable is not volume (more posts) but predictability (members can rely on something showing up at a regular cadence). Separately, research on online communities of practice (Wenger, Trayner, de Laat, 2011) identifies three critical functions of the shared space between structured activities: mutual engagement (members interact), joint enterprise (members feel co-ownership), and shared repertoire (members develop common language and references). The feed is where all three develop organically. Without it, the community becomes a program people attend rather than a culture they belong to. This does not mean every circle needs a hyperactive feed. It means every circle needs a feed where showing up feels worthwhile. Quality of interaction matters more than quantity of posts.

## **The Weekly Rhythm** ***A scaffold, not a schedule***

#### The weekly rhythm is the most important structural tool you have as a feed steward. It gives the feed a predictable pulse that members can rely on without requiring you to post every day or manufacture content when there is nothing to say. Think of it as a scaffold that holds the space open. Some weeks every slot gets filled. Some weeks only two do. The scaffold stays either way, and members learn to trust that the rhythm will return even when a week is quiet. The rhythm is built around a natural energy arc that moves from activation at the start of the week through reflection at the midpoint to release at the end. This mirrors how most people experience their weeks and creates a feed that feels alive rather than random. #### **The Five Slots**

Day	Slot	Energy	What It Does
Monday	First Breath	Activating	Starts the week with a micro-challenge or intention. Gives members something specific to commit to publicly.
Tuesday	Signal Drop	Curating	Shares a resource with personal context. Models the resource-sharing behavior the feed needs to sustain itself.
Wednesday	Midline Check	Centering	A brief prompt that asks members to pause and check in. Lowest barrier post of the week. Often generates the most responses.
Thursday	Deep Dive	Deepening	Longer-form content: a field report, a practitioner insight, a question that requires real thought. The richest post of the week.
Friday	Unwind	Releasing	Light, funny, or celebratory. Ends the week with warmth. Permission to not be serious.

{% hint style="info" %} **💡 The Energy Arc** The week moves from doing **(Monday)** through sharing **(Tuesday)** to feeling **(Wednesday)** to thinking **(Thursday)** to laughing **(Friday)**. This arc is not accidental. It matches the natural rhythm of engagement in communities of practice: members are most action-oriented early in the week, most reflective midweek, and most social toward the end. Work with this energy rather than against it. {% endhint %}

#### **Flexibility Principles** The weekly rhythm is designed to be adaptive, not rigid. Here are the principles that keep it useful without making it a burden: **Consistency beats completeness**\ Posting Monday and Wednesday every single week for three months builds more trust than posting all five slots for two weeks and then going silent. Members do not need a full calendar. They need reliability. Choose the slots your team can sustain and protect those above all else. **Slots can shift**\ If something significant happens on a Tuesday that deserves a Deep Dive, post it on Tuesday. The slot names describe energy and function, not fixed calendar positions. A First Breath post on a Tuesday still works if that is when the week needs activation. **Members fill the gaps**\ As the circle matures, members will begin posting resources on Tuesdays and reflections on Wednesdays without being asked. This is the goal. The weekly rhythm is not meant to be owned by the Core Team permanently. It is meant to model a pattern that the community eventually carries itself. When you notice members naturally posting in the rhythm slots, you are succeeding. **Silence is allowed**\ If Thursday arrives and there is no Deep Dive to post, do not force one. A missing Thursday post is invisible. A low-quality Thursday post that feels manufactured is visible and corrosive. Better to skip a slot than fill it with something that teaches members the feed is performative.
{% hint style="info" %} **💡 The Two-Person Rotation** If your Core Team has at least two people involved in feed stewardship, split the week. One person owns Monday and Tuesday. The other owns Wednesday and Friday. Thursday floats to whoever has something substantial. This prevents burnout, ensures coverage if someone has a busy week, and brings two different voices into the feed, which feels more like community and less like a broadcast channel. {% endhint %} #### **Seasonal Adaptation** The weekly rhythm stays consistent in structure but adapts in content as the season progresses. Here is how: **Early season **^{**(weeks 1-3)**}\ The feed leans toward orientation and invitation. Monday posts introduce the seasonal theme through accessible micro-challenges. Wednesday prompts connect to the new theme. Resources point members to the seasonal playbook and starter materials. The energy is welcoming and low-barrier. **Mid-season **^{**(weeks 4-8)**}\ The feed deepens. Monday challenges increase in specificity. Thursday Deep Dives feature member field reports and emerging insights. Polls begin surfacing preferences for the next season. The energy shifts from "try this" to "what are you discovering?" **Late season **^{**(weeks 9-12)**}\ The feed moves toward reflection and harvest. Wednesday prompts ask members to look back across the season. Thursday posts highlight the best contributions and surface them for the Commons Library. Friday Unwind posts celebrate wins and mark the closing of the cycle. The energy is integrative and forward-looking. This seasonal arc means you are never posting the same kind of Monday post for twelve consecutive weeks. The rhythm stays the same. The content evolves with the community.

📂 Sample Week at Each Stage

**Early Season Week** ^{**(Week 2)**} * Monday: "This week's practice edge: before your first meal each day, take 5 slow breaths and notice your hunger level on a scale of 1-10. Not to change anything. Just to notice. Who is in?" * Tuesday: Signal drop sharing the seasonal playbook with a note about which section felt most relevant. * Wednesday: "One word for how your body feels at this exact moment." * Thursday: A founding team member posts a Field Report from their own experience with the seasonal theme during the pilot phase. * Friday: "What is the most basic health advice you ignored for years that turned out to be completely right?" **Mid-Season Week** ^{**(Week 6)**} * Monday: "This week, track the first physical sensation you notice when you wake up. Write it down before checking your phone. Five days. Let us see what patterns emerge." * Tuesday: Library highlight resurfacing a member-contributed protocol from earlier in the season that deserves more attention. * Wednesday: "We are halfway through the season. What surprised you most about your practice this month?" * Thursday: Member Field Report on their experiment with the seasonal challenge, following Protocol → Experience → Insight format. * Friday: Celebration post recognizing three members who completed quests this month. **Late Season Week** ^{**(Week 11)**} * Monday: "Final week challenge: teach one thing you learned this season to someone outside the circle. A partner, a colleague, a friend. Report back on what happened." * Tuesday: Resource post connecting the seasonal theme to a broader article or research piece, contextualizing what the circle explored within the wider field. * Wednesday: "One sentence: what did this season change in your practice?" * Thursday: Season retrospective post from the Circle Steward summarizing the most accessed resources, completed quests, and emerging themes to carry forward. * Friday: "Best moment of the season. Go."

{% hint style="info" %} **🔍 Reflection** Look at your team's current capacity honestly. How many posts per week can you sustain for three consecutive months without it feeling like a burden? That number is your real rhythm, not the aspirational five-slot version. Start there. You can always expand. You cannot recover trust after going silent. {% endhint %} #### **Quick Reference: Weekly Rhythm**

Priority	Slots	Minimum Team Effort
Essential	Monday (First Breath) + Wednesday (Midline Check)	1 person, 20 min/week
Strong	Essential + Friday (Unwind)	1-2 people, 30 min/week
Full	All five slots	2 people, 45-60 min/week

Choose the tier that matches your team's real capacity. Upgrade when you are ready, not when you feel you should. ## **Post Categories at a Glance** ***Eight types, one living feed***

#	Category	Purpose	Frequency	Who Posts
1	Weekly Rhythm	Maintain the heartbeat through recurring posts that set each day's energy	Weekly, assigned slots	Core Team
2	Polls	Engage members, surface signals, inform decisions	2-3 per month	Core Team
3	Reflection Prompts	Invite brief, honest self-inquiry connected to practice	1-2 per week	Core Team or members
4	Resources	Share and contextualize relevant external or internal content	Organic	Anyone
5	Field Reports	Structured experiment write-ups: Protocol → Experience → Insight	Organic, encouraged monthly	Members
6	Quest Posts	Announce, spotlight, and celebrate quests	2-4 per season	Quest Weaver
7	Event Posts	Promote, remind, and follow up on gatherings	Tied to event calendar	Core Team
8	Celebrations	Recognize contributions, completions, milestones, and transitions	2-4 per month	Core Team

{% hint style="info" %} **💡 The Balance Check** Once a month, scroll back through the last 30 days of the feed and roughly count how many posts fall into each category. If any single category dominates more than 40% of the feed, something is off balance. If any category has zero posts, something is being neglected. This takes five minutes and gives you a clear picture of feed health {% endhint %}

#### **Understanding Each Category** **Weekly Rhythm** posts are the backbone. They follow the five-slot structure (First Breath, Signal Drop, Midline Check, Deep Dive, Unwind) and are covered in detail in Section 2. These are the posts you plan. Everything else is the posts you respond to or invite. **Polls** serve three different functions and it is important to know which one you are using. A Pulse Check gathers a quick temperature read on a topic. A Preference Signal informs upcoming programming. An Experience Map normalizes shared struggles by making private experiences visible. A Decision Poll facilitates lightweight governance. Keep polls short (no more than 6 options) and always include one option that gives permission to the person who is struggling or disengaged. **Reflection Prompts** are the lowest-barrier post type. They ask for one sentence or one word. Their power is in specificity: a good prompt narrows attention to a single point rather than asking a broad open question. "Where is your body holding tension right now?" works. "How are you feeling today?" does not. Prompts land best on Wednesdays (Midline Check slot) but can appear any day. **Resources** are the most common member-contributed post type. The critical difference between a valuable resource post and a link drop is personal context. Every resource share should include why the person is sharing it and what specifically resonated with them. If members are posting links without context, gently redirect: "Great find. What specifically stood out to you?" This establishes the norm early.

📂 Resource Post Structure

Every resource post, whether from a Core Team member or a community member, works best with this structure: * **#signal** tag (consistent across all resource shares for searchability) * **What it is** (format, length, author) * **Why it matters to you** (1-3 sentences of personal context) * **Connection** (how it relates to current season, a quest, or an ongoing discussion) * **Invitation** (a question that opens discussion) You do not need to enforce this as a template. But when Core Team members consistently model this structure, members will begin mirroring it naturally.

**Field Reports** are the circle's most valuable knowledge creation mechanism. They follow a consistent format (Protocol → Experience → Insight → Verdict) and turn personal experiments into collective intelligence. The best ones migrate to the Commons Library as contributed protocols. When a Field Report appears in the feed, celebrate it visibly. A short reply from a Core Team member acknowledging the depth and care of the write-up reinforces the behavior and signals to other members that this kind of contribution is valued. **Quest Posts** connect members to the quest ecosystem. These include new quest announcements, spotlights on underutilized quests, seasonal roundups, and completion celebrations. The most effective quest posts are timely and contextual. When three people in the feed mention struggling with sleep, that is the moment to spotlight a sleep-related quest, not when the content calendar says it is time. **Event Posts** come in four flavors: previews (1-2 weeks before), reminders (1-2 days before), optional live updates during the event, and follow-ups (1-2 days after). The most neglected and most valuable of these is the follow-up. It closes the loop for members who could not attend, archives the event's insight, and honors the facilitator's work. Never skip the follow-up. **Celebrations** make the circle's value systems visible and human. They recognize member contributions, quest completions, role transitions, and collective milestones. The tone should feel like one friend telling the room about something another friend did that mattered, not like a corporate employee-of-the-month announcement. Always get permission before spotlighting a member. {% hint style="info" %} 💡 **The Category Members Will Not Start On Their Own** Field Reports and Celebrations rarely emerge organically. Members need to see them modeled multiple times before they feel permission to post them. Seed at least two Field Reports from the founding team before expecting member-generated ones. Post at least three celebration posts before expecting members to start recognizing each other publicly. The behavior you model first is the behavior the community adopts. {% endhint %} #### **The Ecosystem Between Categories** Categories do not exist in isolation. The healthiest feeds create chains between them: A **Monday micro-challenge** leads to a **member Field Report** the following Thursday. That Field Report surfaces a resource that becomes a **Signal Drop** the next Tuesday. The resource sparks a **Reflection Prompt** the following Wednesday. A poll mid-month asks which challenge people want to revisit. A Celebration post at the end of the month recognizes the members who documented their experiments. When you see these chains forming organically, the feed has become a living system rather than a content schedule. Your job shifts from generating posts to noticing and amplifying the connections that are already emerging. {% hint style="info" %} **🔍 Reflection** Which of the eight categories feels most natural for you personally? Which feels most uncomfortable? Your answers reveal where the feed will be naturally strong and where it will need deliberate attention. A team member who loves sharing resources but avoids celebrations will create an intellectually rich feed that feels emotionally thin. A team member who gravitates toward reflection prompts but rarely posts resources will create a contemplative feed that lacks practical substance. Know your tendencies so you can balance them. {% endhint %} #### **Quick Reference: Category Priorities by Circle Stage** | Circle Stage | Priority Categories | Secondary | Can Wait | | ---------------------------- | ----------------------------------------------------------------- | ---------------------------------------------------------------- | ----------------------------------------------------------- | | **Pre-launch** (seeding) | Weekly Rhythm, Resources, Reflection Prompts | Field Reports | Polls, Quest Posts, Events, Celebrations | | **Early** (first 1-3 months) | Weekly Rhythm, Resources, Quest Posts, Reflection Prompts | Polls, Event Posts, Field Reports | Celebrations (need real contributions to celebrate) | | **Established** (3+ months) | All categories active | Field Reports and Celebrations become increasingly member-driven | Core Team gradually shifts from creating to amplifying | | **Mature** (6+ months) | Core Team focuses on Weekly Rhythm, Celebrations, and Quest Posts | Members drive Resources, Field Reports, Reflection Prompts | The feed sustains itself with lighter Core Team involvement | This progression is the natural lifecycle of a healthy feed. If your circle is six months old and the Core Team is still generating 80% of the content, something needs adjusting. See Section 7 (Troubleshooting) for diagnostic guidance. ## **Writing for the Feed** ***Say it like you would say it out loud***

#### Writing for the feed is not writing an article, a report, or a social media caption. It is closer to standing up in a room full of people you respect and saying something you mean. The best feed posts sound like a real person talking. They are clear, specific, and honest. They do not perform intelligence or vulnerability. They just say the thing. This section gives you a set of principles and practical patterns that make feed writing easier and more effective. None of them are rules. All of them are patterns that consistently produce posts members actually read and respond to. #### **The Three Qualities of a Good Post** Every effective feed post, regardless of category, shares three qualities. If your post has all three, publish it. If it is missing one, fix it. If it is missing two, start over. **Specific**\ A good post is about one thing. Not wellness in general. Not a broad reflection on the season. One specific challenge, one resource, one observation, one question. Specificity is what makes a post feel real rather than generic. "I noticed I hold my breath every time I open my laptop" is specific. "Breathing is so important for our well-being" is not. **Honest**\ A good post says what is actually true for the person writing it, including uncertainty, failure, and not-knowing. Honest does not mean confessional. It means the post would not change if the person knew exactly who was reading it. The gap between what we say publicly and what we actually experience is where trust erodes. Close the gap. **Open**\ A good post leaves a door for others to walk through. It ends with a question, an invitation, or a space for response. A post without an opening is a broadcast. A post with one is a conversation. The opening does not have to be a formal question. Sometimes it is just the vulnerability of sharing something unfinished and letting others complete it. {% hint style="info" %} **💡 The Pub Test** Before you post, read it back to yourself and ask: would I say this out loud to a circle member over a drink? If it sounds natural spoken, publish it. If it sounds like something from a newsletter or a corporate update, rewrite it until it sounds human. {% endhint %}

#### **Formatting That Works** How a post looks matters almost as much as what it says. Members scroll quickly. If a post looks like a wall of text, most people will skip it regardless of quality. These formatting patterns make posts scannable without making them feel like marketing content. **Keep it short by default**\ Most feed posts should be 3-8 sentences. If you need more than that, you are writing a Deep Dive or a Field Report, which is fine, but know that is what you are doing. Reflection prompts and Monday challenges should be under 5 sentences. If you cannot say it briefly, you have not found the core of what you want to say yet. **Use line breaks generously**\ Every new thought gets its own line. Dense paragraphs on a mobile screen become unreadable blocks. White space is a kindness to the reader. A post with five short lines separated by space is read. A post with the same content in one paragraph is skipped. **Bold sparingly and with purpose**\ One bolded phrase per post, maximum. Bold draws the eye, so use it on the single element that matters most: the challenge, the question, the key insight. If everything is bold, nothing is bold. **Avoid formatting that signals "content."**\ Numbered lists, bullet points, headers, and emojis all have their place, but in a community feed they can make a post feel produced rather than personal. Use them when they genuinely aid clarity (a multi-step challenge, a resource list) and skip them when plain prose works. The feed should feel like conversation, not a newsletter.

📂 Formatting Examples — Before and Afte

**Before (wall of text):** "This week I want to challenge everyone to try something simple. Before your first meal each day, take five slow breaths and notice your hunger level on a scale of 1-10. The idea is not to change your eating habits or judge yourself but just to build awareness of what hunger actually feels like in your body before you respond to it automatically. I have been doing this for two weeks and I noticed that most mornings I am not actually hungry when I eat breakfast, I am just following the routine. Try it for five days and share what you notice." **After (formatted for scanning):** This week's practice edge: Before your first meal each day, take 5 slow breaths. Then rate your hunger on a scale of 1-10. Not to change anything. Just to notice what hunger actually feels like before you respond on autopilot. I have been doing this for two weeks. Biggest discovery: most mornings I am not hungry when I eat breakfast. I am just following the routine. **Five days. One breath pause before eating. Who is in?** *** **Before (over-formatted):** "🌟 WEEKLY CHALLENGE 🌟 📋 Steps: 1. Take 5 breaths before eating 2. Rate hunger 1-10 3. Journal your observations ⏰ Duration: 5 days 💪 Difficulty: Easy Drop a 🔥 if you're joining!" **Why this does not work:** It looks like a fitness influencer's Instagram story. The emojis, the numbered list, and the reaction prompt all signal "content" rather than "person talking to people." The substance is identical to the good version above. The formatting changes everything about how it feels.

#### **Voice and Tone** The feed is not a single voice. It is a chorus. Core Team members each bring their own personality, and that diversity is a strength. But there is an underlying tonal range that keeps the feed feeling coherent. Here are the boundaries: **Warm but not soft**\ The tone is kind and welcoming without being gentle to the point of avoiding challenge. "This quest is going to be uncomfortable and that is the point" is warm and honest. "Just do whatever feels right for you, no pressure at all" is soft to the point of meaninglessness. **Direct but not blunt**\ Say what you mean without unnecessary hedging, but remain aware that written words lack the softening cues of spoken conversation. "This did not work for me" is direct. "This is useless" is blunt. The difference is personal ownership versus judgment. **Knowledgeable but not expert**\ Share what you know and what you have experienced without positioning yourself as the authority. "I have found that..." and "In my experience..." create space for others to have different experiences. "Research shows that..." and "The science is clear..." close that space. **Playful but not performative**\ Humor is welcome and necessary, especially on Fridays. But it should feel natural rather than effortful. If a joke requires an emoji to land, it is probably not landing. If something genuinely funny happened, say it plainly. Understatement is almost always funnier than exaggeration in a community context. {% hint style="info" %} **💡 The Voice You Are Not** Whenever you are unsure about tone, it helps to know what you are not. The feed voice is not a wellness influencer (no toxic positivity, no optimization language). It is not an academic (no jargon without explanation, no distanced objectivity). It is not a fitness coach (no motivational shouting, no push-through-the-pain energy). And it is not a therapist (no diagnostic framing, no unsolicited emotional interpretation). Knowing what you are not is often more useful than defining what you are. {% endhint %} #### **Common Writing Traps** **The preamble**\ Starting a post with context nobody needs. "So I have been thinking a lot about this lately and I was not sure whether to post it but I decided to just go ahead because..." Delete everything before the actual point. Start with the point. **The hedge**\ Qualifying every statement until it means nothing. "I might be wrong but I sort of feel like maybe breathwork could potentially be helpful for some people in certain situations." If you believe something enough to post it, say it. "Breathwork changed my sleep. Here is what I did." **The lecture**\ Explaining a concept in detail that nobody asked for. The feed is not a classroom. If you want to go deep on a topic, write a Field Report or a resource for the Library. In the feed, share the insight, link to the depth, and ask what others think. **The echo**\ Repeating what someone else just posted in slightly different words to show you agree. Instead of restating, add something new: your own experience, a counter-example, a question that pushes the idea further. Agreement is a reaction button. Contribution is a reply. {% hint style="info" %} **🔍 Reflection** Pull up the last three posts you wrote for any community, social media, or group context. Read them back with fresh eyes. Do they pass the pub test? Are they specific, honest, and open? Where did you preamble, hedge, or lecture? Most of us have a default trap. Knowing yours means catching it before you hit publish. {% endhint %} #### **Quick Reference: Writing Checklist** Before publishing any feed post, run through these five checks: | Check | Question | | ------------- | --------------------------------------------------- | | **Specific** | Is this post about one thing? | | **Honest** | Would I say this exactly the same way in person? | | **Open** | Is there a door for someone to walk through? | | **Scannable** | Can someone get the gist in 5 seconds of scrolling? | | **Human** | Does this sound like a person or like content? | If all five are yes, post it. If any are no, take 60 seconds to fix it. The difference between a good post and a great post is almost always one small revision. ## Engagement Principles ***Responding is more important than posting***

#### Creating posts gets most of the attention in community stewardship. But how you respond to what others post is where culture is actually shaped. A member who shares something honest and receives silence learns that honesty is not rewarded here. A member who shares something and receives a thoughtful, specific reply learns that this is a space where showing up matters. Your responses teach the community what is valued more powerfully than any post you write. This section covers how to engage with member contributions in ways that build trust, deepen conversation, and grow the circle's collective intelligence. #### **The First Response Principle** When a member posts something, especially for the first time, the speed and quality of the first response determines whether they will post again. This is not about being online 24 hours a day. It is about having a system within the Core Team that ensures no member post goes unanswered for more than 24 hours during the working week. The first response does not need to be long. It needs to be specific. It needs to demonstrate that someone actually read what was written and cared enough to engage with it rather than dropping a generic encouragement.

First Response — Good vs. Generic

**A member posts:** "Tried the cold shower protocol for a week. Days 1-3 were terrible. Day 5 something shifted. I stopped dreading it and started noticing my breathing pattern right before I turned the dial. That moment of bracing is the same thing I do before difficult conversations at work. Never saw that connection before." **Generic response:** "Amazing insight! Thanks for sharing! 🙌" **Why it fails:** It could be a response to literally any post. It does not reference anything specific the person said. It signals "I acknowledged you" without demonstrating "I heard you." **Good response:** "That connection between bracing for the cold and bracing for hard conversations is a really sharp observation. Have you noticed it changing at all? Like, now that you can see the pattern in the shower, does it show up differently at work?" **Why it works:** It names the specific insight. It extends the person's thinking with a genuine question. It invites them to go deeper. The member feels seen and is given a reason to continue the conversation.

{% hint style="info" %} **💡 The 24-Hour Window** Establish a simple rotation within your Core Team: one person is on "first response" duty each day. Their only obligation is to check the feed once and ensure any new member post has received a substantive reply. This takes 5-10 minutes per day and is the single highest-impact engagement habit you can build. {% endhint %}

#### **Six Engagement Patterns** Beyond the first response, there are specific ways of engaging that consistently strengthen feed culture. These are not scripts. They are patterns you can adapt to your own voice. **Name what you see**\ When a member shares an experience, reflect back the specific part that struck you. "The way you described the gap between deciding and doing — that is the part that stayed with me." This tells the person which part of their contribution landed, which is far more valuable than general praise. **Ask the next question**\ The most generative reply is often a single question that takes the conversation one step further. Not a redirecting question that shifts the topic, but a deepening question that helps the person (and other readers) explore their own insight more fully. "What happened the first time you noticed that pattern outside the shower?" **Connect across threads**\ When you notice that two different members have posted about related experiences, bridge them. "This reminds me of what \[member] posted last week about noticing tension before meetings. Have you two compared notes?" These connections are invisible to members who are reading their own thread. Making them visible is one of the Core Team's most valuable functions. **Normalize difficulty**\ When a member posts about struggle, failure, or falling off their practice, resist the impulse to encourage or fix. Instead, normalize. "Three of us had a week like that. The season theme hit harder than expected." Normalization reduces shame and keeps people in the conversation. Encouragement, even well-intended, can feel like pressure to recover faster than is honest. **Amplify quietly**\ Not every great post needs a public celebration. Sometimes the best response is a simple, direct message: "Your Field Report this morning was one of the best things posted in the feed this month. Just wanted you to know." Private recognition can be more meaningful than public praise because it feels personal rather than performative. **Step back when the conversation is carrying itself**\ When members are engaged in a rich exchange, the Core Team does not need to insert itself into every thread. Your presence can actually inhibit peer-to-peer conversation if members start directing their responses toward you instead of each other. Post the opening. Respond to the first few contributions. Then let the conversation breathe. You can always return later with a synthesis or a question that takes it further. {% hint style="info" %} **💡 The Ratio** A healthy target for Core Team engagement: for every 1 post you create, aim for 3-5 substantive responses to member posts. If you are posting more than you are responding, the feed will start feeling like a broadcast channel. If you are responding more than you are posting, the feed feels like a living conversation where the stewards are genuinely present and listening. {% endhint %} #### **Handling Sensitive Posts** Occasionally a member will share something that carries emotional weight: a health scare, a personal loss, a mental health struggle that is connected to their embodied practice. These moments require particular care. **Acknowledge before advising**\ Before offering resources, perspective, or redirection, simply acknowledge what the person shared. "Thank you for trusting us with this. That is not a small thing to put into words." The acknowledgment itself is the most important response. Everything else is secondary. **Do not diagnose or interpret**\ A member sharing that their practice surfaced difficult emotions is not an invitation to explain why. Avoid language like "it sounds like your body is releasing stored trauma" or "this is a classic nervous system response." Even if accurate, this kind of framing can feel presumptuous from a peer. Stay with what the person actually said rather than interpreting it through a framework they did not choose. **Move to private when appropriate**\ If a post reveals something that might need more support than the feed can offer, follow up in a direct message. "I saw your post and I wanted to check in privately. How are you doing with all of this? Is there anything you need?" This creates a container for a deeper conversation without making the public feed feel like a therapy space. **Know the boundaries**\ The circle feed is a community of practice, not a clinical support space. If a member is consistently posting content that suggests they need professional support, the most caring response is a private, honest conversation. "I really value what you bring to this circle. I also want to make sure you have the support you deserve, and some of what you are describing might benefit from working with someone one-on-one. Would it help if we explored some options together?"

📂 When to Respond Publicly vs. Privately

**Respond publicly when:** * The post shares a practice experience, insight, or experiment * The vulnerability is about the work (a failed protocol, a difficult quest, a plateau in practice) * Other members could benefit from seeing the exchange * The person is clearly inviting community response **Follow up privately when:** * The post reveals personal crisis or acute emotional distress * The content might invite well-meaning but unhelpful advice from other members * You sense the person may have shared more than they intended * You need to discuss something about their participation or role **Do both when:** * The post is valuable for the community to witness but the person might need additional support * Public: acknowledge and appreciate the share * Private: check in on how they are doing and whether they need anything

{% hint style="info" %} **🔍 Reflection** Think about the last time you shared something vulnerable in an online space. What kind of response would have made you feel genuinely seen? What kind of response would have made you regret posting? The difference between those two responses is the skill this section is asking you to develop. It is not complicated. It is just attention. {% endhint %} #### **Quick Reference: Engagement Priorities** | Priority | Action | Time | | ------------------- | ------------------------------------------------------------------------ | -------------------- | | **Non-negotiable** | No member post unanswered for more than 24 hours on weekdays | 5-10 min/day | | **High value** | Specific, naming responses to new members' first 3 posts | 2-3 min per response | | **Multiplier** | Connecting related threads across different members | As you notice them | | **Culture-shaping** | Normalizing difficulty and stepping back when conversations self-sustain | Ongoing awareness | ## **What to Avoid** ***Knowing what kills a feed is as useful as knowing what grows one***

#### Most feed stewardship advice focuses on what to do. This section focuses on what not to do. These are patterns that consistently damage feed culture, often with good intentions behind them. They are not mistakes anyone makes once. They are habits that creep in gradually, especially when a Core Team member is tired, under pressure to show activity, or unsure what to post. Recognizing them early is easier than recovering from them later. #### **The Anti-Patterns** **Broadcasting without listening.** The most common failure mode for Core Team feeds. Posts go out on schedule but member posts receive slow or generic responses. The feed starts feeling like a one-way channel: the stewards talk, the members watch. Members tolerate this for a few weeks, then they stop opening the feed entirely. The fix is simple and covered in Section 5: respond more than you post. If you have time for only one activity, choose responding over creating. {% hint style="info" %} **💡 The Broadcast Test** Scroll through the last two weeks of the feed and count two things: posts by the Core Team, and Core Team replies to member posts. If the first number is higher than the second, you are broadcasting.Flip the ratio. {% endhint %} **Performing activity**\ Posting for the sake of showing the feed is active rather than because there is something worth saying. This usually manifests as low-effort posts: a link without context, a vague motivational quote, a prompt so generic it could apply to any community on any platform. Members can feel the difference between a post that exists because someone had something to share and a post that exists because Tuesday needed to be filled. When you have nothing to say, say nothing. A quiet day is better than a hollow one. **Over-facilitating**\ Responding to every comment in every thread, inserting Core Team presence into conversations that are flowing well between members, asking follow-up questions on posts that have already received rich peer responses. Over-facilitation suffocates the organic culture you are trying to grow. It teaches members to direct their contributions toward the stewards rather than toward each other. Know when to plant. Know when to step back and let the garden grow. **Toxic positivity**\ Responding to every post with enthusiasm, praise, and encouragement regardless of content. When someone shares that their practice fell apart this week and the response is "That is so brave of you to share! You are doing amazing!" the message received is that this space does not have room for actual difficulty. Honest acknowledgment ("That sounds like a rough week. You are not the only one.") does more for trust than a dozen exclamation marks.

**Jargon creep**\ Gradually introducing specialized language that new members do not share. Every community develops its own shorthand over time, and that is healthy. But when Core Team posts assume familiarity with terms like "polyvagal response," "somatic mapping," "nervous system regulation stack," or circle-specific references without any context, new members feel excluded. Every post should be understandable to someone in their first week. If you use a technical term, include a brief parenthetical or link. If the post requires a glossary to parse, it belongs in the Library, not the feed. **The correction reflex**\ When a member posts something that is technically inaccurate, the impulse to correct is strong, especially if Core Team members have professional expertise. Resist the public correction unless the inaccuracy could cause harm. A member saying "I read that cold showers reset your vagus nerve" is not dangerous. A public reply saying "Actually, the mechanism is more nuanced than that..." teaches the community that sharing ideas risks being corrected by experts. Instead, add depth without negating: "There is some interesting research on cold exposure and vagal tone. The mechanism is more complex than a simple reset, which actually makes it more interesting. Here is a good overview if you want to dig in." **Inconsistency disguised as flexibility**\ There is a difference between flexible rhythm ("we post Monday and Wednesday, sometimes we add a Thursday") and inconsistency ("we post when we remember to"). Members cannot tell the difference from a single week. But over a month, the pattern becomes clear. If you have committed to a rhythm, protect it. If the rhythm is not sustainable, formally scale it back rather than letting it erode silently. Announced change is leadership. Unannounced change is neglect. **Making it about you**\ Core Team members are also practitioners with their own experiences, and sharing those experiences is valuable. But there is a line between sharing your experience to model vulnerability and centering your experience in every thread. If you notice that your voice is the loudest in the feed most weeks, consciously pull back. Ask more questions. Amplify member voices. Feature others. The feed should feel like a community speaking, not a steward narrating.

📂 The Anti-Pattern Self-Audit

Once a month, take five minutes to honestly assess your feed stewardship against these eight anti-patterns. Score each one: not present (0), occasionally present (1), frequently present (2). | Anti-Pattern | Score (0-2) | | -------------------------------------- | ----------- | | Broadcasting without listening | | | Performing activity | | | Over-facilitating | | | Toxic positivity | | | Jargon creep | | | Correction reflex | | | Inconsistency disguised as flexibility | | | Making it about you | | **0-4:** Healthy range. Stay aware. **5-8:** One or two patterns are creeping in. Address them this week. **9-16:** The feed culture is at risk. Have an honest conversation with your Core Team and recalibrate. This audit works best when each Core Team member does it independently and then compares scores. You will often catch each other's blind spots.

{% hint style="info" %} **💡 The Reversal Habit** For every anti-pattern, there is an equal and opposite positive habit. Broadcasting → respond first. Performing activity → only post what is real. Over-facilitating → step back. Toxic positivity → normalize difficulty. Jargon → write for week-one members. Correcting → add depth without negating. Inconsistency → protect your minimum rhythm. Centering yourself → amplify others. When you catch an anti-pattern, you do not need to analyze it. Just do the reversal. {% endhint %} {% hint style="info" %} **🔍 Reflection** Which of these eight anti-patterns is your most likely default under pressure? Not the one you would never do. The one you would slip into on a busy week when you are tired and just trying to keep the feed alive. Name it honestly. That is the one to watch. {% endhint %} ## **Rhythm Troubleshooting** ***Every feed goes quiet. What matters is what you do next.***

#### No matter how well you steward the feed, you will encounter periods where things feel off. Engagement drops. The same three people post every week. A carefully crafted prompt gets zero replies. A new member joins and never posts. These are not failures. They are signals. And like any signal, they carry information if you know how to read them. This section covers the most common feed challenges, how to diagnose what is actually happening, and practical responses that address the root rather than the symptom. #### **The Feed Has Gone Quiet** This is the challenge every steward dreads and every community experiences. The feed was active for weeks. Then gradually, or sometimes suddenly, the posts slow down. Replies thin out. The space feels empty. **Diagnose before you react**\ Quiet feeds have different causes that require different responses. Posting more content into a quiet feed without understanding why it went quiet is like watering a plant that is drowning. **Possible causes and responses:** **Seasonal fatigue**\ Members engaged intensely early in the season and are now depleted. The energy is not gone, it is resting. Response: lower the bar. Post a Midline Check that requires one word. Share something light on Friday. Do not escalate intensity. Let the feed breathe and the rhythm will resume as energy returns. **The prompt is not landing**\ Your reflection prompts or Monday challenges may have drifted into territory that feels too abstract, too personal, or too demanding. Response: go back to the simplest, most concrete prompt format that worked before. "One word for how your body feels right now" always works. Rebuild from there. **Members are consuming but not contributing**\ The feed has become a reading experience rather than a participation experience. People scroll, absorb, and close the app. Response: post a poll. Polls have the lowest participation barrier of any post type. A member who will not write a sentence will tap an option. Once they have interacted once, the threshold for a second interaction drops significantly. **Something happened outside the feed**\ A difficult gathering, a conflict between members, a seasonal theme that surfaced more than people expected. The quiet is not about the feed. It is about the community processing something. Response: name it. "It has been a quieter week than usual. If the last session stirred something up, that is okay. We are here when you are ready." {% hint style="info" %} **💡 The 10-Day Rule** Do not diagnose a quiet feed until it has been quiet for 10 days. Anything shorter than that is normal fluctuation. Communities breathe. Some weeks are inhale weeks. Reacting to a 3-day quiet spell by flooding the feed with content can actually make things worse by signaling anxiety rather than stability. {% endhint %}

#### **The Same Few People Are Posting** A healthy feed has broad participation. An unhealthy feed has three active members and fifty silent ones. This pattern often means the implicit rules of the feed (what is worth posting, how polished it needs to be, how much expertise is expected) have been set too high by the most active contributors. **Check the implicit standard**\ Are the most active members posting long, eloquent field reports and detailed resource shares? If so, less confident members may feel their contributions do not meet the bar. Response: deliberately post something short, unfinished, and low-stakes. "Tried a new stretch this morning. Not sure if it helped or I just enjoyed the weirdness of it. Anyone else experiment with something odd this week?" This resets the participation threshold. **Activate through direct invitation**\ Some members will never post without being personally invited. Not in a pressuring way, but in a genuine, specific way. A direct message: "You mentioned in the last Pulse session that you had been experimenting with your morning routine. Would you be open to sharing a quick update in the feed? Even a few sentences. I think others would really benefit from hearing your experience." People who would never volunteer will often say yes when asked specifically and told why their contribution matters. **Create structured on-ramps**\ Polls, one-word prompts, and "this or that" posts give silent members permission to participate without the pressure of composing something original. Once they have responded to three polls and a Midline Check, posting a full sentence feels much less daunting. Participation is a muscle. Start with the lightest weight.

📂 The Participation Pyramid

In any community feed, participation naturally distributes into a pyramid: * **1-5%** are frequent contributors (post weekly or more) * **10-20%** are occasional contributors (post monthly, reply regularly) * **30-40%** are active readers (read regularly, react occasionally, rarely post) * **30-50%** are passive members (check in sporadically) This distribution is normal and healthy. The goal is not to make everyone a frequent contributor. It is to ensure that each layer feels valued and has a way to participate at their comfort level. Polls and reactions serve the active reader layer. Reflection prompts serve the occasional contributor layer. Field Reports and Deep Dives serve the frequent contributor layer. When you worry about the "same few people posting," check whether you are actually seeing a problem or simply seeing the natural pyramid at work. The real diagnostic question is: are the occasional contributors increasing or decreasing over time? If increasing, the feed is healthy regardless of how few people are frequent posters.

#### **Posts Are Getting No Engagement** You spend fifteen minutes crafting a thoughtful Thursday Deep Dive. It gets two emoji reactions and zero replies. This is demoralizing but common, and the cause is usually not the quality of the post. **Check the timing.** Was it posted when most members are offline? Community feeds have peak hours that vary by geography and culture. If your circle spans multiple time zones, experiment with posting times and track where engagement clusters. A great post at the wrong hour is invisible. **Check the ask.** Does the post end with something specific enough to respond to? "What do you think?" is too open. "Have you ever noticed this in your own practice?" is more specific but still broad. "What is the first thing that happens in your body when you sit down to work?" is specific enough to answer in one sentence. The more precise the invitation, the easier it is to accept. **Check the length.** Long posts on mobile feeds require scrolling. Many members open the feed in a 30-second window between other activities. If they cannot absorb the post in that window, they bookmark it mentally ("I will come back to this") and never do. If a post consistently gets reactions but no replies, it may be landing emotionally but the response barrier is too high. Consider breaking long posts into a shorter feed post with a link to the full piece in the Library. **Check the pattern.** If a specific post type consistently underperforms, the community may be telling you something about what it values. Three Thursday Deep Dives in a row with low engagement is not bad luck. It is data. Try a different format for that slot. Replace the long-form essay with a sharp question, a controversial take, or a member spotlight. {% hint style="info" %} **💡 The Engagement Seed** When you post something that needs momentum, arrange in advance for one Core Team member or trusted active member to leave a substantive first reply within the first hour. This is not gaming the system. It is priming the pump. A post with one thoughtful reply gets significantly more engagement than an identical post with zero replies. The first response gives permission for the second. {% endhint %} #### **A New Member Joins and Never Posts** This is one of the most important signals to watch for. A member who joins, reads the welcome message, and never participates is not disengaged by default. They are usually uncertain, overwhelmed, or waiting for a clear enough invitation. **The buddy system is the first line.** If your onboarding flow includes a buddy pairing, the buddy's first message should arrive within 24 hours of the member joining. Not a form letter. A short, personal message: "Welcome. I am \[name], your buddy for the first couple of weeks. I have been in the circle for \[time]. If anything feels confusing or you are not sure where to start, message me. No question is too small." **The direct invitation.** If a new member has not posted after one week, a direct message from a Core Team member can make the difference. Keep it warm, specific, and low-pressure: "Hey, I noticed you joined last week. Welcome. If you are still getting oriented, that is completely normal. When you are ready, the Entry Quest is a great first step, and dropping an introduction in the feed whenever it feels right is a nice way to connect. No rush." **The structural on-ramp.** Some people will never introduce themselves unprompted but will happily respond to a prompt that includes them. If you notice several new members are silent, post a targeted Midline Check: "For anyone who joined this month: one word for what brought you here." The collective framing ("anyone who joined this month") removes the spotlight pressure of being singled out while creating a clear invitation to participate.

📂 The Silent Member Timeline

Not all silence is the same. Here is a diagnostic timeline: **Days 1-3 silent:** Completely normal. They are reading, orienting, deciding if this is for them. No action needed beyond the buddy's welcome message. **Days 4-7 silent:** Slightly warm. If the buddy has not heard back, a second gentle message. If the Entry Quest has not been started, a nudge pointing to it. Still normal. **Days 8-14 silent:** The window is narrowing. A direct, personal message from a Core Team member. Not "we noticed you have not posted" (which feels surveillance-like) but "just checking in, how are you finding the space so far?" **Days 15-30 silent:** The member is likely disengaged. One final warm message that does not assume failure: "I know life gets busy. The circle is here whenever you are ready. No catching up needed." Then release the expectation. Some members will return months later. Some will not. Both are okay. **Beyond 30 days:** If the member has never posted, reacted, or completed any quest, they are effectively inactive. This is useful data for understanding your onboarding flow, not a personal failure. Track the percentage of new members who post within their first two weeks. If it drops below 50%, the onboarding experience needs attention.

#### **The Energy Has Shifted After a Difficult Event** Sometimes a gathering, a conflict, or a challenging seasonal theme leaves a residue in the feed. Posts become more cautious. The tone shifts from open to guarded. Members who were active pull back. The feed feels different but nobody is naming why. **Name the shift without dramatizing it.** A post from the Circle Steward that simply acknowledges the energy can release enormous pressure: "Last week's session went to some deep places. I have been sitting with it since. If you are still processing, you are not alone. If you want to share what came up, the feed is here for that. If you need more time, that is equally welcome." **Resist the urge to fix the mood.** Do not follow a difficult event with an artificially upbeat post or a pivot to lighter content. Members can feel the incongruence and it erodes trust. Let the feed be in whatever mood it is in. Post your Monday First Breath as usual, but acknowledge the context: "After a week like that, something simple. Stand up. Stretch for 60 seconds. Come back and tell me where the stretch wanted to go." **Create an explicit processing space if needed.** If the event was significant enough, consider a dedicated post: "Processing Thread — Season 2 Retreat. This is a space to share what came up, what you are sitting with, and what you need. No advice unless asked. Just presence." A labeled container gives permission to be honest while keeping the rest of the feed flowing normally. {% hint style="info" %} **🔍 Reflection** Which of these five scenarios are you most likely to encounter first? Which one would you feel least equipped to handle? Discuss both with your Core Team before they happen. Having a shared understanding of how to respond to feed challenges when things are calm makes it much easier to respond well when things are live. {% endhint %} #### **Quick Reference: Diagnostic Questions** When the feed feels off, work through these five questions in order: | # | Question | What It Reveals | | - | ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------- | | 1 | How long has this been happening? | Whether this is a fluctuation (under 10 days) or a pattern (over 10 days) | | 2 | Did something specific trigger it? | Whether the cause is internal (a difficult event, a conflict) or organic (seasonal fatigue, natural rhythm) | | 3 | Who is still active and who has gone quiet? | Whether the drop is broad (whole community) or concentrated (specific members or member types) | | 4 | What was the last post that generated real engagement? | What the community is actually responding to, which may differ from what you think they want | | 5 | Have you asked? | Sometimes the simplest diagnostic is a direct, honest question to the community or to individual members | ## **Quick Reference Card** ***One page. Everything you need.***

This is the section you screenshot. It compresses the entire guide into a single reference you can glance at before writing a post, during your weekly planning, or when the feed needs attention and you are not sure where to start. Pin it somewhere you will see it. #### **Weekly Rhythm** | Day | Slot | Energy | In One Sentence | | ------- | ------------- | ---------- | --------------------------------------------------------------------- | | **Mon** | First Breath | Activating | Give members one specific thing to commit to this week. | | **Tue** | Signal Drop | Curating | Share a resource and say why it matters to you. | | **Wed** | Midline Check | Centering | Ask members to pause, scan, and respond in one sentence or less. | | **Thu** | Deep Dive | Deepening | Longer-form: a field report, a practitioner insight, a real question. | | **Fri** | Unwind | Releasing | Light, funny, celebratory. End the week with warmth. | **Minimum viable rhythm:** Monday + Wednesday. Protect these two above all else. #### **Post Categories** | Category | What It Does | How Often | | ------------------ | ---------------------------------------------------- | ---------- | | Weekly Rhythm | Sets the heartbeat | Weekly | | Polls | Surfaces signals, sparks participation | 2-3/month | | Reflection Prompts | Invites honest self-inquiry | 1-2/week | | Resources | Shares and contextualizes valuable content | Organic | | Field Reports | Turns personal experiments into collective knowledge | Monthly | | Quest Posts | Connects members to quests | 2-4/season | | Event Posts | Promotes, reminds, follows up on gatherings | Per event | | Celebrations | Recognizes contributions and milestones | 2-4/month | #### **Five Principles** **1. Respond more than you post.** The ratio that builds culture: for every 1 post you create, leave 3-5 substantive replies to member posts. **2. Every post ends with an open door.** A question, an invitation, a space for response. Posts without openings are broadcasts. Posts with them are conversations. **3. Consistency beats volume.** Two posts a week sustained for three months builds more trust than five posts a week that burns out after three. **4. Specific beats general.** "I hold my breath every time I open my laptop" moves people. "Breathing is important for well-being" does not. **5. Silence is data, not failure.** When the feed goes quiet, diagnose before you react. Wait 10 days before calling it a pattern. Then ask the five diagnostic questions. #### **The Three Qualities of a Good Post** | Quality | Test | | ------------ | ----------------------------------------- | | **Specific** | Is this about one thing? | | **Honest** | Would I say this the same way in person? | | **Open** | Can someone walk through the door I left? | #### **Engagement Essentials** **No member post unanswered for more than 24 hours on weekdays.** **Name what you see.** Reflect back the specific part that struck you. **Ask the next question.** One question that deepens, not redirects. **Connect across threads.** Bridge related posts from different members. **Normalize difficulty.** Resist the urge to fix or encourage. Just acknowledge. **Step back when it is flowing.** Your absence can be as valuable as your presence. #### **When Things Feel Off** | Signal | First Response | | ------------------------------------ | ---------------------------------------------------------------------- | | Feed gone quiet | Wait 10 days. Then lower the bar: one-word prompts, polls. | | Same few people posting | Reset the participation threshold with something short and unfinished. | | Posts getting no engagement | Check timing, check the ask, check the length. | | New member silent after 7 days | Personal, warm direct message. Not surveillance. Invitation. | | Energy shifted after difficult event | Name it without dramatizing. Let the mood be what it is. | #### **Eight Anti-Patterns** | Trap | Reversal | | -------------------------------------- | ----------------------------------- | | Broadcasting without listening | Respond first, post second | | Performing activity | Only post what is real | | Over-facilitating | Step back when threads self-sustain | | Toxic positivity | Normalize difficulty | | Jargon creep | Write for the week-one member | | Correction reflex | Add depth without negating | | Inconsistency disguised as flexibility | Protect your minimum rhythm | | Making it about you | Amplify others | {% hint style="info" %} **💡 The Monthly Check-In** Once a month, take 10 minutes with your Core Team: 1. Scroll the last 30 days. Count posts per category. Is the mix balanced? 2. Check the ratio. Are you responding more than posting? 3. Score yourself on the eight anti-patterns (0-2 each). Compare honestly. 4. Name one thing that worked well this month and one thing to adjust. That is your entire feed governance process. Ten minutes. Four questions. Every month. {% endhint %} {% hint style="info" %} **🔍 Final Reflection** The feed is a garden, not a stage. Your job is to tend the conditions for growth, not to perform for an audience. Some weeks the garden is lush. Some weeks it is quiet. Your consistency through both is what builds trust. The members will do the rest. {% endhint %} **That completes the Circle Feed Guide. Eight sections:** | # | Section | Core Message | | - | --------------------------- | -------------------------------------------------------- | | 1 | Why the Feed Matters | The feed is where belonging is built | | 2 | The Weekly Rhythm | A scaffold, not a schedule | | 3 | Post Categories at a Glance | Eight types, one living feed | | 4 | Writing for the Feed | Say it like you would say it out loud | | 5 | Engagement Principles | Responding is more important than posting | | 6 | What to Avoid | Eight anti-patterns that kill feed culture | | 7 | Rhythm Troubleshooting | Every feed goes quiet. What matters is what you do next. | | 8 | Quick Reference Card | One page. Everything you need. | d --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://lumeon.gitbook.io/lumeon-archive/unsorted/circle-feed-guide.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.