← Back to Writing

Community & Organizational Change

Don't Call It a Community

Community teams may disappear while the work remains. What happens to relationships, reciprocity, and institutional knowledge?

(With sincere apologies to LL Cool J. IYKYK.)

Companies want community outcomes: advocacy, engagement, loyalty, retention, …

What I’m seeing of late is that companies want that without community.

What this looks like IRL is dismantling the function and redistributing it. Events and Advocacy go to Marketing. Learning to Customer Success. Feedback to Product. And so on.

Redistributing the work is not necessarily a bad thing. Losing the expertise that knows how to connect it may be.

Community as a discipline is disappearing. The work isn’t.

Companies want the benefits of relationships without doing the work, expecting customers to review and recommend them, contribute content, advocate, and more.

What do customers get in return? 😔

I’ve written about the current state of engagement and its many forms: the impact of broken promises and how to repair it, how the end of an event can be a beginning, and why engagement is a practice, not a campaign. They’re all connected.

I’m not here to defend community as a profession.

I’m interested in helping organizations learn to build relationships, practice reciprocity, and follow through on their commitments within a community team and across the organization.

I’m going to keep writing about it, not because I think community needs a comeback—because I think we can build something better.

What do you think would change if organizations treated relationship-building as a capability everyone needs to develop and actively use in their daily work?

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