Feeling-First Product Metaphor
Pick the feeling, name where you last felt it, and let the metaphor make a thousand small decisions for you.
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 6
- Confidence
- 90%
Rather than specifying what a product should do, Vora specifies what it should feel like, anchors that feeling to a concrete lived scene, and lets the team derive design decisions from the scene. A shared story replaces a decision queue: once everyone agrees the product should feel like sitting in Dolores Park with friends on a sunny Saturday, designers know the iconography, engineers know the interaction weight, and nobody has to escalate.
Origin
Vora learned this from her former manager Eric Antonow, whom she describes as a master of metaphor and analogy. His two-question drill — how is this product going to make you feel, and when is the last time you felt that way — is the generative core of the framework.
Core principles
- 01As a team scales, narrative carries more weight than instruction.
- 02You can either tell everyone exactly what to do at every point, or create a story everyone agrees on — the story scales, the instructions don't.
- 03A feeling is more portable across functions than a spec: design, engineering and copy can all decode the same scene.
- 04The metaphor prunes the design space by exclusion as much as by inclusion — you know what you will not build.
- 05Small interaction details are how the feeling actually gets delivered.
How to run it
- 1
Ask how the product should make people feel
Before discussing features, get an answer to the feeling question. Force a human emotional word, not a product attribute.
Watch out Do not accept 'fast', 'simple' or 'delightful'. Those are attributes, not feelings, and they generate no imagery.
- 2
Ask when they last felt that way
Convert the feeling into a specific lived scene — a place, a time, people. 'Hanging with my friends in Dolores Park.' 'Sitting around the family room.' 'Talking to someone face to face.'
Pro tip Specificity is the whole asset. A vague scene generates vague products.
- 3
Interrogate the ramifications
Ask what it feels like and why, and what follows from that. Walk the scene's properties out into product properties.
Pro tip Antonow's follow-up: 'cool — tell me what it feels like, why that's the analogy, what ramifications come out of that.'
- 4
Get explicit agreement on the story
Ratify the metaphor as a team artefact. It only substitutes for decisions if everyone has bought into the same story.
- 5
Let the team derive decisions from the scene
Stop making individual calls. Designers derive iconography, engineers derive interaction weight, PMs derive the join pattern — all from the scene. The output is consistent because the source is shared.
Pro tip Use the negative space too: a Dolores Park product is not cold and corporate, not strobe-lighty, not flashy. The scene rules things out for free.
- 6
Ship the feeling in the small details
Audit the micro-interactions against the scene. That is where the feeling actually lands.
In the wild
WhatsApp's goal was to connect people to those they cared about most, across high-end Western devices and low-end phones belonging to first-time internet users alike. The team landed on face-to-face conversation as the metaphor: when you talk to someone face to face, you don't think about how to present or what tool to learn — you open your mouth and words come out. The app then had to step back and create spaces that felt intimate: the kitchen table, the living room, the one-on-one banter with disappearing messages.
→ The metaphor produced the details — the typing indicator as someone drawing breath before speaking, the two check marks as a face lighting up when it hears you. Small things that add up to a feeling of being there.
For WhatsApp video calls, the metaphor was sitting around in your family room. In a family room you don't schedule; there's no cold, heavyweight, corporate conference-call ritual. The space exists whether or not you're in it, and people drift in and out.
→ The team built joinable calls — lightweight, no heavyweight action required from everyone, people popping in and out while the call flows on. They agreed on the feeling and then knew what to build.
Common mistakes
Adjudicating every decision yourself
The alternative to a shared story is telling everybody exactly what to do at every point. That doesn't scale, and the output ends up inconsistent anyway because your rulings drift.
Choosing a metaphor nobody has actually lived
The framework runs on recalled sensory experience. An abstract or aspirational metaphor generates no iconography, no interaction weight and no exclusions.
Is it for you?
Best for
Product and design leaders trying to align a scaling, cross-functional team on a coherent product feel without becoming the decision bottleneck.
Not ideal for
Purely technical or infrastructure work where the user-facing feeling is not the constraint, and highly regulated surfaces where compliance dictates the interaction.
From the transcript
“the prct metaphor we kind of arrived at for WhatsApp was face-to-face communication”
“either you can tell everybody exactly what to do at every point or you can create a story that we all agree on and when…”
“you're not going to build something cold and corporate you're not going to build something strob Lighty you're not going to build something flashy but…”
“it's like a typing indicator is like someone who's about to take a breath give them SP to talk”
From the episode
Making an impact through authenticity and curiosity
Ami Vora (CPO at Faire, ex-WhatsApp, FB, IG)