Author: Sergey Veselovsky

An introduction to Need Architecture — a new methodology for identifying, measuring, and operationalizing customer needs.

Companies invest heavily in understanding customer needs, yet translating those needs into product, pricing, and marketing decisions remains surprisingly difficult. Existing theories — including Maslow’s Hierarchy of Needs, Jobs-to-be-Done, Self-Determination Theory, Consumption Values, Identity-Based Motivation, and Means-End Chains — provide valuable insights into customer motivation, but each captures only part of the picture. What is still missing is a comprehensive system for identifying, organizing, measuring, and operationalizing customer needs.

Need Architecture provides such a system. Its central contribution is that it separates customer needs into two independent dimensions:

• Direction of motivation (Need Domain)
• Depth of motivation (Need Level)

The Methodology

Need Domains — the direction of motivation

Need Domains describe what customers are trying to achieve within a category. Each domain represents a distinct underlying human motivation shaping demand. A few examples appear below; the full list of fourteen domains is provided in the appendix.

Most products do not operate within a single Need Domain. They are typically organized around one Primary Domain — the dominant motivation that defines the core strategic territory — supported by one or more Secondary Domains that reinforce credibility, differentiation, or adoption.

Need Levels — the depth of motivation

Need Level describes how deeply a Need Domain is experienced and how important it becomes in the customer’s life. Levitt famously observed that people do not want a quarter-inch drill; they want a quarter-inch hole. Need Architecture extends this logic further: the hole itself (the functional level of the need) may simply be a solution to a deeper need. The real need may be to hang a picture (task level), make a home feel warm and personal (emotional level), or be a good homeowner (identity level). The five levels are summarized below.

The Need Architecture Matrix

Need Domains and Need Levels work together to define a customer’s Motivational Territory. The example below illustrates Motivational Territories for a financial services category. Rows show what customers are trying to achieve (Need Domains); columns show how deeply that motivation is experienced (Need Levels). Each cell is a distinct territory with its own strategic implications, expressed as [Need Domain] @ [Need Level].

For example, a brand might compete at Control @ Emotional. That single coordinate decides everything downstream. Its rivals are products that make customers feel financially stable — not those selling excitement or belonging. Its job is to create a sense of calm and control, not just deliver information. Its price is justified by that feeling, not by features. And it fails the moment the experience makes customers anxious. Which cell you choose shapes every decision that follows, from value proposition to pricing to customer experience.

The Proof of Concept

The Need Architecture Matrix is category-independent. The following illustrative example applies the same methodology to identify Motivational Territories within a specific market: prepaid cards in Canada.

Step 1 — Measure Need Domains using MaxDiff

Need Architecture is built around fourteen fundamental Need Domains representing broad human motivations (see appendix). Because these domains are universal, they must be translated into category-specific expressions before they can be measured. All Need Domain statements were intentionally written at the functional Need Level to avoid introducing Need Level bias into the MaxDiff exercise. For example, the Safety domain was expressed as “Safety: I want to protect my primary bank or card when making purchases online,” and the Control domain as “Control: I want to manage my spending and stay within my budget.”

The five leading Need Domains selected by respondents for a prepaid card were:

Step 2 — Code Need Levels from AI-guided interviews

The dominant Need Level was identified by coding AI-guided interviews conducted after the MaxDiff exercise. The interviews focused on the Need Domains each respondent selected most often during the MaxDiff exercise, exploring the reasons behind those choices to determine the depth at which the underlying need is experienced (Functional, Task, Emotional, Identity, or Ecosystem).

Output — the Motivational Territory Map

Combining domain preference with coded domain level reveals how much demand sits in each Motivational Territory. Each figure below is the share of people whose need for a prepaid card falls in that cell. These five domains account for 92% of people; the remaining 8% fall into other domains. None of the domains reached the Ecosystem level.

Shaded cell = the dominant Need Level for each domain.

Read in order of demand, the map tells a clear story. Different Need Domains gravitate toward different Need Levels, and the largest pockets of demand are concentrated in a handful of cells.

Safety @ Emotional (21.1%) — by far the largest single cell. Safety is experienced as reassurance, not as a feature.

“I do some online transactions, and I’m always afraid of cyber attacks on my card. It would be nice to have piece of mind, and the card not linked at all to my bank account.”

Caregiving @ Task (12.5%) — caregiving is expressed as a convenient way to provide for others.

“I usually give gift cards to friends & family, so they can purchase whatever they want. It makes things easier for me, eliminates the cost of shipping & presents that don’t fit or the recipient would never use.”

Control @ Task (9.4%) — control is about managing spending with less effort.

“As a student I have a hard time with budgeting and often end up spending too much money. If I had a prepaid card I think it would help me better manage my finances.”

Freedom @ Functional (7.7%) — freedom shows up as practical travel utility.

“I think it’s very helpful to be able to load multiple currencies especially for traveling to different countries in a short period of time without the hassle of carrying a bunch of different currencies.”

Self-expression @ Identity (4.3%) and Emotional (3.8%) — the only domain that reaches the identity level.

“Gambling is my thing and I like keeping it on its own card, separate from my everyday life. It’s my own little world.”

In short, several need-specific opportunities emerge — Safety @ Emotional, Caregiving @ Task, Control @ Task, Freedom @ Functional, and Self-expression @ Identity & Emotional. We can now compare this demand side with a supply-side reading of the Canadian market.

On that reading, the main supply is concentrated in three of the five demand areas:

• Control @ Task and Functional (BMO Prepaid, EQ Bank Card, Neo Money, KOHO)
• Freedom @ Functional (Wise, Cash Passport, Wealthsimple Cash)
• Caregiving @ Task (Vanilla gift cards, Neo JA card)

The Strategic Implication

The two clearest demand–supply mismatches point to concrete opportunities.

Safety @ Emotional is the single largest underserved cell. Nobody is selling the reassurance-against-fraud need, so it sits essentially unoccupied. Cards treat security as table-stakes plumbing (CDIC, encryption), not as an emotional brand. Nobody owns “the card that lets you stop worrying online.”

Self-expression @ Identity is a true white space. The only identity-expressive prepaid in Canada is a kids’ product (Mydoh-by-Me). The adult version of that need is currently served backwards: generic cards (Vanilla, JokerCard, Paysafe) get used for gambling, but the motivation in the market is privacy — keeping gambling off a bank statement — and staying in control of spend. It is being met as a Safety / Control job, not as a Self-expression brand. The identity or emotional play for Self-expression does not yet exist, but could gain traction.

Taken together, this proof of concept shows how Need Architecture converts a flat list of customer needs into a navigable map of strategic positions.

• By combining MaxDiff with AI-guided interviews, it identifies not only what customers want but how deeply those motivations shape behavior.
• Overlaying that demand on the competitive supply reveals where demand outruns what the market currently offers.

For Canadian prepaid cards, two openings stand out — an emotionally anchored safety proposition and an identity-driven self-expression play.

The same method applies to any category: identify the Motivational Territory customers seek, locate the territories competitors occupy, and design products, pricing, and experiences around the territory with the greatest strategic opportunity.

Where This Fits

Need Architecture is one of five modules that make up the broader Demand Architecture framework. It provides the foundation for the system by identifying the underlying human needs and Motivational Territories that drive demand. The remaining modules build on it: Persona Architecture identifies the people most likely to occupy those territories; Product & Value Proposition Architecture designs solutions that create value within them; Pricing Architecture determines how that value is monetized; and Experience Architecture evaluates whether the experience reinforces or weakens long-term commitment.

Learn more about the framework at demandarchitecture.org, and read the full Need Architecture methodology at demandarchitecture.org/need-architecture.

Appendix — The Full List of Customer Need Domains

Note: In this proof of concept the Security domain is expressed as “Safety” to match the category-specific language used with respondents.