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.
Company 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 and metric
Source: Buffer · Browse Buffer tactics
Buffer uses a default In Review state as the first visible status for every new public suggestion.
Source discovered: May 28, 2026
When to use it
Use this when Community, Product Roadmap, Customer Feedback is relevant to feedback, community-led growth, product strategy and you can run a bounded test with a free 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.
Founder checklist
- Read Buffer and identify what is directly supported.
- Choose one channel context: Community, Product Roadmap, Customer Feedback.
- Define the test around Buffer uses a default In Review state as the first visible status for every new public suggestion..
- Set an owner, evidence window, and stop condition before launch.
Explore the context
Apply this with an operator
Build creator and community systems around real incentives, trust, and repeat participation.