Every decision made throughout product development contributes to the product the consumer will eventually experience.
And that product is entering a category the consumer already understands.
New product launches are not only competing against other products on the market. They’re also competing against an understanding of the category that has compounded over time.
To be able to compete within that understanding, product development teams must establish what they need to understand as they build toward product validation.
The Research Before the Research
Most people recognize research as surveys, focus groups, and interviews, but the quality of that research is often determined much earlier.
Before the research phase, teams are already working from what they know about the market, competitors, consumers, product experiences, and white space opportunities. The purpose of this phase is to determine what still requires deeper investigation.
Experienced teams often do this quickly because much of that knowledge has accumulated across previous projects, categories, and research. However, experience does not eliminate the need to learn. It changes how quickly existing knowledge can be assessed against new information.
Before investing time, money, and resources into research that builds toward validation, teams need to establish what they actually need to understand.
The Five Sources That Build the Knowledge Base
Before validation, teams need a knowledge base they can reference throughout product development.
The knowledge base gives the team a reference point for determining what it knows, what it does not know, and what matters enough to investigate.
These five sources contribute to that knowledge base, and it continues to evolve as new information and insights emerge throughout product development.
1. Landscape Research
Landscape research establishes the market conditions around the idea.
It shows:
- Where is the category growing
- Where is it declining
- Which subcategories are accelerating
- Where are rebounds happening
- Where democratization is shifting access
- Where prestige, mass, luxury, or value channels are behaving differently
Landscape research places the present market in context by showing how current conditions developed and where the product concept sits within the market cycle.
2. Competitive Scanning
Competitive scanning shows what the category is already rewarding.
It reveals:
- Which claims are repeating
- Which formats are being copied
- Which communication has become standard
- Which benefits are expected rather than differentiated
- Which brands are gaining or losing relevance
The goal is to understand what has already been established competitively and what a new product concept would have to add, change, or make easier to earn consideration.
3. Social Listening
Social listening reveals what consumers are already trying to solve through their own words and behaviors, especially when no one is guiding the conversation.
This is where the team learns:
- What people complain about
- What they praise
- What they misunderstand
- What they hack together
- What they repeat without prompting
Positive and negative reactions are useful, but neutral sentiment is often overlooked. That middle ground can reveal what would need to change for passive interest to become preference or active adoption.
Its value is also in identifying consumer tensions and potential hypotheses that deserve deeper investigation.
4. Category Immersion
Category immersion shows how products work for consumers in real life. It is also one of the most easily misunderstood forms of early learning because teams have to separate their own preferences and standards from the consumer’s experience.
Experienced product development teams are looking to understand:
- Why does this work for the person it serves?
- What expectation does it satisfy?
- What tradeoff is the consumer willing to accept?
- What does the product make easier, clearer, more pleasurable, or more meaningful?
Evaluating products is not about whether the team likes them. It is about understanding why the target consumer does.
5. Observation
Observation reveals what consumers do not always think to say and the nuances that are easy to miss.
- What does the shopper pick up first?
- Do they read the front of the package or turn it over?
- Do they compare price, size, claims, ingredients, or format?
- Where do they hesitate?
- What do they ignore?
- What do sales associates repeatedly have to explain?
- Which questions continue to come up?
Behavior often reveals friction points before consumers can articulate it.
A consumer may not say, “This category is difficult to navigate.”
But they may stand in front of the shelf for several minutes, compare three products, put two back, search for reviews on their phone, and leave without buying. That’s the signal.
It may not be statistically significant yet, but it can reveal what may be worth investigating further.
The Hidden Brief Synthesizes What Matters
From this knowledge base, the team has to determine which information matters for the product being developed and what should inform the research building toward validation.
The synthesis asks:
- What themes are repeating across these sources?
- What do they reveal about the opportunity the concept is entering?
- What can the product credibly address?
- What still needs to be confirmed or challenged?
- Which unanswered questions could affect the concept or the decisions that follow?
That synthesis becomes the hidden brief. It determines the research objectives, and which methods can credibly answer them.
Research Starts with What Needs to Be Answered
The purpose of this phase is to establish what needs to be answered as the team is building toward product validation.
Research should not be where the team is figuring out what it needs to understand.
That does not make the process linear. New information and insights will continue to emerge throughout research and development. The knowledge base provides a reference point for interpreting what emerges, identifying new questions, and reconsidering what requires further investigation.
The knowledge base is not something the team finishes. It evolves alongside the product.
—by THE BUILD BRIEF