A phone can be a product, a manufactured good, an item in a retailer’s catalog, and the object transferred in a sale. Crude oil is a product of extraction and a commodity traded in standardized units. Software may be called a product even when the customer never owns a copy and only receives access to a service.

The material object alone does not settle the vocabulary. Each term highlights a different relation.

A product organizes capabilities for use. A market offering organizes the terms under which capabilities, goods, services, or rights are exchanged.

This distinction has to be established before asking what customers “really” buy.

What Is a Product?

In a broad business sense, a product is an organized set of capabilities and experiences made available to users in a particular context.

It can be a physical object, a digital system, a service, an informational work, or a combination of technology and human activity. The American Marketing Association defines a product broadly as a bundle of attributes—features, functions, benefits, and uses—capable of exchange or use. It may be an idea, a physical good, a service, or a combination. AMA: Definitions of Marketing

A product normally gives structure to six questions:

1. Who will use it, buy it, maintain it, or bear its effects?
2. In what situation will use occur?
3. What task, capability, or change is at stake?
4. What features, content, processes, and services make use possible?
5. How will people discover, obtain, learn, use, support, and leave it?
6. What evidence will show whether it worked and at what cost?

Technology is an enabling capability. A feature is one behavior within a larger arrangement. A project is temporary work. An output is anything a process produces. None of these alone establishes a product.

A language model is a technical capability. A system that combines the model with an interface, accounts, context handling, file operations, safety controls, support, and continuing operation can become an AI product.

Product, Good, Service, Commodity, and Offering

English separates several concepts that cannot be mapped to a single word in every context.

A laptop is a product and a good. Repair is a service. Wheat futures concern a commodity. A business laptop plan that includes hardware, financing, support, warranty, and device management is an offering.

The boundaries vary by discipline. Marketing often uses product as the umbrella. Quality management distinguishes outputs, products, and services to allocate process and delivery responsibilities. Software practice calls a continuously operated service a product because it has users, versions, capabilities, support, and an evolving value proposition. ISO 9000:2026

The useful question is not which vocabulary is universally correct. It is which distinction the present analysis needs.

What Makes Something a Market Offering?

A usable product does not by itself specify a transaction.

A market offering adds answers to questions such as:

• What is the unit being sold?
• What price and payment schedule apply?
• Does the customer receive ownership, possession, access, or a license?
• What quantity, duration, territory, or usage limit applies?
• What support, warranty, maintenance, or service level is included?
• What happens on cancellation, return, failure, or renewal?
• How are privacy, liability, and risk allocated?

The structure can be summarized as:

market offering
= product capabilities
+ deliverables
+ ownership, access, or license rights
+ quantity and duration
+ price and payment terms
+ service commitments
+ return, repair, renewal, and exit rules
+ allocation of risk and responsibility

One knowledge-management product can appear as a free personal plan, a monthly professional subscription, a per-seat team plan, an enterprise agreement with migration and training, or a private deployment contract. The underlying capabilities overlap; the offers do not.

A Product Can Exist Without a Retail Sale

The relation between product and market exchange is not one-to-one.

An internal tool can be managed as a product even though it is not sold outside the organization. Open-source software can be a mature product while access to the code remains free. A public service can be designed and operated as a product without charging the final user. A prototype can contain a product hypothesis before there is a stable commercial offer.

Conversely, being listed and sold does not establish product quality. A transaction shows that an exchange occurred under particular conditions. It does not show that the product was usable, beneficial, fair, or sustainable.

The same object can also change institutional roles without changing its physical form. A computer is a design object during development, a manufactured product at completion, a good in inventory, the object of a sale, the buyer’s property after transfer, and an organizational asset when put to work.

Ownership, Access, and Performance

Different offers transfer different things.

Physical goods

A sale usually transfers ownership or possession of an item. The buyer of a chair receives the object and, within legal and contractual limits, may use, resell, modify, or dispose of it.

Services

A service sale normally concerns an activity, performance, or commitment. A haircut, consultation, and journey are completed through interaction. The customer does not take possession of “the service” as a durable object.

Digital products

Digital transactions often transfer neither a physical object nor ownership of the underlying software. They may provide:

• a time-limited right of access;
• a license to run or reproduce software;
• a usage allowance measured by seats, storage, calls, or tokens;
• continuing operation and support;
• rights over content or virtual items defined by platform rules.

Calling all of these “buying software” hides the legal and operational differences.

Products and Offerings in Everyday Life

The distinction appears across ordinary domains.

Walking can satisfy a mobility need without a product purchase. Buying a bicycle usually transfers a good. Bike sharing sells temporary access. A metro ticket buys a transport service. The domain does not determine the form of exchange.

How Does a Product Relate to a Need?

A need describes a missing or required condition in a person’s situation. A product is one organized response.

A product turns a supplier’s interpretation of a need into a capability that can be used and tested.

“I need a car” already contains a proposed solution. Further inquiry may reveal a chain:

wants to buy a car
→ must commute regularly
→ wants to arrive reliably and comfortably
→ needs practical control over mobility within family, work, and time constraints

A car may be appropriate. So may rail, cycling, moving home, car sharing, remote work, or a different schedule.

This is why a product is better treated as a testable supply hypothesis than as the need itself. The hypothesis survives only if relevant users can discover, understand, obtain, use, and benefit from the product in actual conditions.

Need Is Not Market Demand

An urgent need does not automatically create a viable offer.

A person may need care without being able to pay. A user may value a tool while rejecting its subscription terms, privacy policy, switching costs, or procurement requirements. A product may work but remain inaccessible through the available channel.

Moving from need to purchase requires several different kinds of fit:

1. Problem fit: the situation matters to the intended user.
2. Capability fit: the product supplies a relevant condition.
3. Context fit: the environment allows the capability to work.
4. Comprehension fit: people can find and understand the offer.
5. Economic fit: price, access, and payment conditions are acceptable.
6. Trust fit: the source and its promises are credible enough.
7. Outcome fit: use actually improves the original situation.

Need, demand, purchase, adoption, and outcome are different stages and different evidence.

User, Customer, Buyer, and Beneficiary

The person who needs or uses a product is not always the person who buys it.

For a child’s toy, a parent may decide, buy, and pay while the child uses and benefits. In enterprise software, executives may authorize, procurement may buy, finance may pay, employees may use, and IT or legal teams may control risk.

A product can satisfy users while failing to give a customer a reason to buy. An offer can satisfy procurement while imposing an unusable system on employees. Product design and commercial design must account for both sides without pretending they are the same person.

What Does a Customer Actually Buy?

There are two valid answers at different levels.

The transaction transfers deliverables, rights, and commitments

A customer may receive ownership of a good, licensed use, access for a period, a quantity of service, warranty rights, support, privacy terms, or remedies when performance fails.

An AI subscription grants access to specified capabilities under limits and terms. It does not directly transfer a correct answer, a finished career task, or improved intelligence.

At the transaction level, the customer buys a defined bundle of deliverables, rights, commitments, and allocated risks.

The motivation concerns expected progress

The customer accepts that bundle because it is expected to help complete a task, save time, reduce uncertainty, avoid loss, create an experience, express identity, or preserve an option.

Jobs to Be Done describes customers as “hiring” products to make progress in a circumstance. Its strength is to direct attention away from features and toward what changes for the customer. Harvard Business School Online

But saying “customers buy outcomes” goes too far.

Why the Outcome Is Usually Not the Product

A course can supply instruction, practice, and feedback without guaranteeing mastery. A gym can supply equipment and coaching without guaranteeing health. A physician can provide competent treatment without guaranteeing recovery. An AI system can provide analytical capability without guaranteeing truth.

Outcomes commonly depend on three sources:

capabilities and conditions supplied by the product
+ action and contribution by the user
+ surrounding circumstances and constraints
= realized outcome

Service-dominant logic captures part of this distinction by treating firms as participants in value creation rather than as manufacturers of value fully contained inside goods. Value becomes concrete in use and context. Vargo and Lusch

A precise formulation is:

A customer buys a bundle of conditions believed to improve the probability of a desired outcome, not the guaranteed outcome itself.

A contract may make a supplier responsible for a defined result. Even then, the result, measurement conditions, exclusions, and remedies have to be specified.

Exchange Value Is Not Use Value

A purchase demonstrates that a customer accepted an exchange under the information, alternatives, price, and constraints present at the time.

It does not prove that the product solved the problem, that the decision was fully informed, that the price was fair, or that third parties were unharmed. Promotion, misunderstanding, habit, conformity, lock-in, and lack of alternatives can all produce sales.

The evidence should remain separated:

noticed
→ understood
→ considered
→ purchased
→ activated
→ repeatedly used
→ produced an intended outcome
→ remained worthwhile over time

Exchange validates a transaction. Use validates adoption. Outcome evidence is required to test whether the original need was addressed.

Where Brand Enters

Customers cannot fully inspect future performance before purchase. They use source identity, prior experience, reputation, reviews, and promises to estimate uncertainty.

A brand compresses those signals into recognition and expectation. It can reduce search cost, make an offer easier to interpret, and identify who should be held accountable. It may also carry aesthetic, social, and identity meanings.

Brand can improve the exchangeability of an offer. It cannot perform the user’s task. The brand forms an expectation, the offer defines a transaction, the product enters use, and the result confirms or corrects the expectation.

A Test for Product and Offering Claims

Before saying that a product “meets demand,” ask:

1. What capabilities are organized into the product?
2. Who uses it, in what context, and for what task?
3. What precisely is included in the offer?
4. Which ownership, access, license, support, and exit rights transfer?
5. Who uses, buys, pays, decides, benefits, and bears risk?
6. Which need is the product intended to address?
7. What commercial and noncommercial alternatives exist?
8. Which outcomes can the supplier control?
9. Does purchase lead to adoption?
10. Does use improve the original situation after total cost and side effects are counted?

These questions test product structure, transaction structure, and need fit separately.

Conclusion

A product and a market offering are related but distinct.

A product organizes capabilities so that value can occur in use. An offering organizes exchange by specifying what the customer obtains, under which rights, obligations, prices, and risks.

Needs enter the account after those boundaries are clear. A need describes a condition required in a situation. A product is a testable response. An offering turns that response into a transaction.

Customers acquire deliverables, rights, and commitments because they expect those conditions to help them make progress. Whether value was realized remains a question for use and outcomes, not for the sales record alone.

References

• American Marketing Association — Definitions of Marketing
• ISO 9000:2026 — Quality management: Fundamentals and vocabulary
• ISO 9241-115:2024 — User needs and user requirements
• Harvard Business School Online — Jobs to Be Done
• Vargo and Lusch — Service-dominant logic: continuing the evolution
• Karl Marx — Capital, Volume I, Chapter One

Matching demand and supply is therefore a problem of interpretation, delivery, and learning.

The concepts occupy different positions:

• User intent belongs to the demand side. It concerns what a person is preparing to do or trying to accomplish in a situation.
• Product belongs to the supply side. It organizes capabilities and experiences intended to change that situation.
• Brand connects supply with recognition. It helps people find the source, understand its difference, form expectations, and decide how much provisional trust to place in it.

The firm is the supplier. The product is its vehicle of capability. The brand is the recognition and expectation system around the identifiable source.

Intent gives action a direction. A product offers capability for moving in that direction. A brand helps the user discover, interpret, and evaluate the offer under uncertainty.

Fit is not a single moment in which a company finally reads the user’s mind. It is a revisable relationship built through expression, discovery, use, results, and correction.

Need, Want, Goal, Intent, Demand, and Behavior

Many failures begin by collapsing several layers into one.

Suppose someone says, “I need more notifications.”

That sentence may identify a proposed feature rather than a need. The underlying situation could be fear of missing a deadline. The need may be reliable awareness of urgent changes. The goal may be to respond before a cutoff. The intent may be to check a dashboard every morning. More notifications are only one possible solution, and they may worsen distraction.

A purchase is behavior. It may express an intention, but it can also result from a promotion, inertia, confusion, social pressure, lack of alternatives, or a cancellation barrier. Retention establishes continued use, not the reason for use and not the value of the outcome.

The first discipline of matching is therefore to preserve the layers.

Is There One True Intent?

Sometimes a user has a clear and stable intention: book a train for tomorrow, submit a tax return, or send a file to a colleague. Product work can concentrate on interpreting the conditions and completing the task.

Other situations are less settled:

• the user holds conflicting intentions;
• dissatisfaction is clear but the desired change is not;
• the user names a familiar solution instead of the underlying outcome;
• cost, information, and experience alter the intention;
• immediate impulse conflicts with a longer-term goal;
• the user understands the choice only after trying it.

“True intent” can then mean at least three things:

1. the action the user currently plans to take;
2. the intention the user still endorses after learning the costs and consequences;
3. an action that actually addresses the deeper condition behind the problem.

These can diverge. A person may intend to buy an attention tool, later decide the subscription is not worth its data cost, and discover through use that the real problem was an overloaded work process.

Intent is partly discovered through reflection and partly formed through comparison, commitment, and action. A useful question is not whether a hidden, permanent intention has been uncovered. It is:

Given the current situation, evidence, costs, and values, is this an intention the person understands, endorses, and is prepared to act on?

What a Company Can Know

A company observes signals, not needs directly.

Interviews, search queries, support conversations, purchases, usage, abandonment, workarounds, complaints, and outcomes all provide evidence. Each has limits.

What users say

Language reveals how people understand their situation and which distinctions they can express. Reports can still be distorted by memory, social expectations, limited vocabulary, and question design.

What users do

Behavior proves that an event occurred. It does not by itself identify the cause. A click can indicate interest or confusion. Long time on a page can indicate engagement or difficulty. Renewal can indicate value or high switching cost.

The context of use

Tasks, resources, physical conditions, social rules, skill, time pressure, and organizational environment often explain more than an isolated feature request. Human-centred design treats users, goals, tasks, resources, and environments as parts of the same context.ISO 9241-210:2019

What persists over time

Repeated obstacles, costly workarounds, and stable outcome gaps usually provide stronger evidence than one statement. Longitudinal evidence can also reveal when a product removes one problem but creates another.

A company can improve its model of demand. It cannot turn evidence into direct access to private mental states.

From Evidence to a Product

Insight does not move into a product without loss. At least six transformations occur:

user situation
    ↓ interpretation
need hypothesis
    ↓ selection
target user and value proposition
    ↓ design
product capability and interaction
    ↓ delivery
experience in actual use
    ↓ measurement
outcome, cost, and risk
    ↓ learning
revised need and product model

A failure can enter at every transition.

The company may understand the problem but target the wrong group. A useful capability may be too difficult to discover or learn. A product may create short-term improvement and long-term dependence. The user may benefit while the buyer sees no reason to pay. Average improvement may conceal severe harm to a smaller group.

This is why “the feature works” is a narrower statement than “the product fits the need.”

What Brand Contributes

A product addresses whether a capability can produce a result. A brand affects whether the relevant person can find, understand, and provisionally trust the source.

Discovery

Positioning, category language, distribution, and recognizable cues help a person connect an offer to a situation. A capable product cannot be considered if it is not found at the relevant time.

Interpretation

A clear brand claim tells people whom the product is for, which problem it addresses, what makes it different, and what evidence should be expected. Vague claims make almost any result appear consistent with the promise.

Risk reduction

People cannot test every alternative completely. Source recognition, prior experience, recommendations, and reputation compress information into an expectation. This expectation is probabilistic and must remain open to current product evidence.

Attribution

When a useful experience has no identifiable source, the product may succeed without building memory or trust around the provider. Attribution lets experience affect the next choice.

Accountability

A brand connects many products and actions to the same source. That allows trust to accumulate, and it allows users and institutions to assign responsibility when promises fail.

Brand influence is not neutral. It can help people name a poorly understood need. It can also redescribe ordinary insecurity as a defect that only consumption can repair. The test is whether claims improve understanding and choice or narrow them through manipulation.

Eight Dimensions of Fit

A useful match must survive more than one metric.

1. Problem fit: Does the offer address a problem in the user’s actual situation?
2. Capability fit: Can the product produce the required change?
3. Context fit: Can it work within the user’s time, environment, skill, and workflow?
4. Cognitive fit: Can the user understand what it is, why it matters, and how to use it?
5. Economic fit: Are price, access, learning, switching, and exit costs acceptable?
6. Value fit: Is the method compatible with the user’s identity, principles, and longer-term interests?
7. Trust fit: Is the source credible about performance, risk, data, and support?
8. Outcome fit: Does actual use improve the intended result without imposing unacceptable harm?

No product fits “the user” in the abstract. It fits particular people, situations, times, alternatives, and costs to a greater or lesser degree.

The User Also Needs a Learning Loop

The burden of interpretation does not belong only to the company. A user can clarify intention through a sequence:

notice a problem or attraction
    ↓
describe the current situation
    ↓
separate need, want, goal, and proposed solution
    ↓
form a provisional intention
    ↓
compare brand claims and product capabilities
    ↓
try at a proportionate cost
    ↓
observe results and revise

Useful questions include:

1. What is happening before I name something to buy?
2. Which condition or outcome needs to change?
3. Is this my goal, or a goal offered to me by the seller?
4. Have I confused a desired result with one proposed solution?
5. Would I still address this problem if this brand did not exist?
6. Which money, time, attention, data, and opportunity costs will I accept?
7. What happened after use?
8. After understanding the longer-term effects, do I still endorse the choice?

This process does not uncover a socially untouched inner self. Human desires are shaped by language, culture, comparison, and institutions. Reflection makes those influences more visible and preserves the ability to compare, refuse, and exit.

Two Learning Systems Meet

The supplier’s loop is:

observe situations
→ propose need hypotheses
→ build the smallest useful test
→ observe use and outcomes
→ revise product and brand claims

The user’s loop is:

experience a situation
→ form a provisional intention
→ discover and compare offers
→ use and bear consequences
→ revise self-understanding and choice

They meet at four points:

• Expression: Can the user describe the problem, and can the brand respond in intelligible language?
• Discovery: Can a person with the relevant situation find the offer at the right time?
• Use: Does the product enter the actual context and produce a result?
• Learning: Can both sides learn from success, failure, misuse, and exit?

Product–market fit is often discussed as though the market emits a simple verdict. In practice, the observed result is produced by a distribution channel, price, alternatives, product quality, switching costs, user differences, and measurement choices. Fit must be diagnosed, not merely declared.

Why Matching Fails

A requested solution is treated as the need

The company implements what was requested without examining the situation that produced the request.

Behavior is treated as intention

Clicks, time spent, purchases, and retention are assigned psychological meanings they cannot establish alone.

Average behavior replaces user variation

One metric hides distinct intentions, contexts, and concentrated harm.

The brand promise is too broad

A claim for everyone cannot help anyone determine relevance and cannot be clearly tested.

Immediate impulse displaces endorsed goals

A system optimized for repeated reaction may increase activity while weakening attention, health, or autonomy.

Insight never reaches organizational response

Research remains in a report while product priorities, service, pricing, incentives, and resource allocation continue unchanged. Market orientation requires generating intelligence, sharing it across the organization, and responding to it, rather than merely listening.Kohli and Jaworski, “Market Orientation”

Choice is constrained

Lock-in, opaque information, defaults, and missing alternatives weaken the claim that observed use expresses preference.

Can a Company Create Demand?

A company can reveal an unmet need, create a capability that did not exist, teach people about a new possibility, form a product category, shape a specific desire, or engineer dependence.

Those actions are not ethically equivalent.

The relevant questions are:

• Did the user gain a real capability?
• Are the promise, mechanism, cost, and risk understandable?
• Can alternatives be compared?
• Can the person refuse and leave?
• Do longer-term outcomes remain consistent with interests the user still endorses?
• Are third parties bearing hidden costs?

Influence is unavoidable. Manipulation is not. The difference depends on truthfulness, agency, reversibility, and the distribution of consequences.

The Result

A company can form increasingly reliable hypotheses about demand. It cannot prove that it has read a person’s final and private need.

A product can produce a good fit for specified people and conditions. One successful period does not establish permanent fit.

A user can develop a clearer intention through reflection, comparison, trial, and attention to consequences. There may be no single fixed intention waiting to be found.

The relationship is best understood as reciprocal calibration:

The user moves from an unclear situation toward an actionable intention. The company moves from incomplete evidence toward a need hypothesis. The product exposes that hypothesis to use. The brand helps both sides find one another, set expectations, and remember what happened.

The strongest fit leaves the user better able to understand the situation, the product able to improve a concrete outcome, the brand claim consistent with evidence, and both sides free to revise their judgment.

Sources

• ISO 9241-210:2019: Human-centred design for interactive systems
• ISO 9241-115:2024: Guidance on conceptual design, user-system interaction design, user interface design, and navigation design
• Kohli and Jaworski, 1990: Market Orientation
• Stanford Encyclopedia of Philosophy: Intention
• What Does It Mean to Need Something?
• Intention: How a Commitment Organizes Action
• Brand and Product: Delivery, Expectation, and Trust
• User Intent in AI: Inference Under Uncertainty

A need is not simply a strong preference. Nor is it whatever a customer will pay for.

A need is a condition, capability, resource, or change that a subject requires in a particular situation in order to achieve an outcome, maintain a function, avoid harm, or realize an important value.

A complete need claim therefore has a relational form:

a subject
in a context
seeking or avoiding an outcome
requires a condition

A presenter working under a fixed time limit needs to know how much time remains in order to finish on schedule. Knowing the remaining time is the need. A watch, a countdown display, a phone app, and a signal from a moderator are possible solutions.

ISO 9241-115:2024 defines a user need in the same relational way: a prerequisite identified as necessary for a user to achieve an intended outcome in a specific context of use. It explicitly states that the need is independent of any proposed solution.

“The user needs an app” usually arrives too late in the analysis. It has already selected a means.

Need, Want, Demand, Intention, and Requirement

The distinctions become clearer when each term is made to answer one question.

A person may need medical care without wanting it. Someone may intensely desire something harmful. A household may want a product but lack the income to create effective market demand. A team may write a precise requirement that addresses the wrong need.

ISO/IEC/IEEE 29148:2018 places requirements in systems and software engineering. A requirement expresses a need together with associated constraints and conditions so that it can guide design and verification.

The transitions are possible, not automatic:

need → recognized problem → goal → intention → action
need → solution hypothesis → requirement → design → product
want + willingness and ability to pay → market demand

At every arrow, interpretation, resources, institutions, and alternatives can change what happens next.

Needs Are Not Only Felt Deficiencies

The language of a “gap” is useful. A person notices a difference between the present condition and a desired one. But not every need begins with dissatisfaction.

Some needs concern restoration: food when hungry, medical care when ill. Others concern maintenance: sleep, nutrition, backups, and routine safety measures preserve a condition that has not yet failed. Still others concern prevention: insurance, redundancy, and protective equipment respond to possible future harm.

This produces three broad forms:

1. restore an impaired condition;
2. maintain a valuable condition;
3. prevent a credible loss or harm.

A need may also exist before the person can describe it. Children, patients, and people facing inaccessible systems may be unable to articulate important conditions. Yet experts can also misuse the language of “real needs” to impose their own values.

Good need judgments therefore combine lived experience, contextual evidence, relevant expertise, and observable consequences. No single party has automatic access to the whole answer.

Maslow’s Five Sets of Basic Needs

Abraham Maslow’s hierarchy remains the best-known account of human needs in popular psychology and management. In his 1943 paper, “A Theory of Human Motivation,” Maslow proposed at least five sets of basic needs arranged in a hierarchy of relative prepotency.

The important phrase is relative prepotency. Maslow did not require one level to be completely satisfied before another could appear. An urgently frustrated need tends to dominate attention and organize behavior. Once it is sufficiently satisfied, other motives can become more prominent.

His original account also allowed partial satisfaction, simultaneous motives, exceptions, and reversals. A person may sacrifice safety for love, recognition, moral commitment, or creative work. Treating the theory as a universal sequence of five locked stages is more rigid than Maslow’s own formulation.

The familiar pyramid was not drawn by Maslow. Historical research by Bridgman, Cummings, and Ballard traces the pyramid to later management teaching and visual simplification. The diagram made the theory memorable, but it also encouraged the idea that people must climb one level at a time. Who Built Maslow’s Pyramid?

Maslow remains useful because he refused to explain motivation only through bodily drives or financial incentives. Belonging, dignity, growth, and the development of human capacities matter. But the hierarchy is not a complete product-research taxonomy, and evidence does not support treating its exact order as a universal law across persons and cultures.

Other Ways to Classify Needs

Needs can be grouped for different purposes.

• Bodily maintenance: nutrition, rest, movement, health, and protection.
• Safety and continuity: physical security, income stability, data protection, and predictability.
• Task and capability: conditions required to work, learn, communicate, care, create, or manage.
• Information and understanding: facts, explanations, orientation, and reduced uncertainty.
• Agency and control: choice, correction, manageable effort, and the ability to exit.
• Relationship and belonging: companionship, cooperation, intimacy, and social participation.
• Identity and recognition: dignity, status, expression, and acknowledgment by others.
• Experience and meaning: pleasure, beauty, curiosity, commitment, and a coherent sense of what matters.

Self-determination theory offers another influential account. It treats autonomy, competence, and relatedness as basic psychological needs whose satisfaction supports development and well-being. This is an empirical theory with specific criteria, not proof that all human needs have been reduced to three. Basic Psychological Needs

These frameworks answer different questions. Maslow describes a proposed motivational priority. Self-determination theory studies psychological nutriments associated with functioning and well-being. Product research identifies conditions required in a particular context. One list should not silently replace the others.

Clothing, Food, Housing, and Mobility Are Domains

Everyday categories such as clothing, food, housing, and mobility describe domains of life. They are not a complete taxonomy of needs.

Food can answer hunger, nutrition, safety, convenience, pleasure, ritual, hospitality, and identity. Housing can provide shelter, privacy, stability, location, family space, status, or an investment position. Mobility can involve distance, punctuality, safety, autonomy, comfort, and access to work or care.

The same domain contains many needs, and the same need crosses many domains. Safety can involve food, housing, transportation, finance, health, or software. Belonging can be served through a home, a meal, a club, a communication service, or no commercial product at all.

Are Needs Objective or Subjective?

Some needs have a strong physiological and causal basis. Severe dehydration harms the body. Others depend on goals and institutions. A person needs internet access to join an online meeting because a social organization has made online participation a condition of work.

A need claim can be represented as:

subject A
for purpose G
in context C
requires condition X

That structure exposes two different judgments:

1. Causal judgment: What happens without X?
2. Normative judgment: Is G worth achieving, or is the threatened outcome worth avoiding?

The fact that X is necessary for a goal does not make the goal legitimate. A harmful plan may require effective tools. Need claims acquire moral and political force only when we also consider harm, rights, alternatives, responsibility, and the distribution of cost. Stanford Encyclopedia of Philosophy: Needs

Do Companies Discover Needs or Create Them?

Several different mechanisms are hidden inside the phrase “create demand.” A company can:

• discover a recurring difficulty that people have not named;
• create a capability that makes a new outcome possible;
• shape a desire around a particular object or identity;
• turn interest into effective demand through price, access, credit, and trust;
• alter social expectations until a formerly optional capability becomes practically necessary;
• create dependency through lock-in, network effects, or the removal of alternatives.

Smartphones did not invent communication or belonging. They changed how those needs could be met and changed expectations about availability. As work and public services reorganized around smartphones, access to one could become a practical condition of participation.

Discovery, innovation, persuasion, market formation, and dependency creation have different ethical consequences. They should not be collapsed into one triumphant claim that a company “created a need.”

How Can a Need Be Investigated?

A company cannot observe a need directly. It develops a need hypothesis from evidence.

Useful questions include:

1. Who is in which situation?
2. What outcome matters, or what harm must be avoided?
3. What condition appears to be missing?
4. What workaround is used now?
5. How frequent and serious is the problem?
6. What time, money, risk, and opportunity cost are already being spent?
7. Are the user, buyer, payer, beneficiary, and affected party the same?
8. After a proposed solution is used, does the original situation improve?

Interviews show how people interpret their experience. Observation shows how activity actually unfolds. Behavioral data show what happened but rarely settle why. Experiments test candidate explanations. Complaints, misuse, exclusion, and abandonment expose mismatches that successful transactions can hide.

Interest, purchase, use, satisfaction, and outcome are separate forms of evidence.

Conclusion

A need is not a feature request, a product category, a purchase, or everything a person says they want.

It is a relation in which a subject, in a particular context and for an outcome that matters, requires a condition.

Maslow’s hierarchy is an important historical model of motivation, especially because it brought belonging, esteem, and self-actualization into the account. It is most useful as a prompt for inquiry, not as a rigid pyramid or a universal product template.

The practical test remains specific: Who needs which condition, in what context, for which outcome? What evidence makes the condition necessary? When it is provided, does the person’s situation actually improve?

References

• A. H. Maslow — A Theory of Human Motivation, 1943
• Abraham Maslow — Motivation and Personality, 1954
• Bridgman, Cummings, and Ballard — Who Built Maslow’s Pyramid?
• ISO 9241-115:2024 — User needs and user requirements
• ISO/IEC/IEEE 29148:2018 — Requirements engineering
• Stanford Encyclopedia of Philosophy — Needs in Moral and Political Philosophy
• Self-Determination Theory — Basic Psychological Needs