# Snoozed triage that returns on new activity

> Snooze issues that need more context instead of forcing a fake yes or no, and let them come back when the timer or the next signal arrives.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/snoozed-triage-returns-on-new-activity/
- Source: [linear.app](https://linear.app/docs/triage)
- GrowthDex source hub: [Linear Docs](/sources/linear-docs-linear-app/)
- Last checked: 2026-05-28
- Rarity: uncommon
- Budget: free
- Channels: Support, Product, Operations
- Stages: triage, feedback loop, queue hygiene, support-led growth


## Why this can grow

Some issues are real but not ready. If the team must accept or reject them immediately, the queue fills with half-understood work or polite cancellations that come back later as duplicates. Snoozing creates a middle state. The issue stays out of the way until the chosen review time or fresh activity makes it worth another look. That keeps triage honest without turning it into a dumping ground.

## 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 snoozed triage that returns on new activity 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 linear.app 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

Linear's Triage docs say snoozed issues return at a time of your choosing or when there is new activity on the issue, whichever comes first.

## Adjacent tactics in the same lane

- [Triage responsibility rotation linked to on-call schedules](/growth-ideas/triage-responsibility-rotation-linked-to-on-call-schedules/) - same source, 3 shared channels, 2 shared stages
- [Priority required before triage exit](/growth-ideas/priority-required-before-triage-exit/) - same source, 3 shared channels, 1 shared stage
- [Dedicated feedback team for customer request intake](/growth-ideas/dedicated-feedback-team-for-customer-request-intake/) - same source, 2 shared channels, 2 shared stages
- [Shared Slack channel linked to the customer record](/growth-ideas/shared-slack-channel-linked-to-the-customer-record/) - 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 queue gets clearer when done means shipped](/blog/the-queue-gets-clearer-when-done-means-shipped/) - support-led growth, product operations, brand trust

## Advisory

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