Engagement
Pick one ritual and run it for 60 days before adding anything else. Here's how to design the right one.
Murtaza Bambot
•
May 9, 2026
•
Time min read
The most common mistake community builders make with rituals is running too many. They launch a Monday motivation post, a Wednesday wins thread, a Friday reflection prompt, a monthly challenge, and a quarterly member spotlight, all in the same month, and then wonder why none of them gain traction.
Rituals don't work because they're designed well. They work because they're run consistently long enough to become expected. A member who sees the same prompt format every Tuesday at 10am for six weeks starts to expect it. By week eight, they're thinking about their answer on Monday night. By week twelve, missing it feels like missing something.
That expectation takes time to build. You can't build it across six simultaneous rituals. Pick one, run it without interruption for 60 days, and measure whether it's pulling members back on its own. If it is, you've found a ritual worth keeping. If it isn't, retire it and try something different. Then add a second ritual only after the first is stable.
Victoria Cumberbatch, founder and lead coach at Victorious Coaching with nearly a decade of experience in nonprofits, digital nomad communities, and medical education platforms, teaches a four-step design process adapted from "The Art of Community" by Charles Vogl: Intention, Why, Explain, Acknowledge.
Intention is the feeling you want members to have when the ritual is over. Not "they learned something" but a specific emotional state. A wins thread should leave members feeling recognized and energized. A monthly reflection prompt should leave them feeling clear about their progress. Start with the feeling and design backward to the format. If you can't name the feeling, you haven't defined the ritual clearly enough yet.
Why is the specific problem the ritual solves for members. A Monday commitment post exists because members who publicly commit to one goal at the start of the week are more likely to act on it. A Friday wins post exists because members who end the week celebrating a small win come back next week. The "why" keeps the ritual from becoming hollow over time. When you're six weeks in and participation dips, the "why" is what reminds you to keep running it.
Explain is the specific execution in enough detail that members can participate without being told how every time. The first time you run a ritual, over-explain it. Show an example. Tell members exactly what you're looking for and why. After the third time, you shouldn't need to explain it, the format should be legible from the prompt itself.
Acknowledge is what transforms a task members complete into an experience they look forward to. Every ritual needs a close, a reply, a shoutout, a summary. The wins thread that gets ten responses and zero acknowledgment from the founder teaches members their wins don't matter. The wins thread that gets ten responses and a specific "I want to highlight what [Name] shared this week" teaches them that showing up gets them seen. The acknowledge step is the difference.
For most communities in the first year, the right first ritual is a weekly prompt posted at the same time every week, structured to produce member-to-member replies.
Noele Flowers, community and online learning expert who ran community at Teachable for four years, argues that the content calendar itself is a ritual, and the mistake is treating it as a publishing schedule instead of a repeated experience. The same prompt format, posted at the same time, on the same day, creates the predictability that turns a task into a habit.
The prompts that produce member-to-member conversation share a few characteristics. They ask members to share from their own experience, not to give general advice. They're specific enough that answers naturally differ from each other. They end with an implicit or explicit invitation to reply to someone else's answer.
"What's the one thing you're working on this week that you could use input on?" produces member-to-member replies because someone else in the thread will have faced the same challenge. "What book or resource changed how you think about X?" produces responses people want to add to. Both work because they treat member expertise as the value source, not founder content.
In Heartbeat, you can batch four weeks of weekly prompts in one session using post scheduling, set them to auto-post at the same time each week, and have the entire month of prompts running without daily effort. The ritual runs on its own; your job is to close each one with specific acknowledgment.
Laura Cole Gonzalez, marketing mentor with over 20 years of experience, teaches gamification as the infrastructure for the acknowledge step, the part that makes rituals feel rewarding rather than transactional.
Her PATH framework maps how this works: Point (the ritual trigger), Action (what the member does), Trophy (the recognition), Habit (the behavior that becomes automatic). The trophy step is where most builders underinvest. Generic badges like "Top Contributor" create less sustained engagement than specific ones: "First Post," "10 Events Attended," "Course Graduate." The more precisely the recognition describes what the member actually did, the more it lands as recognition rather than just a status symbol.
In Heartbeat, badges appear automatically on member profiles when they hit thresholds you define: post count, course completion, event attendance, membership tenure. The badge is visible to every member who views that profile. It's ambient recognition, always accumulating, never requiring active management, always answering the question "how am I doing here?" with visible evidence.
The combination that works best: automated badges for consistent participation (they see it happen without being told), plus specific public acknowledgment in the weekly ritual close (the founder sees them specifically). One is scalable. One is human. Both are necessary.
Victoria's most counterintuitive piece of advice: don't design all the rituals yourself.
A ritual a member proposed carries more social weight than one the founder mandated. When a member suggests a Thursday accountability thread and their peers start to participate, the ritual has community ownership. Members feel invested in something they helped build, and more likely to sustain it when participation dips.
Survey your community twice a year: "What recurring experience do you wish existed here?" Compile the responses, share them back, let members vote on what to try. Run the winning idea for 60 days and measure. If it moves your core metric, make it permanent. If it doesn't, retire it transparently.
The rituals members co-create become the ones they defend. When someone suggests retiring a community ritual that a member helped design, that member will push back. That friction is valuable. It means the ritual has become part of what makes the community theirs.
One. Run it consistently for 60 days before adding a second. The most common failure mode is launching six rituals in January and abandoning all of them by March because the workload collapses. One excellent, consistently-run ritual outperforms six half-hearted ones by every measure.
Ask your most engaged members whether they still find it valuable. Rituals have natural life cycles. Make one of three decisions: reinvent it, retire it, or keep running it with a clear reason why. Don't keep running a dead ritual out of sunk-cost loyalty, it signals to members that you're not paying attention.
Start with the simplest possible version: one question, posted by you, with your own answer as the example. Invite three members personally to reply. You don't need critical mass for a ritual to work. You need consistency and a founder who participates visibly.
The seasonal calendar sets the emotional context (Q1 is goal-setting energy, Q4 is reflection energy). Rituals are the repeating mechanical layer that runs regardless of season. The intersection is where the best engagement happens: a seasonal kickoff event that launches a new ritual, a year-end ritual that reflects on the community's progress together.
Evolve them, don't replace them suddenly. A ritual that's been running for two years has members who've built habits around it. If you need to change it, introduce the new version alongside the old one, let members vote on the direction, and make the change gradual. Abrupt retirement of a beloved ritual damages trust more than a poorly-designed new one.
