Avatar or Logo

The Emotional Prototype

Work

Why we should design for feelings first, functions second?

—

The Backwards Product Development I Keep Seeing

Every product meeting starts the same way: features, specs, user flows, technical requirements.

Then someone asks: "But how should it feel?"

And everyone stares blankly because they've already committed to building a feature factory instead of an emotion engine.

The result: Products that work perfectly and feel like nothing.

The Feeling-First Winners

iPhone (2007): Technically inferior to BlackBerry. Slower network. Worse battery. Fewer features.
The feeling: Desire. Pure, physical want. You touched that screen and immediately understood the future was in your palm.

Instagram: Terrible photo quality compared to actual cameras. Limited editing. Forced square crops.
The feeling: Instant transformation. Your boring lunch became art. Your mediocre life became curated perfection.

Tesla: Overpriced. Unreliable charging. Manufacturing issues for years.
The feeling: You're driving tomorrow. Every gas station you pass is a relic.

None of these won on specs. They won on emotional jobs.

The Emotional Jobs Framework

People don’t hire products to do functional tasks. They hire them to feel different.

  • Spotify’s real job: Not “play music.” Make me feel like the protagonist of my own soundtrack.

  • Notion’s real job: Not “organize information.” Make me feel like my chaotic thoughts are finally under control.

  • Discord’s real job: Not “chat with friends.” Make me feel like I belong somewhere.

  • Figma’s real job: Not “design software.” Make me feel like my ideas can become real without technical barriers.

The function is just the delivery mechanism for the feeling.

Why We Design Backwards

Corporate design process:

  1. Define user requirements

  2. Map user journey

  3. Design features

  4. Add “delight” at the end

Result: Functional products with emotional sprinkles on top.

Human reality:

  1. Feel something

  2. Rationalize why you need it

  3. Use features to justify the feeling

  4. Tell stories about functionality to mask emotional decisions

We buy with emotion, then defend with logic. But we design with logic and hope emotion happens.

The Neuroscience Doesn’t Lie

Emotional response happens in 0.5 seconds.
Rational evaluation takes 2–3 seconds.

By the time someone thinks about your product, they’ve already felt about it.

Case study: Dating apps

  • Tinder: Swipe = instant yes/no feeling. No profiles to read first.

  • eHarmony: 29-dimension compatibility questionnaire first.

Guess which one changed dating culture?

Web3 example:

  • OpenSea: Functional NFT marketplace. Works fine. Feels like eBay.

  • Foundation: Invitation-only, curated, mysterious. Same functionality. Feels exclusive.

Foundation commanded 10x higher prices for identical technical capability.

The Corporate Emotion Allergy

  • What companies say: “We’re data-driven.”
    What they mean: Emotions are unpredictable and unmeasurable, so we’ll ignore them.

  • What companies say: “User-centered design.”
    What they mean: We’ll ask users what they want, not what they feel.

  • What companies say: “Let’s A/B test the emotional response.”
    What they mean: We’ll reduce complex human emotions to click-through rates.

You can’t survey your way to emotional truth. You can’t spreadsheet your way to desire.

The Prototype-to-Feeling Process

Instead of wireframing features, prototype feelings.

  1. Name the target emotion
    Not “easy to use.” That’s not an emotion.
    Try: Effortless mastery. Quiet confidence. Productive flow.

  2. Find existing emotion triggers
    What already makes people feel this way? Movies, spaces, sounds, objects.
    Study those, not competitor products.

  3. Build the minimum viable feeling
    Before any features work, the emotion should be present.
    Figma felt collaborative before real-time editing worked.
    Stripe felt trustworthy before the payments were reliable.

  4. Reverse-engineer the features
    What functionality would serve this feeling?
    Not: “What features do users need?”
    But: “What features would sustain this emotional experience?”

The Anti-Pattern: Feature Creep as Emotion Dilution

Every feature added dilutes the core emotion.

  • Snapchat’s emotion: Ephemeral authenticity.
    Then they added: Stories (permanent), Discover (professional content), Snap Map (surveillance).
    Core emotion got muddied. User growth stalled.

  • Instagram’s emotion: Instant aesthetic transformation.
    Then they added: Shopping, Reels, IGTV, messaging, live video.
    Original feeling lost in feature bloat.

The rule: If a feature doesn’t amplify the core emotion, it’s probably destroying it.

The Feeling-First Roadmap

Traditional product roadmap:

  • Q1: User authentication

  • Q2: Core features

  • Q3: Advanced features

  • Q4: Polish and delight

Emotion-first roadmap:

  • Q1: Nail the core feeling with minimal features

  • Q2: Amplify that feeling

  • Q3: Remove anything that dilutes the feeling

  • Q4: Scale the feeling to more contexts

Real example from a project I worked on:
Traditional approach would have built full functionality first.
Instead, we prototyped just the moment of “creative breakthrough” — the feeling when an idea clicks.
Built entire product around amplifying that 2-second emotional peak.
Result: Higher engagement than feature-complete competitors.

The Measurement Problem

You can’t A/B test an emotion, but you can recognize it:

  • Do people talk about your product differently?

  • Do they use emotional language in reviews?

  • Do they share it without being asked?

  • Do they defend it irrationally?

  • Do they keep using it even when competitors have better features?

Tesla owners defend panel gaps and delivery delays.
iPhone users upgrade annually for minimal feature improvements.
Notion users evangelize it like a religion.

That’s emotional loyalty, not functional satisfaction.

The Web3 Emotional Gap

Most Web3 products lead with technology: “Decentralized,” “Trustless,” “Permissionless.”

The emotions people actually want from Web3:

  • Sovereignty (control over digital identity)

  • Belonging (finding your tribe)

  • Status (early adopter credibility)

  • Rebellion (fuck the system)

Products that nail Web3 emotions:

  • ENS domains: Digital identity ownership feels like claiming territory

  • Friend.tech: Social speculation feels like insider trading

  • Zora: NFT creation feels like artistic liberation

The successful ones prototype the feeling first, implement the blockchain second.

The Corporate Rebellion

Standard corporate advice: “Follow user research. Build what users ask for.”

Emotional reality: Users don’t know what they feel. They definitely don’t know what they could feel.

  • No one asked for the iPhone. They asked for “better keyboards” and “longer battery life.”

  • No one asked for Instagram. They asked for “better photo editing.”

  • No one asked for TikTok. They asked for “cleaner video sharing.”

The breakthrough products give people feelings they didn’t know they wanted.

The Choice

You can build products that work.
Or you can build products that make people feel something.

The first approach gets you steady, forgettable growth.
The second approach gets you cultural impact and irrational loyalty.

Most companies optimize for functionality because it’s measurable.
But humans optimize for emotions because that’s how we’re built.

The Insight

Emotional response precedes rational evaluation in all meaningful user experiences.
Design for the feeling first, then build features to deliver that feeling consistently.

Note: Written with AI assistance, edited with human judgment, published with zero apologies.