Latest / Community Marketing with Fexingo: Discord, Slack Groups, and Brand Communities / How a Brand Community Co-Wrote Its Own Handbook
Transcript
- Lucas: So there's this software company, a mid-sized project management tool with about forty thousand users, and last quarter they did something I don't think I've seen done well before: they let their community write the official user handbook. Luna: You mean like, the actual help docs that everyone sees? Lucas: Exactly. Not a wiki, not a forum thread. The actual onboarding guide that new users get. And it wasn't a stunt—they spent eight weeks on it, had clear guardrails, and the result was something their own support team says is better than anything they'd written in-house. Luna: That's a bold claim. What made them try it in the first place? Lucas: Their support tickets were drowning them. About sixty percent of questions were the same ten 'how do I set up a project' type queries. Their docs were technically accurate but written in that dry, corporate voice that nobody reads past the first paragraph. Luna: So they figured the people who actually use the tool daily might explain it better than the product team. Lucas: Right. And they had a vibrant community already—a few thousand active members in their Slack. So they put out a call: 'Help us write the new user handbook. We'll pay you in swag and credit, and we'll be transparent about the process.' Luna: How many people actually signed up? Lucas: About two hundred volunteered. They whittled it down to a core team of fifteen, mostly power users who had been around for years and had seen every feature evolve. Luna: Fifteen people co-writing a handbook sounds like a recipe for chaos. How did they keep it from turning into a mess? Lucas: They had a structure. Each chapter had a 'lead' from the community, but they also paired every lead with a staff editor from the documentation team. The editor's job wasn't to rewrite—it was to fact-check and keep the tone consistent. Luna: So the community owned the words, but the company owned the accuracy. That's a smart split. Lucas: And they had weekly check-ins where the whole group reviewed one chapter together. That's where the real magic happened, but also where the friction showed up. Luna: What kind of friction? Lucas: One chapter was about project templates, and the community lead insisted on including a workaround for a limitation that the product team had deliberately built. The lead argued that real users needed that workaround every day, and the company wanted to hide it so it wouldn't encourage bad practices. Luna: That's a genuine conflict. Who won? Lucas: They compromised. The handbook included the workaround, but with a clear note explaining why it wasn't officially supported and what the future roadmap was. That transparency actually built trust with the community. Luna: It also probably made the handbook more genuinely useful. People hate when docs gloss over the messy reality. Lucas: Exactly. And this is where I want to pause, because we're able to have this conversation without any sponsor interruptions, and that's something we're pretty proud of. We deliberately don't run ads on these shows. If you value that, and you want to support the choice, the link is buy me a coffee dot com slash fexingo. It's a small way to keep this going, and we appreciate anyone who does. Luna: Yeah, it's a nice model. Every little bit genuinely helps us stay independent. Lucas: So back to the handbook. After eight weeks, they had a draft that covered everything from basic setup to advanced integrations. They published it as version one point zero, clearly marked as community-authored, with a note that it would be a living document. Luna: And the impact on support tickets? Lucas: Within the first month, basic support queries dropped by forty percent. The kind of tickets that used to be 'how do I create a task' basically vanished. The community-authored explanations were just clearer. Luna: That's a huge win. Did they see any other unexpected benefits? Lucas: A big one: feature adoption. The handbook included real-world workflows from power users, not just feature lists. So users who read it started using things like custom fields and automations at a much higher rate. The company measured a fifteen percent increase in feature adoption among new users who read the handbook. Luna: So the community didn't just write documentation—they essentially wrote a better onboarding experience. Lucas: Right. But it wasn't all smooth sailing. There was a moment in week five where the whole project nearly fell apart over a disagreement about tone. Some community members wanted to use emojis and casual language, while others wanted it to feel more professional. Luna: I can see that being a real flashpoint. How did they resolve it? Lucas: They ran a quick vote among the whole community, not just the writing team. The result was a split, so they settled on a middle ground: professional for the core instructional sections, but allowed casual 'tips from the community' boxes throughout. Those boxes have become the most-liked parts of the handbook. Luna: That's a smart compromise. It kept the integrity of the manual while letting the community's personality shine through. Lucas: And it created a sense of ownership. The people who contributed felt a real stake in the product's success. Several of them have since become volunteer moderators or beta testers. The community became a pipeline for deeper engagement. Luna: So what would you say is the one lesson other brands should take away from this? Lucas: That your most experienced users often understand your product better than you do—not in terms of code, but in terms of real-world usage. If you can give them a structured way to share that knowledge, and you're willing to hand over some control, you end up with something more valuable than any internal team could produce alone. Luna: And the handbook is still being updated by the community, right? Lucas: Yes. They set up a monthly review where community leads propose changes, and the staff editor approves them. It's become a permanent part of their ecosystem. The last time I checked, the handbook has become the most-linked resource in their entire knowledge base. Luna: It's a great example of turning your community from a audience into a co-creator. I wonder how many other companies could pull this off. Lucas: It takes a willingness to share power, and a community that's engaged enough to care. But the payoff can be real, both in support savings and in community loyalty. Luna: I'm already thinking about how I'd pitch this to a client. Maybe we should do a follow-up on how to actually structure that kind of project. Lucas: That's a good idea. For now, I think the takeaway is that your community is a resource you're probably underusing. Sometimes the best content is the content they create themselves.