The Gap

I had a meeting where someone on the team told me my tagline was wrong.

Not wrong as in grammatically wrong or factually wrong. Wrong as in they didn’t like it. The product was a digital photo frame, a smart frame you could send pictures to from your phone so your parents or grandparents could see new photos of the kids without having to figure out how to use an iPad. And my tagline was: “Stay connected, even when you’re apart.”

The pushback wasn’t articulate. It wasn’t “this doesn’t match our brand positioning” or “our user research says otherwise.” It was more like a feeling. A shrug. The team couldn’t put their finger on what was wrong with it, but they knew they didn’t love it. Partly because they hadn’t thought of it. Partly because nobody on the team could come up with anything in the same league, which made the discomfort worse. Nobody likes being outwritten on their own product.

I recognized the dynamic from improv. One of the first things my teacher taught us: if you don’t come up with an idea you like and someone else does, you get a negative pull toward shooting it down. Not because of anything wrong with the idea. Because you didn’t think of it first, and that makes you feel something about yourself.

The fix is the same as every other social instinct we were learning to override in that class. Notice it, name it, choose yes-and instead of no-but.

I kept it anyway.

---

Campaigns with that tagline outperformed everything else the company ran. Not by a little. By enough that the conversation about whether it was the right tagline just stopped. The numbers ended the argument.

Two years later, Aura Frames, one of the biggest competitors in the space, started using nearly identical messaging. “Stay connected” language. The same emotional architecture. They didn’t arrive at it by coincidence. They arrived at it because it works, and when something works that well, competitors find it.

My rule of thumb: when your competitor steals your tagline, you found the emotional core.

That company, Simply Smart Home, went from $1.7M to $5M in annual revenue. 233% year-over-year growth. Disney licensing. Costco pallet placement. Walmart shelf space. The product didn’t change. It was the same hardware the whole time. Same screens, same app, same wood casing. What changed was the perception.

And the perception changed because I stopped telling people what the product did and started telling them what having the product would feel like.

---

This is Layer 3: Perception Bias Optimization, and it’s the most politically difficult principle in the entire framework. Because it means telling stakeholders that their instincts about their own customers may be wrong. Not their instincts about the product, not their instincts about the market. Their instincts about what their customers actually care about and why they buy.

A hard conversation to have. People identify with their products. They built the thing. They know the specs, the engineering trade-offs, the supply chain nightmares. And when someone walks in and says “none of that is what your customer cares about,” it feels dismissive. Even when it’s true.

The core insight comes from a 1977 study by Richard Nisbett and Timothy Wilson that should be required reading for anyone who designs anything. They demonstrated, across multiple experiments, that people are often completely unaware of what actually influenced their decisions. When asked to explain their choices, subjects generated plausible post-hoc rationalizations, stories that sounded reasonable but had nothing to do with the actual cause.

The subjects weren’t lying. They genuinely believed their explanations. They just didn’t have access to the real process.

---

Kahneman formalized this in Thinking, Fast and Slow (2011) with the System 1 / System 2 framework I introduced in Chapter 2. System 1 makes the decision. Fast, automatic, emotional, below the surface. System 2 constructs the explanation. Slow, deliberate, rational, satisfying to articulate.

This matters for design: survey data captures the System 2 rationalization. Analytics captures the System 1 decision. The gap between them is where perception problems hide.

Ask a customer why they bought a digital photo frame and they’ll tell you about the screen resolution, the app reviews, the price comparison they did. That’s the story. System 2 constructed it after the fact because humans need reasons for their behavior.

But the actual purchase decision, the moment they went from “maybe” to “yes,” happened in System 1. It happened because the brand made them feel something. Connected to their family. Less guilty about distance. Like a thoughtful gift-giver.

Ask a customer why they didn’t buy, and the gap gets even wider. “The price was too high.” “I wasn’t sure about the reviews.” “I’ll think about it.” All perfectly rational explanations. All System 2 reconstructions of a System 1 verdict that already fired: “This doesn’t feel right.”

Maybe the site looked cheap. Maybe the messaging was all specs and no soul. Maybe the product photos showed hardware instead of humans. The customer felt a perception barrier, bounced, and then constructed a reason that had nothing to do with what actually happened.

I’ve seen this on every project I’ve worked on. The stated reason and the actual reason almost never match.

---

The Simply Smart Home story is the clearest example I have, so let me tell it fully.

When I came on, the company was doing $1.7M in annual revenue. The product was functional, the price was competitive (for the category), and the team was working hard. But the presentation told a completely different story. The site was a template. The branding was scattered. The marketing was entirely feature-focused: screen resolution, WiFi connectivity, photo capacity, app compatibility.

Every layer of perception was failing. The site didn’t answer a visitor’s basic questions (cognitive load problem). No faces, no warmth, no emotional context in the imagery (first impression problem). A template site at a premium price point created a quality mismatch that screamed “knockoff” (processing fluency problem). Feature specs instead of emotional connection (perception bias problem). And the homepage was structured around the company’s org chart, not the customer’s goals (decision architecture problem).

But the perception bias problem, Layer 3, was doing the most damage. Because it infected everything upstream. The feature-focused messaging shaped the photography choices (product shots instead of lifestyle shots). The photography shaped the visual identity (cold, technical, sterile). The visual identity shaped the first impression (this feels like a $15 tablet, not a $150 smart home product). Each layer was failing partly because the perception bias at the messaging level was wrong.

The product was actually $20 to $35 worth of hardware in a wood casing, sold for $100 to $180. That’s not a criticism. That’s every consumer electronics product. The gap between hardware cost and retail price is called brand. It’s called perceived value. And perceived value isn’t a lie. It’s the emotional architecture that makes the price feel fair.

So I built one.

---

I created “smart home decor” as a category. Not “digital photo frame.” Not “WiFi-enabled picture display.” Smart home decor. A thing that belongs in your living room because it makes the room feel warmer, more connected, more like a home where people who love each other actually live.

That phrase repositioned the entire product. It wasn’t a gadget anymore. It was decor. It wasn’t competing with tablets. It was competing with the framed photos on your mantle, except these ones updated automatically when your daughter posted new pictures of the grandkids.

And the tagline, “Stay connected, even when you’re apart,” told you why you wanted it. Not what it did. Why you wanted it. Because you miss people. Because distance is hard. Because seeing a new photo of someone you love, appearing on a frame in your kitchen without you having to do anything, makes you feel closer to them.

Perception bias optimization. Finding the emotional core that drives the actual purchase decision, the System 1 decision, and making it the centerpiece of the brand. Instead of burying it under specs.

The team didn’t like it at first. That’s the politically difficult part. The people closest to the product are the least equipped to see it from the customer’s perspective, because they know too much. They know about the WiFi chip and the display resolution and the firmware update process. They think those things matter to the buyer because those things matter to them.

This is one of the hardest things I have to communicate to stakeholders: it’s not for you. It’s for them.

I’ve said those exact words. Looked someone in the eye and told them: this product isn’t for you. You’re not the customer. Your feelings about the messaging are real, but they’re not data about what your audience needs to hear.

---

There’s a famous comparison that illustrates this perfectly, and I use it in almost every client conversation.

The iPod and the Zune were the same product category. Both were portable music players. Both played MP3s. The Zune actually had some features the iPod didn’t, like wireless sharing between devices and a larger screen on certain models. From a pure feature comparison, the Zune was competitive. In some ways it was better.

The iPod won. Completely. Overwhelmingly. Not because of the hardware. Because of the perception architecture.

Apple’s marketing never told you what the iPod did. It told you what having an iPod made you feel. Freedom. Self-expression. Your entire music library in your pocket, available whenever you wanted it, wherever you were. The silhouette ads, the white earbuds as a cultural signifier, the integration with iTunes as a music discovery experience. Every touchpoint reinforced the same emotional message: this product is about who you are, not what it does.

Microsoft’s marketing for the Zune told you what it did. Screen size. Storage capacity. Sharing features. FM radio. All real features. All things that System 2 can evaluate and compare. And all completely irrelevant to the System 1 decision that was already made the moment someone saw a white earbud cord on a stranger in a coffee shop and felt something.

Same hardware category. Radically different perception architecture. One became a cultural icon. The other became a case study in how to lose.

The gap between what users say they want (features, specs, rational comparison) and what actually drives their behavior (feeling, identity, emotional resonance) is the gap. It’s the space where perception bias operates, invisible to everyone except the people paying attention.

---

Nisbett and Wilson’s 1977 finding plays out in a design context like this.

You run a user survey. You ask people what matters to them when choosing a product in your category. They tell you: price, features, reviews, reliability. All rational. All System 2. All true, in the sense that people genuinely believe these are the factors driving their decisions.

Then you look at your analytics. The highest-converting landing page has the fewest feature mentions and the strongest emotional hook. The product photo that drives the most clicks shows a person using the product, not the product alone. The email subject line with the highest open rate doesn’t mention a single spec. The customers who pay full price without waiting for a sale came in through channels that emphasized lifestyle, not value.

The survey says one thing. The data says another. The gap between them is where your actual design problem lives.

Most teams resolve this by trusting the survey. It’s explicit. It’s quotable. You can put it in a slide deck and say “customers told us they want X.” It feels like evidence because it comes from the customer’s own mouth.

But it’s not evidence of what they want. It’s evidence of what they think they want. And those are different things.

I’m not saying surveys are useless. They’re useful for what they actually measure: conscious rationalizations, stated preferences, articulated pain points. That data matters. But treating it as ground truth about purchase behavior is like asking someone why they married their spouse and taking the answer at face value. The real reasons are deeper, messier, and largely inaccessible to the person giving the explanation.

---

There’s a specific pattern I watch for that tells me a company has a Layer 3 problem. It shows up the same way every time.

Marketing focuses on features. The homepage leads with specs, capabilities, technical details. The assumption is that if people understand what the product does, they’ll buy it. But understanding and wanting are different processes. I can understand exactly what a product does and feel nothing.

Stakeholders love the design, but customers don’t buy. The team looks at the site and says “this is great, this represents us well.” And they’re right, it does represent them. It represents how the company sees itself. But the customer doesn’t care how the company sees itself. The customer cares how the product makes them feel. The design passes the internal test and fails the external one because the internal test is checking the wrong thing.

Copy describes what the product does, not why you’d want it. “WiFi-enabled digital photo frame with 10.1-inch display, 16GB storage, and free cloud service.” That’s a product description. It’s accurate. It’s also dead on arrival, because it activates System 2 (evaluation, comparison, deliberation) when it should be activating System 1 (feeling, desire, identity).

Nobody lies awake at night wishing they had a WiFi-enabled digital photo frame. People lie awake wishing they felt closer to the people they love.

When all three of these patterns show up together, I know the problem isn’t the product, the price, or the funnel. The problem is perception bias. The company is designing for what they know about the product instead of what the customer feels about the product. And the fix isn’t better features or lower prices. It’s better perception architecture.

---

The SSH story has a payoff that I think about a lot.

After the rebrand, after “stay connected, even when you’re apart,” after “smart home decor” as a category, after the emotional photography and the lifestyle-first marketing, the company went from $1.7M to $5M. 233% year-over-year. Disney wanted licensing deals. Costco gave them pallet placement. Walmart put them on shelves.

None of those retailers cared about the WiFi chip. They cared about perceived value. They cared that the brand told a story customers would respond to. They cared that the packaging looked like it belonged next to $200 products instead of next to $15 knockoffs.

The product was the same product. The engineering team didn’t redesign the hardware. The supply chain didn’t change. The price didn’t drop. What changed was the story, and the story changed what people were willing to pay, where they were willing to buy it, and which companies were willing to put it on their shelves.

I put enough lipstick on the pig that was Simply Smart Home to persuade enough people on the fence that it was worth the buy. I’m honest about that framing. The product was fine. Not remarkable. Fine. The perception architecture made it remarkable. And the people who were almost going to buy, the fence-sitters who needed one more reason to say yes, those people started buying. That’s the conversion impact of perception bias optimization. You’re not creating demand out of nothing. You’re removing the perception barriers that were blocking demand that already existed.

Perceived value meant more than anything else sales or marketing tried to do to increase sales. That’s a direct quote from my own notes. I don’t say things like that unless I mean them.

---

There’s a subtlety here that I want to name because it matters for how you apply this.

Perception bias optimization is not lying. It’s not inventing qualities the product doesn’t have. It’s not manipulating people into buying something they don’t want. It’s finding the true emotional value of the product and making it visible.

“Stay connected, even when you’re apart” is true. The digital frame does connect people across distance. That’s what it actually does, at the emotional level, for the person who uses it. I didn’t invent that value. I identified it. The product team was too close to the hardware to see it. They saw WiFi chips and screen resolutions. I saw a grandmother in Ohio looking at photos of her grandkids in California and feeling less alone.

The ethical line is clear to me: perception bias optimization means aligning the perception with the best true version of the product. Making the emotional reality visible. Not fabricating an emotional reality that doesn’t exist.

When the perception you build doesn’t match the experience, people find out. They always find out. And the trust damage is worse than if you’d never built the perception in the first place. Layer 3 only works when it’s grounded in something real.

---

I want to come back to the team resistance for a moment, because if you’re going to practice this, you need to be ready for it.

The people closest to the product will almost always push back on perception-first messaging. Not because they’re wrong about the product, but because they’re evaluating the messaging from the wrong perspective. They’re asking “does this accurately describe what we built?” when the right question is “does this make someone want what we built?”

Those are fundamentally different questions. The first is an accuracy check. The second is a desire check. And the answers are often in tension, because the things that make someone want a product (emotional connection, identity alignment, aspiration) are not the things that accurately describe it (specs, capabilities, technical details).

I’ve had this conversation dozens of times. The stakeholder says “but we need to mention the 16GB storage.” And I say “does your customer know what 16GB means in the context of photo storage?” They don’t. “Does your customer care?” They don’t. “What does your customer care about?” That their mom can see pictures of the grandkids.

The stakeholder knows this. At some level, they’ve always known it. But saying it out loud feels like a betrayal of the engineering effort. Like all those months of firmware development and hardware sourcing don’t matter. They do matter. They matter enormously, because without the engineering the product doesn’t work. But the engineering is the table stakes. It’s the foundation. The customer assumes it works. What the customer needs help with is wanting it.

The gap. What the team values and what the customer values are different things, and the team’s instinct is to communicate what they value. Perception bias optimization means having the discipline to communicate what the customer values instead.

---

One more thing about the SSH story that I think is underappreciated.

The revenue growth wasn’t a one-time spike from a campaign launch. It built over roughly two and a half years. Every year, the brand system got more refined. The photography got more emotionally resonant. The messaging got more precise. The seasonal palettes, the sub-brand mood boards for Disney and Brookstone and Costco co-branding, the collateral for sales teams, the packaging updates. All of it compounding.

Processing fluency isn’t a one-time fix. It’s brand infrastructure that compounds. And perception bias optimization sits right on top of it, benefiting from every improvement in visual consistency and brand coherence. Each year, the perceived quality matched the price point more precisely. Price objections decreased. Vendors got more interested. The flywheel spun faster.

$1.7M to $5M wasn’t a redesign payoff. It was a perception compound interest payoff. The redesign set the foundation, and the compounding did the rest.

---

So take this from the chapter.

Your customers are making decisions you can’t see, for reasons they can’t explain. The gap between what they tell you and what they actually do is not noise. It’s signal. It’s the most important signal in your data, and most teams ignore it because the survey results are easier to act on than the behavioral patterns.

Find the emotional core. Not the features, not the specs, not the technical differentiator. The feeling. What does someone feel after they use your product? What problem does it solve that they can’t articulate but absolutely feel? That’s your message. That’s your brand. That’s your entire perception architecture.

And be ready for the room to push back. Because the emotional core almost never sounds like what the team expects to hear. It sounds too simple. Too soft. Too far from the engineering. “Stay connected, even when you’re apart” doesn’t mention screens or apps or cloud storage. It mentions a human feeling. And human feelings are what drive human decisions.

It’s not for you. It’s for them.

Next: You Wouldn’t Vibe Code a Car, on why memes work, why video doesn’t, and what the credibility gap in AI-assisted development actually looks like.