WHAT — Designing products around customer motivation, not just features
How to Read This Document
Read the Framework document, the WHY module (Need Architecture), and the WHO module (Persona Architecture) first.
The WHY module identifies the customer needs that exist within the market. The WHO module identifies the personas organized around those needs. The WHAT module uses those insights to determine which products, features, experiences, and value propositions should be designed to satisfy them.
The assumption at this stage is that the organization has selected one or more target personas and identified the motivational territories it wishes to serve. The goal of the WHAT module is to design products and value propositions that are aligned with those customer needs, create a coherent customer experience, and support future growth opportunities.
The outputs of this module become direct inputs into the HOW MUCH module (Pricing Architecture), which determines how those value propositions should be monetized.
Product Value Proposition
KEY TAKEAWAY
Products create value
A value proposition is more than a collection of features and benefits. It is designed to satisfy a specific customer need and reinforce a specific Motivational Territory. Every value proposition serves a particular Need Domain and a particular Need Level.
Products as Value Delivery Systems
Demand Architecture, products are treated as value delivery systems rather than collections of features. The goal is not simply to build products customers prefer, but to design products that consistently deliver the value promised by a specific Motivational Territory.
The role of the WHAT module is to determine how value should be delivered. Products translate customer needs and Motivational Territories into features, experiences, and outcomes that customers can see, use, and benefit from.
The WHAT module builds on traditional product testing methods such as conjoint analysis. However, concepts are evaluated not only on preference, but also on how well they align with the needs, motivations, and future direction of target personas. The objective is to ensure that product features, benefits, positioning, and customer experiences all reinforce the same Motivational Territory and create a coherent value proposition.
A product can perform well in concept testing yet still struggle in the market if it serves the wrong motivation or sends conflicting signals. Conversely, products that align closely with the needs, motivations, and future direction of their target customers often outperform expectations because they create stronger adoption, engagement, and long-term commitment.
For this reason, the WHAT module is not simply about feature optimization. It is about designing products and value propositions that deliver the right value to the right customers in the right way.
Product Design Principles
1. Preference alone does not determine success.
The most commercially valuable opportunity is not always the concept with the highest average preference share. Some concepts – even if they have lower preference share – generate strong enthusiasm among strategically important customer personas and may represent future growth opportunities rather than current mainstream demand.
2. Products should send one clear motivational signal.
Features, benefits, messaging, pricing, onboarding, and customer experience should reinforce the same customer need and motivation. Products that send conflicting signals often struggle to build long-term adoption and loyalty.
3. Products must support the entire adoption journey.
Successful products do more than create initial interest. They reinforce customer needs and motivations throughout onboarding, usage, habit formation, and ecosystem expansion. Long-term success depends on the entire customer journey, not just the moment of choice.
Product & Value Proposition Architecture Mechanics
Research Question
The research question shifts from “Which concept wins?” to “Which concept fits which persona, serves which Motivational Territory, and supports which growth opportunity?” Preference remains important, but concepts are also evaluated based on the motivations they serve, the personas they attract, and their potential to support future growth.
Product-Market Fit Reframed
Traditional product-market fit asks whether customers want a product. Demand Architecture asks whether a product serves the right Motivational Territory for the right persona at the right stage of need evolution.
Product-market fit occurs when customer needs, target personas, product design, positioning, and experience all reinforce the same source of value. Strong fit creates adoption, engagement, loyalty, and long-term growth. Weak fit often appears as inconsistent adoption, pricing pressure, low differentiation, or high churn despite positive product testing results.
Two-Layer Product Design — Both Essential
Every product design engagement should produce two outcomes:
- Mainstream Opportunities — concepts with the strongest potential for immediate scale.
- Emerging Opportunities — concepts that reveal where customer needs and demand may be heading.
One supports growth today; the other helps prepare for growth tomorrow.
| Mainstream Products — Scale Today | Niche / High-Intensity Products — Growth Tomorrow |
|---|---|
| Broad appeal across the market | Strong appeal among specific personas or customer groups |
| Highest potential for immediate adoption and revenue | Early indicator of future growth opportunities and potential first-mover advantage |
| Optimized for current customer needs | Aligned with evolving customer needs and behaviors |
| Supports current business objectives | Helps identify future product, portfolio, and innovation opportunities |
| Often visible through traditional product testing | Often overlooked when focusing only on average preference scores |
Emerging opportunities generally fall into two categories. Some represent deeper engagement within the same Motivational Territory (vertical migration), while others reflect movement toward a different customer need (horizontal migration). The first often leads to premiumization and category expansion; the second may signal a broader shift in market direction.
Product Portfolio Architecture
Most organizations require a portfolio of products serving different Motivational Territories. Some products defend existing demand, while others prepare for future migration. Product Portfolio Architecture helps determine where to invest, expand, reposition, or retire products as customer needs evolve.
A balanced portfolio typically includes products serving today’s largest opportunities as well as products aligned with emerging customer needs and future growth opportunities.
The Same Feature Can Serve Different Needs
One of the most important principles of Product & Value Proposition Architecture is that the same feature can activate different customer motivations depending on design and framing.
| Feature | Motivational Territory | What This Means for Design and Messaging |
|---|---|---|
| AI financial assistant | Control @ Emotional | Helps customers feel organized, clear, and in charge. Emphasize visibility, reassurance, and financial stability. |
| AI financial assistant | Competence @ Identity | Helps customers feel smarter and more capable. Emphasize learning, insight, and mastery. |
| AI financial assistant | Freedom @ Emotional | Helps customers feel less burdened by money management. Emphasize automation, simplicity, and relief from effort. |
| AI financial assistant | Belonging @ Ecosystem | Helps customers make financial decisions with others who share similar values. Emphasize connection, shared goals, and community progress. |
The strategic implication is simple: a feature does not have one fixed meaning. Its meaning depends on the product architecture around it. The same AI financial assistant can be designed as a control product, a competence product, a freedom product, or a belonging product. The goal of this module is to make that design choice explicit before the product goes to market.
Product Coherence Check
Product coherence is often a stronger predictor of long-term adoption than any individual feature. Customers rarely evaluate product elements separately; they evaluate the overall signal the product sends.
Strong product concepts reinforce the same customer motivation through their features, messaging, onboarding, pricing, and customer experience. Many products fail not because individual elements are weak, but because different elements point in different directions.
For example, a product may promise freedom, require heavy monitoring during onboarding, use premium-status pricing, and create a security-oriented experience. Individually these elements may make sense; together they create a confusing value proposition.
The Product Coherence Check evaluates whether all major elements of the value proposition reinforce the same Motivational Territory.
| Dimension | Coherence Question |
|---|---|
| Messaging | Does the communication language match the target customer motivation? |
| Features | Do the product features deliver the need the concept promises? |
| Onboarding | Does the first-use experience reinforce the intended motivation? |
| Pricing | Does the pricing architecture send the right signal? |
| UX / Experience | Does the interaction create the intended emotional and behavioral outcome? |
| Expansion | Do adjacent features and ecosystem opportunities fit the same motivational territory? |
What Makes Value Proposition Architecture Different
Traditional product testing identifies what customers prefer. Value Proposition Architecture explains why they prefer it and what that means for future growth.
| Standard Conjoint Output | Value Proposition Architecture Adds |
|---|---|
| Overall preferred concept | Preferred concept plus niche product opportunities that may have lower overall appeal but generate strong adoption among specific personas and represent future growth opportunities. |
| Feature preferences averaged across all respondents | Persona-specific feature preferences plus motivational fit — which concepts align best with the needs and motivations of different personas. |
| “Concept B wins in Segment 3” | “Concept B is particularly attractive to Financial Optimizers because it reinforces their desire for control, mastery, and financial confidence.” |
Value Proposition Architecture Toolbox
The WHAT module turns product testing into product strategy. Its outputs help organizations identify winning concepts, uncover future opportunities, match products to personas, and design more coherent value propositions.
| Tool / Deliverable | What It Provides |
|---|---|
| Mainstream Concept Recommendation | Identifies the concept with the strongest potential for near-term scale. Includes the preferred concept, its motivational profile, target personas, positioning direction, and recommended activation pathway. |
| Niche Opportunity Portfolio | Identifies smaller but high-intensity product opportunities that may represent future growth. Includes priority niche concepts, target personas, enthusiasm strength, commercial potential, and whether the opportunity reflects deeper engagement or a shift toward a different customer motivation. |
| Motivational Territory Map | Maps tested concepts and key competitor products by the customer needs and motivations they serve. Shows which territories are crowded, underserved, or emerging. |
| Persona / Product Fit Matrix | Shows which concepts fit which personas. Combines preference, enthusiasm, adoption potential, price tolerance, and motivational fit to identify where each concept has the strongest opportunity. |
| Product Coherence Diagnostic | Evaluates whether the concept’s features, messaging, onboarding, pricing, UX, and expansion path reinforce the same customer motivation. Flags potential conflicts before launch. |
| Feature Ecosystem Map | Shows how product features work together as a system, not just as a list of attributes. Identifies which combinations strengthen the value proposition and which create confusion or conflict. |
| Adoption Pathway Briefs | Defines how each winning concept should move customers from interest to trial, habit formation, and longer-term engagement. Includes entry triggers, onboarding priorities, communication cues, and expansion opportunities. |
| Product Portfolio Map | Maps existing and proposed products by Motivational Territory, target persona, and growth horizon. Identifies portfolio gaps, overlap, future migration opportunities, and areas of strategic concentration. |
The ultimate goal of this module is not simply to identify the winning concept, but to understand why it wins, which customer motivations it serves, and how to build a sustainable advantage around it. Features can be copied. A clearly defined and consistently delivered Motivational Territory is much harder to replicate.
What Success Looks Like
- Product concepts aligned with motivational territories
- Portfolio gaps identified
- Future innovation opportunities prioritized