Latest / Community Marketing with Fexingo: Discord, Slack Groups, and Brand Communities / Why Your Brand Community Needs a Shared Calendar
Transcript
- Lucas: There is a moment every community manager knows — you log in one Tuesday morning and there are forty-seven unread messages and none of them are on the same topic. Three different arguments. Two people asking the same question. One member posting a meme that has nothing to do with anything. Luna: And you just sit there, coffee in hand, wondering where to even start. Lucas: Exactly. That chaos is normal, but it's also a signal. The communities that scale well — that don't burn out their moderators or frustrate their members — tend to have one thing in common: a shared calendar. Not a secret editorial calendar, a public one that the whole community sees. Luna: Before we dive in — and I know this is a marketing show, so this fits — if these conversations about community building have sparked something you've actually used in your own work, a handful of listeners chip in monthly at buy me a coffee dot com slash fexingo, and that's literally what keeps this show ad-free and independent. Lucas: Yeah, and we mean it when we say it's a small group making it possible. We don't run ads, we don't do sponsorships, and that's by design. So if the show's been useful, that link is the whole engine. Luna: Alright, back to the calendar. So what does a shared calendar actually look like in practice? Lucas: Let me give you a concrete example. There's a small indie SaaS company — they make a project management tool for creative teams — and their community has about 150 active members. They were struggling with the same thing: sporadic posts, low engagement, moderator fatigue. So they did something simple. They created a public Google Calendar and shared the link in their welcome channel. Luna: And what went on that calendar? Lucas: Three layers. First, recurring platform-wide events: Monday Motivation thread, Wednesday Workshop where a member shares a workflow, Friday Feedback thread. Second, member-initiated slots: any member could claim a time to do a live demo of their work. Third, behind the scenes moderation blocks — like 'mods reviewing new join requests' every evening at 8 PM. The calendar became the single source of truth. Luna: I love the third layer. Most community managers don't think to broadcast when they're doing invisible work. Lucas: Right. Because when members see that a moderator is 'offline' but actually they're reviewing applications from 7 to 8, they're less likely to feel ignored. The calendar gave the community a rhythm. Within three months, weekly active participants went up by 30 percent. The number of duplicate questions dropped. And the moderators reported feeling less scattered. Luna: But I have to ask — doesn't a calendar make the community feel too structured? Part of the magic of a brand community is spontaneity, right? The random late-night conversation that sparks a new idea. Lucas: That's the pushback I hear every time I talk about this. And I think it's a valid concern. The trick is the calendar shouldn't fill every hour. Leave white space. In that SaaS community, they reserved Wednesday afternoons as 'open water' — no scheduled events, just unstructured hangout. That's when the best serendipity happened. Luna: So the calendar is more about creating a baseline predictability, not erasing spontaneity. Lucas: Exactly. And here's the thing — the members actually start self-organizing around the calendar. They see 'Friday Feedback' and they prep their work in advance. They know when the community manager is available. It reduces anxiety. The community becomes a place you can rely on, not a firehose you have to check constantly. Luna: What about the tool itself? Does it have to be Google Calendar, or are there community-specific platforms? Lucas: Can be anything. Some use Notion with a timeline view. Some use a dedicated Discord channel with scheduled events. The format doesn't matter as long as it's publicly visible and editable by the community manager. The key is that it's not hidden in a doc that nobody reads. Luna: And how do you get people to actually look at it? Lucas: Embed it in the welcome flow. Pin it in a high-traffic channel. Refer to it verbally — 'as you can see on the calendar, Thursday is our member spotlight.' Over time, it becomes a habit. The community I mentioned saw that 60 percent of members checked the calendar at least once a week after two months. Luna: So the return on investment is a more predictable community that's easier to moderate. Seems like a no-brainer. Lucas: It's one of those low-effort, high-impact changes that most communities overlook because they're too busy putting out fires. But a shared calendar doesn't just help the moderators — it helps the members know what to expect. And that predictability builds trust. Luna: I'm actually going to try this in my own community. Start with just one recurring event per week and see how it goes. Lucas: Start small. One event, one pinned post, and a public link. See if it reduces the entropy. I suspect you'll never go back.