← Back to Writing

The Invisible Work of Community

The Invisible Work of Community: What If You're Solving the Wrong Community Problem?

A supposedly languishing support forum turned out to be something entirely different: a community of practice.

Early on in my community career, I heard about a once buzzing support community that was languishing.

According to the lore, a handful of members remained and occasionally participated at a much lower activity level than when the community was in its prime.

The assumption about this community was that if I could find people in the company to answer questions and help resolve issues, the community would begin to thrive again.

Intrigued, I wanted to learn more, but I needed to do discovery to understand the past and the current state of the community before I prescribed a solution.

I had many questions about the community’s history, trajectory, and growth. One question was foremost in my mind—if no one was available to answer community members’ questions, why were members still showing up, even in reduced numbers?

Once I started spending time in the community, observing conversations and interactions, and talking to the handful of members who were still there, I found something completely unexpected.

The community was still alive with conversation and activity.

While there was talk around issues and resolution, that was not the main event.

Members were deep diving into products and new features, comparing approaches, sharing notes on implementations, and exchanging practical information. Learning together.

This was not a neglected support community. It had organically morphed into a community of practice.

The lore may have been outdated, but it led me to one of the rarest community finds, a community that endured even after active stewardship stopped.

And members weren’t just keeping it alive. They were creating value for one another and for the company. This was no longer about reviving an under-resourced community—it was about building around the new community of practice that members created.

That meant synthesizing what members told me, my observations about their behavior, and what I knew about building communities, and translating all of it into an experience centered on peer learning, support, and contributions.

User journey mapping and segmented onboarding paths. More channels for conversations. Daily, weekly, and monthly rituals like office hours, AMAs, and listening sessions. Recognition for their contributions on a leaderboard and through shout-outs.

Opportunities for them to lead and to learn, including demo days, workshops, and contests. New ways to connect with peers and leaders in the company.

Now, I just had to sell it.

Next: Now, I Just Had to Sell It.

Building something new, scaling what works, or rethinking what could work better?

Let's talk about the customers you're serving and the outcomes you're working toward.

Let’s Talk