Skip to content

Distinguish needs and wants when planning product use

Summary

Distinguish underlying needs and specific wants through real purchasing situations, then assess product specifications, prices, and small-scale tests.

Published

Investigate the underlying difficulty and preferred method in context

A need is an underlying requirement; a want is a preferred way of satisfying it. Needing food and choosing a particular dish are distinguishable.

Necessity does not guarantee sales, and preference does not imply failure. Investigate use contexts, costs, and current alternatives.

Distinguish the problem from the preferred solution

OpenStax includes understanding needs, designing offerings, communication, and distribution in marketing. Investigate contexts alongside requested product names. (OpenStax: Marketing and the Marketing Process)

The same product serves different situations, such as a quick meal or a gift. Record practical requirements and preferences.

Ask about actual purchasing situations

Ask about timing, triggers, alternatives, and actual use. Record stated purchase intent separately from purchases.

Connect price or effort preventing a preferred method to product and channel decisions.

Test a limited offering and price

Explain specifications, price, and purchase steps for the hypothesised context. Ask prototype users what helped and what preparation was missing.

Record understanding, applications, and purchases separately and log specification changes. Publish use and actual offering on the product page.

SpreadSite is a no-code website builder that lets you create, publish, and update a website from Google Sheets using ready-made templates.

To publish product uses and concrete offerings, give SpreadSite a try!

Build a website with SpreadSite →

Frequently asked questions

Q: Do need-based products always sell?

A: Prices, context, alternatives, and purchase channels matter too.

Q: Are wants unnecessary preferences?

A: They express preferred ways of satisfying a need; preferences can matter in selection.

Q: Should every request become a product?

A: Assess difficulties, current methods, and purchase records.

Q: What should a test explain?

A: Use, specifications, price, preparation, and purchase steps.

Sources

Build a website with Google Sheets using SpreadSite