Almost every portfolio has one: a product category that's been around for years, sometimes decades. Nobody questions it. Nobody gets excited about it. Revenue is stable or gradually declining, the marketing budget goes elsewhere, and internally, the category is considered “established.” That's exactly the problem.
A mature category rarely dies because the product is bad. It dies because nobody asks what customers actually need it for today. The assumptions it was originally built on may be ten or twenty years old. The market has moved on since then. The product hasn't.
Four phases instead of a feature list
The obvious reaction is to add another feature and hope revenue recovers on its own. That rarely works because the underlying problem usually isn't technical. It's commercial: The category no longer speaks to today's market. A structured relaunch therefore follows four phases.
Discovery
Structured, segmented customer research instead of internal assumptions. Who actually uses the category today, and what do they use it for?
Synthesis & business case
Raw customer statements are consolidated into patterns and paired with a commercial assessment before any investment is made.
Requirements & prioritization
Patterns are translated into traceable requirements, prioritized by effort and impact, not internal preference.
GTM relaunch
Positioning, language, and sales collateral are updated, not just the product itself.
Discovery: Segment instead of generalize
The most common mistake in Phase 1 is running one generic customer survey. A mature category typically serves several very different segments, each with its own language and its own problems to solve.
An interview guide that's identical for all four segments ultimately produces little more than the lowest common denominator. A segmented guide with a shared core and industry-specific follow-up questions, on the other hand, produces insights that can actually be translated into differentiated offerings.
From insight to business case
Not every interesting customer statement justifies an investment. That's why there needs to be a step between Discovery and implementation that often gets skipped in practice: synthesis. Recurring patterns are grouped, weighted by frequency and intensity, and only then translated into a business case that weighs effort against expected impact.
This step protects against two common mistakes at once: a relaunch driven by the loudest voice rather than the most representative one, and a relaunch that never happens because the company is too afraid of making the wrong decision.
Requirements with traceability
Synthesis produces requirements, not opinions. Every requirement should be traceable back to the original customer statement. Otherwise, the very thing the process was designed to prevent quietly creeps back in: internal assumptions replacing market reality.
How to trace customer statements all the way through to final requirements, including MoSCoW prioritization and a practical example, is covered in a separate article: From customer statement to requirement.
A relaunch is a marketing job, not just an engineering job
Even the most compelling new product feature will go nowhere if the positioning, language, and sales collateral remain unchanged. A real relaunch updates both at the same time: the product for today's market and the way the company talks about it. Update only one, and the category remains just as quiet as before, only now with an additional feature nobody knows about.
A mature product category rarely needs a new feature first. First, it needs someone to ask whether the original assumptions about the market still hold, and to answer that question through structured, segmented customer research instead of internal gut instinct.
Published August 2026