# Feature-request survey routed into shared Slack triage

> Route every post-launch feature request into one shared channel so product can spot demand clusters before the roadmap drifts.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/feature-request-survey-routed-into-shared-slack-triage/
- Source: [buffer.com](https://buffer.com/resources/lessons-launching-new-product/)
- GrowthDex source hub: [Buffer](/sources/buffer-buffer-com/)
- Last checked: 2026-05-28
- Rarity: uncommon
- Budget: free
- Channels: Feedback, Product, Slack
- Stages: post-launch, roadmap, voice of customer, feedback ops
- Key metric: Buffer said roughly 10 new feature requests came through the shared channel on most days.

## Why this can grow

A launch usually produces too many opinions to read one by one in isolation. A single intake path turns scattered asks into a visible queue that product, marketing, and support can read together. That makes repeated pain easier to notice and keeps the roadmap tied to live usage instead of pre-launch guesses.

## 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 feature-request survey routed into shared slack triage can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Feedback and Product channel.
3. Use the evidence from buffer.com 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

Buffer sent feature requests through a Typeform survey into its internal #feature-requests Slack channel, where the product team grouped requests into categories to look for trends after launching Start Page.

## Adjacent tactics in the same lane

- [Request-cluster roadmap after MVP launch](/growth-ideas/request-cluster-roadmap-after-mvp-launch/) - same source, 2 shared channels, 2 shared stages
- [Missing metric priority from repeated user asks](/growth-ideas/missing-metric-priority-from-repeated-user-asks/) - same source, 1 shared channel, 1 shared stage
- [Recurring product review for in-app feedback](/growth-ideas/recurring-product-review-for-in-app-feedback/) - 2 shared channels, 3 shared stages
- [Adjacent-product onboarding email loop](/growth-ideas/adjacent-product-onboarding-email-loop/) - same source, 1 shared channel

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The launch should keep teaching you after launch day](/blog/the-launch-should-keep-teaching-you-after-launch-day/) - product-led growth, launches, support

## Advisory

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