People often tell you what they want — a faster app, a cleaner homepage, more control. But design isn’t just about listening. It’s about uncovering what they actually need. Wants are often surface-level, shaped by past habits or trends. Needs run deeper: they reveal the problems people are trying to solve, the emotions they’re navigating, and the goals they may not know how to articulate. As designers, we may begin by asking users what they want — but our real job is to observe, probe, and translate those wants into meaningful, usable solutions that meet their underlying needs. All these following categories are simply different ways of looking at the same thing: human needs. By examining them through multiple lenses, we expand our chances of understanding what truly matters to the people we’re designing for.

1. Stated vs. Unstated Needs

Example: Designing an Online Railway Ticket Booking System

Stated Need:

• “I want to book a train ticket easily.”
• The reader asks for fewer steps, smoother search, faster checkout.

Unstated Need:

• They want confidence that the ticket is actually booked.
• They want clarity on refund rules or train delays.
• They fear booking the wrong train, so they need error-prevention nudges.
• They want trust signals (IRCTC logo, payment gateway reliability).
• They might want to compare seat classes visually, even if they don’t say it.

Unstated needs are often emotional, risk-related, or rooted in prior negative experiences. Good design anticipates these — even when users don’t explicitly voice them. These are often more valuable to understand, because they explain behavior—why people hesitate, abandon flows, or gravitate toward other products.

Surface vs. Depth

Not all needs come wrapped in clear language. Some sit on the surface. Others live deeper down. Surface needs are what readers say:

• “Add a search bar.”
• “I want dark mode.”
• “The button should be bigger.”

They’re direct and specific—but often symptoms, not root causes. Depth needs are what readers mean:

• “I feel lost.”
• “This strains my eyes.”
• “I’m not sure what to do next.”

The job of design is to hear the surface, but solve for the depth.

• Not just “dark mode,” but “comfort in dim light.”
• Not “make it bigger,” but “clarity and emphasis.”
• Not “add search,” but “ease of finding.”

How to Uncover Unstated Needs?

You don’t guess. You observe. You listen beyond the words.

• What steps do readers repeat?
• Where do they hesitate?
• What instructions do they ignore?
• Where do they look for reassurance?

You ask:

• “What made you pause here?”
• “What were you expecting when you tapped that?”
• “What felt confusing or uncertain?”

You map what they said against what they did. The gap is where unstated needs live. A reader says: “I wish there was a progress bar.” That’s the stated need. The unstated need might be “I feel anxious not knowing how long this will take.” or “I need assurance that I’m not stuck.”

A progress bar is a feature. The real need is clarity, momentum, and trust. Now the design brief shifts—from “add a bar” to "How might we reduce anxiety and make progress feel visible?"

Short-Term vs. Long-Term Needs

A reader opens a banking app to check their balance. They want one number. No tour, no upsell. Short-Term needs are urgent, task-driven, and context-specific needs related to:

• Accessing content
• Completing tasks
• Navigating steps
• Getting quick feedback
• And require clarity, speed, and minimal friction

Long-Term needs are emergent, relational, and reflective needs related to:

• Tracking progress
• Personalisation
• Building routine
• Memory and history
• Sustaining trust
• Require continuity, foresight, and meaningful feedback

A reader returns to a note-taking app every day. They want to find old ideas, link thoughts, and notice patterns. The design must support memory, not just input. Short-term needs shape first impressions. Long-term needs shape loyalty. Sometimes, they conflict. A pop-up may aid onboarding (short-term), but feel intrusive later (long-term). Hiding complexity eases entry, but may limit growth over time. And so, designers must ask

• “What does the reader need right now?”
• “What might they need after ten uses?”
• “How does today’s interaction build toward tomorrow’s experience?”

In Summary

• Stated needs describe friction.
• Unstated needs reveal intention.
• Surface needs demand attention.
• Depth needs demand insight.
• Short-term needs drive urgency.
• Long-term needs drive meaning.

Design listens to all—but solves for the deeper one. That’s how we move from problem-solving to meaning-making.

---