Cognitive and Emotional Design

Mental Model Alignment Framework

Use when: designing navigation, workflows, or any interaction where users bring expectations from elsewhere.

Users expect your product to behave like similar products they've used before. A trash/delete icon should be recoverable. Swiping right should mean "accept" or "advance." A red button should mean danger or stop. You can break these conventions — but only when you provide a clearly better alternative, and only with adequate signaling. The cost of violating a mental model is always higher than designers estimate, because the frustration is invisible in mockups and only emerges during real use.

Three Types of Cognitive Load Framework

Use this to diagnose why an interface feels overwhelming or confusing.

Affect-Cognition-Emotion Chain Framework

Use when: diagnosing why users respond unexpectedly to your interface, or designing for emotionally complex scenarios.

Negative affect narrows focus: users become more task-oriented, more suspicious, less receptive to suggestions. Positive affect broadens receptivity: users explore more, tolerate more friction, and are more open to upsells or new features. The design implication is that you must accommodate both states simultaneously. A tax filing tool should provide a streamlined, no-nonsense path for the stressed user filing at deadline (negative affect) and a more exploratory, suggestion-rich experience for the user filing months early (positive affect). The same interface, two emotional contexts — and both need to work.

Mood Meter Research Tool

Use when: you need a more precise vocabulary for describing user emotions than "happy" or "frustrated."

Marc Brackett's mood meter maps emotions along two dimensions: pleasantness (how good or bad) and energy (how activated or calm). This produces four quadrants: high-energy pleasant (excited, inspired), low-energy pleasant (calm, content), high-energy unpleasant (anxious, angry), and low-energy unpleasant (bored, sad). Designers typically think in binary (happy/unhappy) but users experience granular states. A checkout flow that produces "calm confidence" is different from one that produces "excited anticipation" — both are positive, but they call for different visual treatment, different copy tone, and different pacing.

Priming Bias

Use when: selecting imagery, choosing microcopy, or designing onboarding sequences that set expectations.

Exposure to one stimulus influences the response to a later stimulus, without conscious awareness. In a break-room experiment (Bateson, Nettle, and Roberts), placing an image of watching eyes near an honor-system payment box significantly increased contributions compared to a neutral image — people behaved more honestly when primed with the feeling of being observed. For design: the images, words, and tones users encounter early in a flow shape how they interpret everything that follows. A financial services site with images of families and homes primes trust and security; generic stock photography of handshakes primes nothing. Use associative imagery intentionally — especially in trust-sensitive industries where the wrong prime creates suspicion rather than confidence.

Anchoring Bias

Use when: designing pricing pages, comparison tables, or any choice architecture.

The first piece of information a user sees disproportionately influences their judgment. Show a $99/month plan first, and $49/month feels like a bargain. Show the $49 plan first, and it feels expensive on its own. Anchor users to the reference point that best supports their decision-making — the "most popular" plan badge, the original price before a discount, the competitor's price.

Peak-End Rule Bias

Use when: designing any multi-step experience or flow.

People judge an experience primarily by its most intense moment (the peak) and its final moment (the end), not by the average. A difficult checkout is forgiven if the confirmation page is delightful. A smooth onboarding is forgotten if the first real-use session is confusing. Design your peaks (moments of delight or accomplishment) and your endings (confirmation screens, exit moments) with extra care.

Serial Position Effect Bias

Use when: ordering lists, menus, or navigation items.

People remember the first items (primacy effect) and last items (recency effect) in a list better than the middle. Put the most important navigation items first and last. Put the action you most want users to take at the beginning or end of a list, never buried in the middle.

Framing Effect Bias

Use when: writing any user-facing copy, especially around risk or loss.

"90% success rate" and "10% failure rate" convey identical information but produce different responses. Frame outcomes positively when encouraging action ("Save 2 hours per week") and frame losses when discouraging inaction ("You're losing 2 hours per week"). Be ethical: framing should help users make better decisions, not trick them into worse ones.

Choice Overload Bias

Use when: designing any screen with multiple options — settings, product listings, filter panels.

More options feel better in theory but perform worse in practice. The jam study: 24 jam varieties attracted more browsers but 6 varieties produced 10× more purchases. Apply this to feature settings, plan selection, product catalogs. When you can't reduce options, provide defaults, recommendations, and progressive filtering. "Most popular" and "Recommended" labels are choice-reducing tools.

Visceral, Behavioral, Reflective Framework

Use this to evaluate or design the emotional impact of your product at three levels.

Visceral (immediate reaction): How does it look and feel at first glance? This is pre-conscious — before any interaction. Clean typography, harmonious colors, quality imagery, and appropriate whitespace create positive visceral responses. Cluttered, low-contrast, or amateur-looking interfaces create negative ones. First impressions form in 50ms.

Behavioral (during use): How does it feel to use? Is it efficient, predictable, and responsive? This is where usability lives. A beautiful interface that's confusing to navigate fails at the behavioral level. Success here means tasks feel effortless and the system responds as expected.

Reflective (after use): How do users feel about the product when they're not using it? Do they recommend it? Does it align with their self-image? This is where brand loyalty, word-of-mouth, and long-term satisfaction live. Reflective design shapes how users think about your product in the context of their identity and values.

Delight Framework Framework

Use when: evaluating or designing moments of positive surprise in your product, or when stakeholders ask for "delight" without defining it.

Delight is not decoration — it's a layered design quality that maps directly to Norman's three levels. Visceral delight is sensory pleasure: a satisfying animation when a task completes, a pleasing sound on success, a beautiful empty state illustration. It's immediate and universal but shallow — it fades with familiarity. Behavioral delight is the pleasure of something working better than expected: autocomplete that predicts what you need, a form that remembers your preferences, a flow that takes three steps instead of ten. This is durable delight — it compounds with use. Reflective delight is meaning and identity: a product that makes you feel competent, a feature that shows the team cares about details you care about, an experience that aligns with your values. This is the deepest form of delight and the hardest to design. The practical test: visceral delight earns first impressions, behavioral delight earns daily use, reflective delight earns recommendations. Most products over-invest in visceral (polish the surface) and under-invest in behavioral (make the workflows genuinely better).

Hierarchy of User Needs Framework

Use when: prioritizing design effort, or pushing back on stakeholders who want "delight" before the basics work.

Adapted from Maslow by Aarron Walter: a product must satisfy needs in order — functionality, then reliability, then usability, then pleasure. You cannot achieve any level of delight if the lower layers are broken. A delightful animation on a form that crashes is not delightful. A playful mascot on a site that takes eight seconds to load is not playful. The hierarchy is a prioritization tool: fix functional gaps before reliability issues, fix reliability before usability, and only invest in pleasure once the other three are solid. This doesn't mean pleasure is unimportant — it means it has prerequisites.

Surface Delight vs. Deep Delight Framework

Use when: distinguishing between polish and genuine experience quality.

Surface delight is local and contextual — a positive feeling derived from isolated interface features: animations, tactile transitions, microcopy, beautiful imagery, sound interactions. It's effective for first impressions but fades with repetition. Deep delight is holistic — a positive feeling that emerges once all user needs are met and the overall experience is exceptional. It comes from streamlined workflows, eliminated pain points, and an experience that consistently exceeds expectations. Surface delight without deep delight is decoration. Deep delight without surface delight is functional but forgettable. The strongest products layer both — but if forced to choose, invest in deep delight first. A confetti animation doesn't compensate for a broken workflow.

Aesthetics of Joy Framework

Use when: making visual design decisions about color, shape, imagery, and layout — especially when the brand permits warmth.

Ingrid Fetell Lee identifies ten aesthetic categories that reliably trigger positive emotional responses because they're linked to evolutionary signals of safety, abundance, and belonging: Energy (vibrant color, warm light), Abundance (lushness, variety, multiplicity), Freedom (nature, open space, wildness), Harmony (balance, symmetry, parallel lines, flat-lay photography), Play (circles, spheres, rounded edges), Surprise (contrast, whimsy), Transcendence (elevation, lightness), Magic (iridescent colors, reflective patterns), Celebration (sparkle, bursting shapes), and Renewal (blossoming, expansion, curves). These categories are a practical vocabulary for art direction — they explain why specific visual choices feel joyful and give designers language to discuss aesthetic decisions beyond "I like it."

Gamification Core Drives Framework

Use when: designing for sustained engagement, motivation systems, or when considering points/badges/leaderboards.

Yu-kai Chou's Octalysis framework identifies eight core motivational drives behind why people engage with game-like systems: meaning and calling (contributing to something larger), accomplishment (challenge and mastery), empowerment (creative expression and feedback), ownership (accumulation and customization), social influence (mentorship, competition, envy), scarcity (exclusivity and impatience), unpredictability (curiosity and chance), and avoidance (loss aversion and urgency). Simply adding points, badges, and leaderboards (PBLs) doesn't create engagement — those are surface mechanics. The drives behind them are what matter. A fitness app that taps accomplishment and social influence sustains engagement; one that only awards badges loses users once the novelty fades. Powerful in self-improvement contexts (health, finance, education); apply within ethical bounds.

Disposition to Trust Framework

Use when: understanding why conversion strategies work differently across user segments.

Users arrive with varying dispositions to trust, shaped by personality, culture, life experience, and socialization. Trusters hold an optimistic worldview — they believe people are generally good and things are within their control. Mistrusters are pessimistic — they believe people cannot be trusted and outcomes are beyond their control. The design implication: mistrusters rarely change their baseline disposition, so your trust-building efforts will disproportionately benefit trusters. This is not a reason to ignore trust design — it's a reason to focus it. Optimize for the trusters who can be won over, and make sure you don't actively trigger the mistrusters' suspicions with sloppy credibility signals or aggressive data requests.

Experiential Commitment Levels Framework

Use when: designing onboarding, progressive disclosure of data requests, or any funnel where trust must build over time.

Users move through five levels of trust commitment: (1) no trust established, (2) baseline relevance — trust that basic needs can be met, (3) interest and preference over alternatives, (4) willingness to share personal information, (5) trust with sensitive or financial data and commitment to an ongoing relationship. The designer's goal is to demonstrate credibility and benevolence at each level so users graduate naturally to the next. The critical mistake: asking for level-5 commitment (credit card, personal data) when you've only established level-2 trust (they just arrived). Don't ask for too much too soon. Pace requests to match the trust you've earned.

Cognitive Ease for Credibility Technique

Use when: designing content layout, typography, and information hierarchy — especially for landing pages and product pages.

Kahneman's research shows that cognitive ease breeds trust: when information is easy to process, people are more likely to believe it, trust their intuitions, and feel the situation is familiar. Cognitive strain produces the opposite — vigilance, suspicion, and effortful scrutiny. For credibility: clearly state what your company does (tagline + navigation categories should resolve ambiguity immediately), immediately address the user's primary questions ("Will this fit my needs?"), maximize legibility (bold or medium type, avoid fine print and low contrast — users interpret hard-to-read text as something you're trying to hide), avoid unnecessarily complex language (pretentious vocabulary is interpreted as a sign of low intelligence and low credibility), and use progressive disclosure to start simple and reveal details on request.

Meaningful Imagery for Trust Technique

Use when: selecting photography and illustrations for any commercial or trust-sensitive context.

Visual first impressions disproportionately shape credibility — one study found that users who rated a site highly for visual appeal continued to rate it favorably even after failing more than half the usability tasks (Lindgaard et al., 2006). Use images that accurately represent what you do or sell. For e-commerce, show products in context with demos and tutorials for utilitarian products, and products in lifestyle settings for hedonic products. For nonprofits, illustrate the problem you solve. For B2B, show your team or your product in action. Avoid generic stock photography — it primes nothing and signals that you didn't invest in genuine representation.

Transparency and Kindness Signals Technique

Use when: designing pricing pages, checkout flows, data collection forms, or any moment where users must decide whether to trust you with something.

Benevolence means putting the user's interests visibly first. Make prices visible by default — even in B2B, show pricing for common scenarios. Check for interactions that might trigger suspicion (a price that changes between product page and cart destroys trust instantly). Show shipping, return, and support policies prominently on product pages and in the cart, not buried in a footer link. When you need personal information, explain why you need it and what you'll do with it. The user's internal question is always "are they looking out for me, or for themselves?" Every design decision either answers that question favorably or unfavorably.

Humor in Microcopy Technique

Use when: writing helper text, placeholder text, error messages, or empty states — and your brand permits warmth.

Humor humanizes a brand and builds benevolence — it signals that a real person, not a machine, is behind the interface. Microcopy is a safe place to try it: helper text, placeholder text, error messages, loading states. But humor has strict guardrails. It must not detract from clarity or usefulness. It must never appear during critical moments (payment failures, data loss, account problems). It must never be at the user's expense — if it's rude to say in person, it's rude to say in copy. And bad humor erodes trust faster than no humor at all. Test the truth, pain, and distance: remove the joke — is the underlying statement still appropriate? Is the pain distant enough to laugh about? Know your audience's mood and cultural context.

Prominence-Interpretation Theory Framework

Use when: evaluating which elements on a page actually affect trust, rather than which ones users claim affect trust.

BJ Fogg's theory states that credibility impact = prominence × interpretation. Prominence is the likelihood that an element is noticed during a credibility evaluation. Interpretation is the value (positive or negative) that users assign to the element. An element that's highly prominent but interpreted negatively (a conspicuous stock photo) hurts more than a positive element that's invisible (a privacy badge buried in the footer). To test prominence, use five-second screenshot testing: show users a page for five seconds, then ask what they noticed. The elements they recall are the ones shaping their trust judgment — and they may not be the ones you intended.

Trust Signals Core Method

Use when: designing any experience where users provide personal data, make payments, or take irreversible actions.

Competence signals: Professional visual design, error-free copy, fast performance, working features. Every bug, typo, or broken link erodes trust. Transparency signals: Clear pricing, visible privacy policies, honest progress indicators, upfront about limitations. Social proof: Reviews, testimonials, user counts, recognizable logos. Control signals: Undo capabilities, confirmation dialogs for destructive actions, clear cancellation processes, data export options. Trust is built incrementally and destroyed instantly — one dark pattern can undo months of trust-building.

Trust as Design Quality for AI Framework

Use when: designing AI-powered features where users need to develop appropriate trust in system outputs.

AI features introduce a new trust challenge: users must calibrate trust in a system that is sometimes right and sometimes wrong, with no reliable external signal for which is which. Trust in AI is a design quality built through four properties. Transparency: Users can see that AI is involved, understand what data it uses, and see when it's less certain — ranging from simple "AI-generated" labels to detailed reasoning chains. Control: Users can steer, correct, undo, or override AI behavior — the granularity of control should match the stakes of the decision. Consistency: The AI behaves predictably across similar situations — inconsistency erodes trust faster than occasional errors because users can't build a mental model of the system. Failure support: When the AI gets it wrong, the system identifies the failure clearly, provides easy correction paths, and visibly improves over time. These four qualities are mutually reinforcing: transparency without control feels like surveillance, control without transparency feels arbitrary, and none of it matters without graceful failure handling.

Trust Observation Protocol Core Method

Use when: evaluating how trustworthy your product feels to real users — especially before launching trust-sensitive features.

Do not measure trust by asking users about trust. Three common methods produce unreliable results: (1) guided surveys where users rate the importance of trust attributes inflate every attribute (a Lumsden study found guided responses rated all attributes significantly higher than unguided ones), (2) side-by-side credibility comparisons where users name what influenced them fail because people don't know what actually influences them (Fogg, 2002), and (3) self-reported "rate the importance" surveys produce socially desirable answers rather than honest ones. Instead, measure trust through behavior: observe users performing specific, goal-oriented tasks. Watch, listen, and ask open-ended questions without addressing credibility specifically. Conduct follow-up surveys after tasks (SEQ for ease, plus a confidence question). Watch for trust signals in body language, hesitation, and expressed comfort level. Use analytics to identify where users abandon trust-sensitive flows. Metrics tell you what happened; observation tells you why.

Perspective-Getting Technique

Use when: building empathy skills for user research, or when "put yourself in the user's shoes" advice isn't producing real insight.

Perspective-taking (imagining you're in someone's shoes) is less effective than most designers assume. Research shows that imagining others' experiences produces inaccurate predictions about their wants and reactions. Perspective-getting — actually talking to people to gather their insights — is reliably more accurate. For designers, this means user interviews, contextual inquiry, and usability testing are not optional supplements to empathy; they are the mechanism by which empathy becomes functional. You cannot design for emotions you've never observed. Practice empathy skills outside of research settings: work on self-awareness and self-regulation, talk to people outside your normal social circles, and pay attention to context and body language without judging what you observe.