Product trends: reading demand and customer needs before you launch

A product trend is only useful if it survives three questions: who needs this, will they keep needing it, and will they pay?

What are product trends?

A product trend is a sustained change in what people want from a product type. It can be a new format, ingredient, feature, price level or use. The word "sustained" matters, because a spike is not yet a trend.

One consulting paper defines a trend as a general direction in which a market is developing. It describes a fad as intense, widely shared enthusiasm that is short-lived and not based on the object's qualities.

Where do product trend signals come from?

They come from places where people show a need before it reaches your sales figures. No single source is enough, so compare what people look for, what they say and what they buy.

Then read each need at the level where your choice sits. The five levels below use illustrative examples. A launch decision often sits at Type or Specification, while a brief can start at Attribute.

How do you tell a fad from lasting demand?

Look at the need, the buyers and the source of the excitement. You cannot know for certain early on. You can check whether the evidence leans toward a fad or toward a lasting change.

Here is an illustrative scenario. A snack brand sees a flavour spike after one viral video, and search falls within weeks. A second signal, for high-protein snacks, rises more slowly across several countries and formats. The second deserves the deeper look.

How do you validate a product trend before launch?

Move from cheap evidence to expensive evidence, and let each step earn the next. A trend signal justifies research. Research justifies a concept test. A concept test justifies a limited launch or market test.

1. Size the need. Use product research and market data to estimate who has this need and how often.
2. Understand why. Interview buyers and read reviews, because demand data rarely explains motives.
3. Check existing options. See who already serves this need, and what they miss.
4. Run a concept test. Show real category buyers a clear description, price and image.
5. Try it in the market. Use a small launch, a retailer pilot or a simulated test market.

Concept testing has one main design choice: how many concepts each person sees. One survey guide explains that monadic tests show one concept per respondent and need a sample per concept. Sequential monadic tests show several in random order. They cost less, though earlier concepts can influence later ratings.

When should you stop pursuing a product trend?

Stop when evidence misses a limit you agreed before you started. Decide those limits early, because stopping gets harder once money and reputations are involved. A clear stop is a useful result, since it frees people for the next idea.

Possible stop rules for a launch team, shown as illustrations and not as benchmarks:

• The signal fades. Interest falls for several months, outside the usual season, in every market you track.
• The need does not appear. Interviews show curiosity, but no repeated problem to solve.
• The concept loses. It scores below an existing product or your own past concepts.
• The economics fail. The price buyers accept does not cover cost and margin.
• Repeat purchase stays low. People try it in the market test, then do not return.

Set the actual thresholds from your own category and past launches. A borrowed number from another market gives false comfort. For the forecast behind those limits, read the guide to demand forecasting.

How do you build a product trend routine?

Review a short list of needs on a fixed rhythm, and give each one an owner. A monthly review suits many categories. It keeps trend work attached to the roadmap, rather than a yearly report nobody uses.

• Keep a watchlist. Note each need, its signals, its owner and its next check.
• Use three statuses. Watch it, research it or test it.
• Link it to new product development. Each "test it" item needs a route into the pipeline.
• Record outcomes. Write down what you called correctly and what you missed.