# Basics ### **Basic User Needs** Once something works, users need to believe it works. Trust is the bridge between function and confidence. It transforms usability into reliability. It is not earned by saying the right things; it is proven through consistent design that behaves exactly as people expect. When trust is present, users feel safe acting. When it is missing, hesitation replaces flow, and every next step feels uncertain. ## **Why Trust Matters** Trust is what keeps users moving forward. Without it, even the most polished experiences feel fragile. A single broken promise or unpredictable behavior can erase confidence instantly. In the Glare stack, Trust sits right above Basics. Where Basics prove that a design works, Trust proves that it is dependable. It is how users decide whether to believe what they see, click what they do not yet know, or return after something goes wrong. Trust can disappear in a single moment of uncertainty. One broken confirmation, a delayed save, or a missing signal can undo months of reliability work. Users do not consciously measure trust. They feel it. Every clear message, consistent pattern, and honest signal adds to it. Every contradiction takes it away. When trust fails, momentum stops. A vague message, a security doubt, or one confusing interaction can ripple upward into lost engagement, credibility, and belief. Trust gives design its integrity. Without it, even good work looks uncertain. * * * ## **The Four Core Needs** The Basics form the groundwork of any good experience. They remove friction and make interaction feel natural, not something users have to think about. These four needs define what “working” really means in design: that every step, click, and choice feels effortless. Each one represents a principle of clarity and ease. Together, they shape the foundation that every other user need builds upon.

User Need	Guiding Question	Why It Matters	When It’s Working
Usable	Does it function clearly?	Design should make actions intuitive and feedback immediate.	Users complete tasks easily and know what happened next.
Useful	Does it solve the right problem?	Even the most polished flow fails if it’s solving the wrong thing.	The product feels necessary — not optional — because it meets a real need.
Findable	Can users locate what they need?	If people can’t find information, the experience breaks before it begins.	Users move confidently through the interface without hesitation or confusion.
Accessible	Can everyone use it?	Accessibility ensures that people of all abilities can perceive and operate what’s designed.	Everyone can participate — nothing feels off-limits or hidden.

When these four needs are met, design becomes invisible. It just works. Users stop thinking about how to use it and start focusing on why they’re using it. * * * ## **How Basics Fit the Stack** In the User Needs hierarchy, Basics build the ground layer of confidence. They align with the Measure → Usefulness facet of Glare, where behavior and performance metrics prove that design functions.

Level	Question	Design Focus	Common Metrics	Facet
Basics	“Can I use it easily?”	Flow, clarity, access	Task completion, error rate, time on task	Measure
Trust	“Do I believe it works?”	Predictability, consistency	Credibility, bounce rate	Define
Personal	“Does it fit my needs?”	Relevance, inclusion	Adaptability, comprehension	Define + Focus
Impact	“Does it make a difference?”	Efficiency, results	Conversion, retention	Show
Feelings	“Does it inspire me?”	Emotion, motivation	Sentiment, preference	Focus

Good design starts here. When the Basics are strong, everything above them has something solid to stand on. ### **From Basics to Belief** When Basics are solid, everything else becomes possible. They build the measurable foundation for credibility, personalization, and delight. Teams that test and prove the Basics consistently move faster because they fix the right problems first. The moment a product “just works” is when users start trusting it, even before they can say why. * * * ## **How to Apply Basics in Practice** 1. Test your flows early. Don’t polish, prove. Watch where users struggle. 2. Measure completion and clarity. If people hesitate, the design isn’t ready. 3. Map the friction. Track every point of confusion, delay, or error. 4. Design for access. Meet WCAG standards and go beyond compliance — aim for inclusion. 5. Repeat after refinement. Usability isn’t a one-time check; it’s a continuous signal. Confidence in design begins when the basics work. Every next step has proof beneath it. ## **Checklist for the Basics**

Step	Action	Outcome
1	Identify core user tasks	Define what “working” means
2	Test usability on key flows	Reveal friction early
3	Validate usefulness	Confirm you’re solving the right problem
4	Measure findability	Track how easily users locate key info
5	Check accessibility	Ensure everyone can use it
6	Review post-launch	Monitor signals over time

Strength in Basics turns design from guesswork into evidence. Every improvement and every user’s confidence starts here.