Growth idea action plan
New feature requests default to public In Review
Drop every new request into a visible In Review state so customers can see that the idea entered the system before it earns a roadmap slot.
Why this can grow a startup
Most public roadmaps fail because they only show the polished middle. That makes customers feel like ideas vanish into a private room until the company is ready to announce something. Buffer puts all new suggestions into a visible In Review bucket first. That small move keeps the feedback loop legible, invites other users to add votes or nuance, and buys the team time to triage without going silent.
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 new feature requests default to public in review can create a measurable lift.
- Turn the tactic into one offer, page, campaign, or workflow for the Community and Product Roadmap channel.
- Use the evidence from buffer.com 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
Buffer marks new suggestions as In Review by default so other users can upvote them while the team decides whether to move them onto the roadmap.
Source: Buffer (buffer.com)
GrowthDex source hub: Buffer
Last checked: 2026-05-28
Adjacent tactics in the same lane
If this page is close to your problem, these tactic pages usually belong in the same working set.
- All feature requests visible before roadmap prioritization same source · 3 shared channels · 3 shared stages
- Signed-in feedback board links requests to customer identity same source · 1 shared channel · 3 shared stages
- Feature request stage emails for submitters and followers same source · 1 shared channel · 2 shared stages
- Open beta toggle inside product navigation same source · 1 shared channel · 2 shared stages
Related GrowthDex essays
- The feedback loop breaks when the middle stays hidden product-led growth, community-led growth, brand trust
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