On Monday (link is in the comments), I wrote about the outcomes of dismantling community teams and redistributing their responsibilities.
Today’s post considers what receiving those responsibilities often looks like for the recipient teams.
Marketing might inherit an event series without understanding its value to attendees, why it worked, or how changes to it might affect them and their attitudes toward the company.
Customer Success might find themselves with additional engagement responsibilities and may not have the expertise to recognize behaviors that signal damaged trust.
These are not small additions to someone’s job description.
They’re substantial responsibilities being transferred to those who may already be stretched thin, without the training, resources, or institutional knowledge to manage them.
To quote Taylor Swift, “you’re on your own, kid.”
When employees lack the capacity to sustain those relationships, the consequences can extend beyond their workloads.
That can mean competing priorities, reduced capacity, burnout and/or turnover. It’s unlikely that these costs will appear in the same budget that shows savings, but not early on.
There’s also revenue leakage.
A missed renewal. An expansion opportunity that goes unnoticed. An advocate who stops advocating.
The savings from eliminating a community team are visible. They’re reflected in headcount and budgets.
The resulting costs and potential revenue leakage may be harder to identify, especially when consequences surface in different departments long after the original decision.
A retention problem becomes Customer Success’s problem. A missed expansion opportunity becomes Sales’ problem. Declining advocacy becomes Marketing’s problem.
I truly wonder whether decision makers understand that those outcomes are the result of their decision to dismantle their community?
I’m not saying that every organization needs a community.
I’m asking organizations to consider the consequences of eliminating community capabilities because dismantling them sends the work back to the very departments they were designed to help.
Furthermore, redistributing activities does not default to preserving the relationships that connected them or properly equipping those expected to take them over to manage them.
The irony of all of this? Community helped solve many of these problems in the first place.
Now, we’re in a situation—dismantle the solutions, recreate the problems.
It’s an organizational ouroboros. The cost-cutting strategy consumes the cost savings.
Does this resonate with your experience? Share your thoughts in the comments.