Ideas category type with topic voting defaults
Create a dedicated ideas category that turns feature requests into a ranked backlog instead of a flat complaint list.
Why this can grow a startup
A forum gets messy when support questions, product ideas, and general discussion all fight for the same surface. Discourse's Ideas category type gives operators a cleaner fork in the road. It automatically turns on topic voting, exposes the useful settings in one place, and treats feature requests like items that can accumulate demand over time. That helps the community signal which asks keep getting real support instead of rewarding whichever request was posted first or argued the loudest.
Source-backed example
Discourse says the Ideas category type preconfigures topic voting, surfaces the most useful idea settings during category creation, and reflects how they have seen this category style work best in their own and other communities.
Source-reported evidence
Source: Discourse Meta: Easily create Ideas categories using the Topic Voting plugin
Discourse notes Topic Voting on hosted plans is available on Business or higher tiers and adds a Limit member votes setting during Ideas category setup.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
Source discovered: May 30, 2026
When to use it
Use this when Community, Product Feedback, Support is relevant to feedback routing, community ops, roadmap intake and you can run a bounded test with a medium budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Community and Product Feedback, using evidence from Discourse Meta: Easily create Ideas categories using the Topic Voting plugin as context—not as a promised result.
- Record a baseline for: Users who resolve the issue and complete the next useful action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Build creator and community systems around real incentives, trust, and repeat participation.