Broadcast or community post? A simple rule for choosing the channel

You have written the message. Now you are hovering, because it could go in two places. Post it in the community feed and only members see it, which feels like wasting a good message. Send it to the whole list and members get it twice, which feels like shouting at people who already agreed with you. So you do both, every time, and six months later your members have quietly stopped opening the feed because everything in it arrived by email first.

Two channels that look similar and behave nothing alike

A broadcast is push. It arrives whether or not the reader was thinking about you, it interrupts, and it is the only channel that reaches somebody who has drifted away. That power is exactly why it degrades with use: every email spends a little of the reader's patience, and you cannot get it back by sending another one.

A community feed is pull. Posts, replies and pinned announcements sit there and wait, and the person has to come. That sounds weaker, and in reach it is. In everything else it is stronger: replies happen, threads carry on for days, members read things that were posted before they joined, and the whole place accumulates rather than evaporating the way an inbox does.

The genuinely difficult bit is that both channels can carry the same message, so the decision never feels forced. Nothing breaks when you get it wrong. The cost is slow and invisible: a feed that becomes a copy of the newsletter stops being worth visiting, and a list that receives member business it cannot act on stops being worth opening. You lose both by trying to be thorough.

The way it usually goes, versus the split that holds

Most creators route by importance: big news goes everywhere, small news goes in the feed. That is the wrong axis. Route by audience instead — who needs to act, and have they already paid — and the decisions become obvious.

The four-second routing test

Run down these in order and stop at the first one that answers. It is deliberately crude, because a rule you follow beats a framework you admire.

1. 1Does this ask somebody to buy, join, book or turn up who has not already? Broadcast. This is the one thing the feed cannot do, because the people you need are not in it.
2. 2Is it only true for members — a session recording, an answer to a member's question, work in progress, a change to how the community runs? Feed. Copying it to email spends the exclusivity you are charging for.
3. 3Is it time-critical for members specifically, like a live session starting on Thursday? Pin it in the feed, and send a short broadcast that points at the feed without repeating the contents.
4. 4Is it a conversation rather than a statement? Feed, every time. Replies belong somewhere they can be read by everyone later, not scattered across your inbox.
5. 5Is it something you want strangers to find in six months? Neither — that is a product page or an article, both of which are statically rendered, indexable and in your sitemap.

• Feed: the recording of last week's call, a half-finished draft you want reactions to, a members-only discount on something you made, an answer to a question three people asked.
• Broadcast: a new product, an open enrolment window, a webinar anyone can attend, a lead magnet, an offer that expires.
• Both, carefully: a live session for members starting soon — pinned in the feed with the detail, one line in the email pointing at it.

A worked example: launch week for a new workshop

You are running a paid workshop that anyone can attend, and your community is £9 a month. The routing is: broadcast to the list announcing the workshop, because most of the people who might come are not members. A feed post the same day, but a different message — not the sales pitch, an explanation of why you are running it and what you are still deciding, which is a conversation only members get. Then a members' perk in the feed, perhaps a seat included or a code they can use, posted and pinned.

That is three messages, two channels, no duplication, and each one is doing something the other cannot. Say 1,200 people are on your list and 180 in the community. The broadcast is trying to convert some fraction of the 1,200 who have never bought. The feed post is protecting the 180 who already did, by making the membership visibly better during a week when everyone else is being sold to. Those figures illustrate the shape of the decision rather than predicting anything about your launch, and per-product analytics will tell you afterwards which route actually carried the sales.

The mistake most people make

The mistake is treating the feed as a distribution channel rather than a place. Distribution is what email does. A community is not another slot in your publishing schedule, it is somewhere people expect to find you behaving slightly differently — less finished, more responsive, willing to answer. The moment the feed becomes a mirror of the newsletter, members correctly conclude that the free version of you is the same as the paid one, and the cancellation is not a failure of the content, it is a failure of the routing. Everything the membership is worth lives in the gap between the two channels.

You are not choosing between two ways of saying the same thing. You are deciding whether a message is an invitation or a conversation, and once you have named which it is, the channel is already chosen. When you genuinely cannot tell, put it in the feed — the worst case is that fewer people see something good, which is a far cheaper mistake than a membership that stops feeling like one.