Vote-to-watch prompt after idea upvote
Prompt members to watch an idea after they vote so feature requests keep a live audience instead of becoming silent scoreboards.
Why this can grow a startup
A raw vote count tells you what the community liked once. It does not guarantee anyone comes back when the discussion sharpens or a workaround appears. Discourse's newer topic voting flow fixes that gap by keeping the vote button reachable while scrolling, asking members whether they want to watch the idea after voting, and letting Hot sorting account for recent voting activity. That turns the ideas area from a static leaderboard into a queue where current momentum is easier to see and the right people stay attached to the thread.
Source-backed example
Discourse announced that ideas topics now keep the voting button accessible in the topic header while scrolling, prompt members to watch the topic after voting, and factor vote recency into Hot sorting.
Source-reported evidence
Source: Discourse Meta: Improvements to Topic Voting
After a vote, members can opt into Watching the idea topic, and Hot sorting now accounts for vote recency instead of only total votes.
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, Lifecycle Messaging is relevant to request follow-through, community engagement, roadmap signal quality 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: Improvements to Topic Voting as context—not as a promised result.
- Record a baseline for: Target users from this channel who complete the intended first 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.