Communication Fetishism: Stop Over-Investing in Platforms
Jono Bacon coined the term for a reason. Every new platform you add fragments attention, creates maintenance debt, and distracts from the only thing that actually matters: the quality of what your community says to each other.
Three months into building her partner network, a founder I advise showed me her "communication stack." Slack workspace with 14 channels. A Circle community portal. A WhatsApp group for "quick questions." A private Facebook group. A biweekly email digest. A private podcast. And a shared Notion wiki that hadn't been updated since launch week.
She had 18 partners.
Her engagement rate across all channels combined was lower than most single-channel communities half her size. Partners had no idea where to post questions. Important announcements got buried in one channel while half the partners were checking a different one. Three partners had quietly muted every notification and only showed up for the monthly call. Two hadn't logged into Slack in six weeks.
When I asked her why she'd built such an elaborate infrastructure for 18 people, her answer was honest: "I wanted it to feel professional." And that instinct — the desire to signal seriousness through tooling — is exactly the trap Jono Bacon warns about.
He calls it Communication Fetishism: the tendency to over-invest in communication platforms and under-invest in communication content. It's one of the most common and most destructive mistakes in community building. And it's almost always motivated by good intentions.
The Platform Multiplication Problem
More Channels, Less Engagement
Every communication platform you add introduces a tax on your partners' attention. Each new channel requires them to remember where it is, log in, check for updates, and decide whether to respond. For a busy consultant running their own practice, serving clients, and trying to grow revenue, every additional login is friction they didn't ask for.
The math works against you quickly. Imagine a partner's morning routine:
- Check email. There's a digest from the community portal, a direct message notification from Slack, and a newsletter update from the founder. Three items from the same ecosystem, in three different formats, requiring three different actions.
- Open Slack. 14 channels. Most are quiet. Two have unread messages from yesterday. One has a question that should have been posted in the portal. Another has an answer to a question that was asked in the WhatsApp group. Context is fragmented.
- Check WhatsApp. 47 unread messages, most of them emoji reactions and "great point!" responses. The actual useful content is buried three screens back. The partner skims, gives up, closes the app.
- Remember the portal exists. Maybe. If there's a notification. If there isn't, the portal sits unused until someone specifically directs traffic there.
Net result: the partner spent 15 minutes touching four platforms and retained almost nothing useful. Compare that to a single Slack workspace where all conversation happens in three well-organized channels. The same partner opens one app, scans three channels, catches up in five minutes, and actually engages.
Channel proliferation doesn't create more communication. It creates more noise. And noise, over time, teaches partners to stop listening.
"The professional-looking portal that nobody visits is worse than the messy Slack channel where everyone talks. Engagement beats aesthetics. Every time."
Bacon's insight is that founders confuse platform investment with community investment. Building a beautiful portal feels productive. It looks impressive in the partner onboarding deck. It signals that you're "serious." But the community doesn't live in the portal. The community lives in the conversations between partners — and those conversations happen wherever the friction is lowest, regardless of what you built.
The Content Problem Nobody Talks About
Platforms Are Empty Rooms Until Someone Speaks
There's a second dimension to Communication Fetishism that's even more damaging than channel proliferation: the belief that building the platform is the work. It isn't. Building the platform is the easy part. Filling it with valuable content is the actual work — and it never ends.
A Slack workspace with no new messages for three days is a ghost town. A community portal with the same five articles from launch month is a abandoned website. A WhatsApp group where only the founder posts is a monologue disguised as conversation. The platform doesn't create engagement. Content creates engagement. Conversations create engagement. Useful, timely, relevant interactions between partners create engagement.
And here's the uncomfortable truth: most founders spend 80% of their community-building energy on platforms and 20% on content. The ratio should be inverted.
What does valuable community content actually look like?
- A partner posting a specific challenge they're facing with a client — and three other partners responding with approaches they've used in similar situations. That's a conversation no training module could replicate.
- The founder sharing a methodology insight that came from last week's research or a recent client interaction. Not a polished article. A raw observation that invites discussion.
- A cross-referral opportunity posted clearly — "I have a client in financial services who needs data governance expertise. Anyone in the network work in that space?" That's tangible value delivered in 30 seconds.
- A quick win celebration — "Just closed a $40K engagement using the diagnostic as the entry point. Here's how the conversation went." That's social proof and practical learning in one message.
None of this requires a custom portal. All of it can happen in a single Slack channel. The value isn't in the container. It's in what fills it.
If your partners aren't engaging, the answer is almost never "we need a better platform." The answer is almost always "we need better content, better questions, and more reasons to show up."
The Minimum Viable Communication Stack
What You Actually Need for Up to 100 Partners
Bacon's prescription, validated across communities ranging from open-source software projects to professional associations, is deliberately minimal:
Async communication: one platform. Slack or Microsoft Teams. Not both. Three to five channels maximum: #general for community-wide announcements, #wins for celebrating partner success, #referrals for cross-practice opportunities, #methodology for framework discussions and questions, and optionally #off-topic for the informal bonding that makes the professional channels productive. Anything beyond five channels for a community under 100 is fragmentation.
Video: one platform. Zoom or Google Meet. Monthly calls, quarterly reviews, training sessions, and ad-hoc partner meetings all use the same link format. Don't make partners learn two video platforms because your quarterly review feels "more serious" than the monthly call.
Documents: one library. Google Drive, Notion, or a SharePoint site. Playbooks, templates, methodology documents, case studies, and training materials all live in one searchable location. Organize by type, not by date. A partner looking for the pricing playbook shouldn't have to remember when it was published.
Calendar: one cadence. Monthly call on the same day each month. Quarterly review on a predictable schedule. Annual summit date announced a full year in advance. Predictability reduces cognitive load. When partners know the third Tuesday is always the monthly call, attendance becomes automatic rather than deliberate.
That's the entire stack. Four tools, each serving a single purpose, each chosen for the lowest possible friction.
The founder with 18 partners and seven platforms could have achieved higher engagement with Slack, Zoom, Google Drive, and a calendar invite. The remaining three platforms weren't adding value — they were adding friction disguised as professionalism.
When to Invest in Custom Tooling
Three Thresholds That Justify the Build
Custom platforms aren't inherently wrong. They're prematurely wrong. There are genuine thresholds where general-purpose tools break down and purpose-built infrastructure becomes justified:
Threshold 1: 100+ partners. At this scale, Slack channels become unmanageable. Conversations move too fast for asynchronous participation. Regional or specialization-based subgroups need their own spaces. A structured community platform with threaded discussions, searchable archives, and member profiles starts adding more value than it costs.
Threshold 2: Diagnostic data aggregation. When your network has delivered enough assessments that the aggregate data becomes strategically valuable — for benchmarking, for research, for methodology validation — a centralized platform that captures and normalizes that data is worth building. This isn't a communication tool. It's a data asset that requires custom architecture.
Threshold 3: Automated client-partner matching. When you're receiving enough inbound diagnostic completions that manually matching clients to the right partner becomes a bottleneck, automation justifies the investment. A matching algorithm that considers partner specialization, geographic proximity, availability, and client needs is genuinely complex — and genuinely valuable.
Until you've crossed at least one of these thresholds, resist. The urge to build is strong — especially for founders who come from technology backgrounds. Building a portal feels like progress. But progress in community is measured by engagement, not infrastructure.
Communication Fetishism is seductive because it feels like investment. You're building something. You're creating infrastructure. You're being professional. But the partners don't care about your infrastructure. They care about whether the community helps them win clients, solve problems, and grow their practice. A single Slack channel with three useful messages per week does more for retention than a bespoke portal with perfect UX and zero conversation. Build less. Say more. That's the entire playbook.