# 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.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/vote-to-watch-prompt-after-idea-upvote/
- Source: [meta.discourse.org](https://meta.discourse.org/t/improvements-to-topic-voting-voting-access-notification-prompts-and-hot-sorting/401156)
- GrowthDex source hub: [Discourse Meta: Improvements to Topic Voting](/sources/discourse-meta-improvements-to-topic-voting-meta-discourse-org/)
- Last checked: 2026-05-30
- Rarity: rare
- Budget: medium
- Channels: Community, Product Feedback, Lifecycle Messaging
- Stages: request follow-through, community engagement, roadmap signal quality, feedback loops


## Why this can grow

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.

## 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 vote-to-watch prompt after idea upvote can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Community and Product Feedback 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 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.

## Adjacent tactics in the same lane

- [Events category as recurring programming home](/growth-ideas/events-category-as-recurring-programming-home/) - 2 shared channels, 1 shared stage
- [Ideas category type with topic voting defaults](/growth-ideas/ideas-category-type-with-topic-voting-defaults/) - 2 shared channels
- [GitHub discussion thread to issue with label carryover](/growth-ideas/github-discussion-thread-to-issue-with-label-carryover/) - 2 shared channels
- [Discourse solved tags on mixed discussion categories](/growth-ideas/discourse-solved-tags-on-mixed-discussion-categories/) - 2 shared channels

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The forum should route the newcomer before they post](/blog/the-forum-should-route-the-newcomer-before-they-post/) - community-led growth, support-led growth, product feedback

## Advisory

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