# How do you decide whether a feature update deserves a full launch versus a quiet release?
> A rule for when a feature earns a full launch and when release notes will do, with a spoken example and how to handle a product manager who disagrees.

Source: https://mokk.ai/pmm-questions/gtm-strategy/full-launch-or-quiet-release (updated 2026-09-22)
Markdown: https://mokk.ai/pmm-questions/gtm-strategy/full-launch-or-quiet-release.md

Decide by who the change affects and what it changes for them. A feature that alters what someone would pay for, opens a new audience, or closes a gap competitors use against you earns a launch. A refinement for existing users ships quietly with release notes and in-product messages. Write the tiers down in advance, and watch adoption so a quiet release that takes off can get a louder second moment.

## What the launch-or-quiet decision is about

Every launch spends something scarce, from audience attention to sales training time. A company that launches everything teaches its users to ignore announcements.

So the question is about judgment under pressure. Can you say which updates deserve that spend, and can you hold the line when a product manager wants a splash for a small feature? Answers score well when they give a rule someone else could apply with you out of the room. Answers that describe a feeling, such as "it depends how big it is," usually get a follow-up that exposes them.

## Three tests that decide the launch tier

1. **Does it change what someone would pay for?** New buyers, a new plan, or a fresh reason to upgrade points toward a launch.
2. **Does it change the daily habit of many existing users?** A redesign of a core screen affects everyone and needs explaining, even if it wins no new customers.
3. **Does it change the story against alternatives?** Closing a gap that competitors or reviewers keep citing is worth saying out loud.

Two or three yeses usually mean a full launch. One yes means a middle tier, such as an email, a blog post, and a short note to sales. No yeses means release notes and an in-product message for the people it affects. The [tiered platform launch question](https://mokk.ai/pmm-questions/gtm-strategy/tiered-platform-launch) goes further into what each tier contains.

## Worked example from a budgeting app

**Strong answer (invented example)** "I'd run each update through three questions. Would it change what someone pays for? Does it change what lots of current users do every day? And does it change how we compare with the apps people consider alongside us? Here are two updates from a budgeting app. The first is CSV export. It's useful, a few hundred people asked for it in support, and nobody picks a budgeting app because of it. That gets a line in the release notes and a reply to every support ticket that asked for it. The second is shared budgets for couples. That opens a new audience, it gives the premium plan a clear reason to exist, and reviewers keep pointing out that a rival app has it and we don't. That's a full launch with new onboarding, an email campaign, fresh app store screenshots, and outreach to personal finance writers. I'd also write the tiers down before anyone asks, so when a product manager wants a splash for export, we argue about the rule instead of their feature."

## When a product manager wants a bigger launch than the rule allows

Treat the request as information. The product manager may know something you don't, such as a large customer waiting for the feature.

Ask what outcome they want from the launch. If the outcome is recognition for the team, an internal announcement and a customer note from the product lead can deliver it at a fraction of the cost. If the outcome is new revenue, run the three tests together and see whether the feature passes. Then offer an upgrade path. A quiet release with an adoption threshold for the first month can earn a louder second moment later, with real usage numbers as the story. That second moment often lands better than the first launch would have.

## The trade-offs to say out loud when tiering launches

- **Frequency versus attention.** More launches keep the product looking busy, but each one draws less notice. Say roughly how many top-tier moments a year your audience can absorb.
- **Bundling versus shipping.** Holding three medium features for one release makes a bigger story. It also delays value for the users who wanted the first one.

## Where launch-tiering answers go wrong

**Where it goes wrong (invented example)** "It depends on the size of the feature and the engineering effort behind it. Features that took a quarter to build get a full launch with a campaign, and smaller ones get release notes."

This sounds sensible, and plenty of experienced PMMs give it. It loses points because engineering effort measures the company's investment, and the tier should follow the customer's gain. A six-month infrastructure rebuild may deserve nothing louder than a changelog entry. A two-week integration can open a segment. Replace size with who is affected and what changes for them.

The other common miss is a rule with no way to promote a quiet release. Without one, the rule sounds brittle.

## Follow-ups on launch tiers

Pushback to expect on launch tiers
| Pushback | The concern behind it | How to answer |
| --- | --- | --- |
| How many full launches a year is too many? | Whether you think about audience fatigue | Give a range tied to the audience, for example two to four, and roll the rest into bundled moments. |
| A big customer asked for this small feature. | Account awareness | Tell that customer directly. A personal note from their account manager does more than a public post. |
| What if a quiet release takes off? | Whether the rule adapts | Set a threshold in advance and promote it with the adoption numbers as the story. |
| Who else gets a vote on the tier? | Stakeholder awareness | Product, sales, and support leads review it, and marketing makes the call using the written rule. |

## More questions in this category

- [Your most complex launch](https://mokk.ai/pmm-questions/gtm-strategy/most-complex-launch)
- [Building a launch brief](https://mokk.ai/pmm-questions/gtm-strategy/build-a-launch-brief)
- [Launch metrics and timeframes](https://mokk.ai/pmm-questions/gtm-strategy/launch-success-metrics-timeframes)
- [Adjusting a launch mid-execution](https://mokk.ai/pmm-questions/gtm-strategy/adjust-launch-strategy-mid-execution)
- [All go-to-market strategy questions](https://mokk.ai/pmm-questions/gtm-strategy)

## Frequently asked questions

**Can one feature get different tiers in different markets?** Yes. A feature that is table stakes in one market can be news in another, such as a local payment method where rivals lack it. Tier by market when the audiences differ.

**Is a quiet release ever the wrong call for a small feature?** Yes, when the small feature removes a known objection. If sales keeps losing deals over a missing export, that export deserves a note to reps and a line in the pitch, even if the public announcement stays quiet.

## Practice

**Answer it out loud.** A Mokk session asks this question, follows up on your answer, and scores it on five competencies.