# Request trend view separating weekly demand from spikes

> Track which requests recur every week versus which ones spike briefly so product teams stop treating all volume as the same kind of demand.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/request-trend-view-separating-weekly-demand-from-spikes/
- Source: [productlane.com](https://productlane.com/changelog)
- GrowthDex source hub: [Productlane Changelog](/sources/productlane-changelog-productlane-com/)
- Last checked: 2026-05-26
- Rarity: rare
- Budget: low
- Channels: Product, Analytics, Customer Success
- Stages: prioritization, signal quality, roadmap, support-led growth


## Why this can grow

A request count is blunt. Some asks come up every week because they sit in the product's main path. Others explode for two days because a launch, outage, or one loud account pulled attention onto them. A trend view helps the team separate durable demand from temporary heat, which makes roadmap conversations less emotional and follow-up with customers more honest.

## 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 request trend view separating weekly demand from spikes can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Product and Analytics channel.
3. Use the evidence from productlane.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

Productlane added customer request reporting over time so teams can compare requests that keep returning every week with issues that only spiked recently.

## Adjacent tactics in the same lane

- [Customer-adjustable request importance with added context](/growth-ideas/customer-adjustable-request-importance-with-context/) - same source, 2 shared channels, 2 shared stages
- [Account-wide request rollup on the public roadmap](/growth-ideas/account-wide-request-rollup-on-public-roadmap/) - same source, 2 shared channels, 2 shared stages
- [Context prompt immediately after a feedback upvote](/growth-ideas/context-prompt-immediately-after-feedback-upvote/) - same source, 1 shared channel, 2 shared stages
- [Request page with the prior mail thread visible](/growth-ideas/request-page-with-prior-mail-thread-visible/) - same source, 2 shared channels, 1 shared stage

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The request count is usually the wrong number](/blog/the-request-count-is-usually-the-wrong-number/) - support-led growth, product signal, brand trust

## Advisory

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