Growth idea action plan
Topic voting category for public feature requests
Keep feature requests in a dedicated voting category so demand gathers on one public thread instead of splintering across duplicate asks.
Why this can grow a startup
A public forum gets messy fast when feature requests arrive as plain conversation. The same idea gets posted three times, support cannot point prospects to one live record, and product loses the compounding signal of visible demand. Discourse Topic Voting gives a cleaner lane by letting specific categories run on votes. That makes each request page work harder. It becomes a demand counter, a place for clarifications, and a public artifact sales or success can reuse. The gain is not just prioritization. It is a more legible product story in public.
Key metric to watch
Topic Voting gives users the ability to vote on topics in a specified category.
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
- Define one narrow startup segment where topic voting category for public feature requests can create a measurable lift.
- Turn the tactic into one offer, page, campaign, or workflow for the Community and Product channel.
- Use the evidence from meta.discourse.org to set the first version of the message, format, and audience.
- Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
- Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.
Source-backed example
Discourse's official Topic Voting plugin lets admins enable voting on topics inside specified categories.
Source: Discourse Meta: Discourse Topic Voting (meta.discourse.org)
GrowthDex source hub: Discourse Meta: Discourse Topic Voting
Last checked: 2026-05-29
Adjacent tactics in the same lane
If this page is close to your problem, these tactic pages usually belong in the same working set.
- Canny Slack notifications before feedback gets buried 3 shared channels
- Prospect vote required before feature promise 2 shared channels · 1 shared stage
- Roadmap stage notifications for feature requesters 2 shared channels · 1 shared stage
- Founder-calendar pricing page for first sales 2 shared channels
Related GrowthDex essays
- The forum should keep the answer after the chat scrolls away community-led growth, support deflection, forum seo
Read GrowthDex essays
The Blog turns real growth tactics into plain-English case studies by niche, channel, and buying situation.
Why this is worth your time
GrowthDex starts with tactics that founders, marketers, and product teams have actually tried. Each essay turns the evidence into a practical move you can test without pretending one case study is a guarantee.
Ian Goh has helped grow consumer platforms across Southeast Asia, India, and MENA. His work includes scaling Tiki to 100M+ users, doubling BIGO's MENA revenue in 7 months, and increasing OYO's direct booking share across 6 Southeast Asian markets.
- Helped scale Tiki to 100M+ users.
- Doubled BIGO's MENA revenue in 7 months.
- Raised OYO's direct booking share by 50% across 6 Southeast Asian markets.
Want help turning this into a growth system?
If you want someone to pressure-test this against your real market, Ian works with founders on growth, market entry, and operator-led distribution.
Work with Ian on growth advisory