# Discourse Upcoming Changes opt-in before community rollout

> Use the Upcoming Changes page as a feature gate so new community behavior can be tested, communicated, and staged before everyone feels the change at once.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/discourse-upcoming-changes-opt-in-before-community-rollout/
- Source: [meta.discourse.org](https://meta.discourse.org/t/introducing-upcoming-changes-a-system-to-manage-new-features-and-changes-to-existing-functionality-in-your-community/392894/)
- GrowthDex source hub: [Discourse Meta: Introducing Upcoming Changes](/sources/discourse-meta-introducing-upcoming-changes-meta-discourse-org/)
- Last checked: 2026-05-30
- Rarity: rare
- Budget: free
- Channels: Community, Operations, Brand
- Stages: change management, community trust, feature rollout, operator communication


## Why this can grow

Communities often break trust not because the new feature is bad, but because the operator changes behavior without a safe introduction path. Discourse's Upcoming Changes system gives admins a staging lane for product changes that are still alpha, beta, or rolling out gradually. That means the team can trial a new moderation or category workflow with the right audience first, prepare staff docs, and avoid surprising the whole community with an untested operating change.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where discourse upcoming changes opt-in before community rollout can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Community and Operations channel.
3. Use the evidence from meta.discourse.org to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Discourse introduced an Upcoming Changes config page in February 2026 so admins can review incoming changes, see who is affected, and choose how features in states like Alpha are enabled in their own community.

## Adjacent tactics in the same lane

- [Group flair for visible host identity](/growth-ideas/group-flair-for-visible-host-identity/) - 2 shared channels, 1 shared stage
- [GitHub profile README as operator proof surface](/growth-ideas/github-profile-readme-as-operator-proof-surface/) - 2 shared channels
- [GitHub default community health files across repos](/growth-ideas/github-default-community-health-files-across-repos/) - 2 shared channels
- [Discourse category approval rules by trust group](/growth-ideas/discourse-category-approval-rules-by-trust-group/) - 2 shared channels

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The support queue should know what kind of thread it is](/blog/the-support-queue-should-know-what-kind-of-thread-it-is/) - support-led growth, community-led growth, brand trust

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.