# Signed-in feedback board links requests to customer identity

> Tie the public request board to product logins so the team can see who asked for what without a manual lookup pass.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/signed-in-feedback-board-links-requests-to-customer-identity/
- Source: [buffer.com](https://buffer.com/resources/transparent-product-roadmap-v2/)
- GrowthDex source hub: [Buffer](/sources/buffer-buffer-com/)
- Last checked: 2026-05-28
- Rarity: rare
- Budget: free
- Channels: Product, Community, Lifecycle
- Stages: feedback, segmentation, product strategy, community-led growth


## Why this can grow

A request only becomes strategic when the team can connect it to an actual customer, plan, or workflow. Buffer called out that its older intake flow made it hard to identify who a request came from. Using the product login on the feedback board fixes that, which gives product, support, and sales better context when deciding whether an idea reflects a valuable segment or just a loud edge case.

## 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 signed-in feedback board links requests to customer identity can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Product and Community 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 says its suggestions hub works with Buffer login credentials so requests and votes stay tied to real customer accounts.

## Adjacent tactics in the same lane

- [Open beta toggle inside product navigation](/growth-ideas/open-beta-toggle-inside-product-navigation/) - same source, 2 shared channels, 2 shared stages
- [All feature requests visible before roadmap prioritization](/growth-ideas/all-feature-requests-visible-before-roadmap-prioritization/) - same source, 1 shared channel, 3 shared stages
- [New feature requests default to public In Review](/growth-ideas/new-feature-requests-default-to-public-in-review/) - same source, 1 shared channel, 3 shared stages
- [Roadmap stage notifications for feature requesters](/growth-ideas/roadmap-stage-notifications-for-feature-requesters/) - same source, 3 shared channels

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The feedback loop breaks when the middle stays hidden](/blog/the-feedback-loop-breaks-when-the-middle-stays-hidden/) - product-led growth, community-led growth, brand trust

## Advisory

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