# Customer Advocacy design-brief pass before build

> Let the frontline customer team review the design brief early so support pain and workflow context shape the feature before implementation hardens.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/customer-advocacy-design-brief-pass-before-build/
- Source: [buffer.com](https://buffer.com/resources/support-team-product-launches/)
- GrowthDex source hub: [Buffer Open Blog](/sources/buffer-open-blog-buffer-com/)
- Last checked: 2026-05-28
- Rarity: rare
- Budget: free
- Channels: Support, Product, User Research
- Stages: pre-launch, product discovery, voice of customer, support-led growth
- Key metric: Buffer brings Customer Advocacy into the design-brief stage before engineering and design move too far ahead.

## Why this can grow

Product managers and designers understand the intended workflow. Customer-facing teams understand the recurring confusion, edge cases, and language customers already use. Pulling those people into the brief before build turns support knowledge into product input instead of post-launch cleanup. It usually catches missing context earlier and makes the eventual launch easier to explain.

## 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 customer advocacy design-brief pass before build can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Support 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 said its Customer Advocacy team reviews the product manager's early design brief and offers suggestions based on what its most vocal users are trying to do.

## Adjacent tactics in the same lane

- [Staged rollout milestones in shared launch channel](/growth-ideas/staged-rollout-milestones-in-shared-launch-channel/) - same source, 2 shared channels, 1 shared stage
- [Community wireframe email with inline comments](/growth-ideas/community-wireframe-email-with-inline-comments/) - same source, 1 shared channel, 2 shared stages
- [Multi-source feedback firehose behind the public roadmap](/growth-ideas/multi-source-feedback-firehose-behind-public-roadmap/) - same source, 2 shared channels, 1 shared stage
- [Frontline support prototype pass before public rollout](/growth-ideas/frontline-support-prototype-pass-before-public-rollout/) - same source, 2 shared channels

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The public roadmap only works if the team keeps answering](/blog/the-public-roadmap-only-works-if-the-team-keeps-answering/) - community-led growth, brand trust, product strategy

## Advisory

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