The Feeling of Truth

Say a sentence out loud. Any sentence. “The capital of France is Paris.” Now say it again. Notice how it feels more true the second time? Not because you verified it. Not because you learned something new. It just sits easier. The words land smoother. The thing that was already true somehow feels more true.

That’s processing fluency. And it is, quietly, one of the most powerful forces in design.

Reber and Schwarz ran an experiment in 1999 that should have changed every design brief written since. They presented identical trivia statements in two different fonts: one easy to read, one harder. The easy-to-read statements were judged as more true. Not more readable. Not more pleasant. More true. The content was the same. The font changed how the brain evaluated it.

Think about what that means. The truthfulness of a statement, something we experience as a property of the statement itself, is influenced by the visual presentation. Your brain doesn’t separate “this is easy to read” from “this is probably accurate.” It can’t. The feeling of ease bleeds into the feeling of truth, and the user never notices the transfer happening.

---

Alter and Oppenheimer expanded this in 2009 and found it wasn’t just about truth. Processing fluency generalizes. Easy-to-process information is judged as more true, more likable, more trustworthy, and more confident. Hard-to-process information gets the opposite treatment across the board. The brain uses processing ease as a heuristic for everything from aesthetic preference to risk assessment. If it flows, it’s good. If it stutters, something’s wrong.

Dechene and colleagues confirmed the illusory truth effect in a 2010 meta-analysis across 51 studies. Repeated exposure to statements increases their perceived truth, and the proposed mechanism is processing fluency: the second time you encounter something, it processes more smoothly, and the brain reads that smoothness as a signal of accuracy. This is why brand consistency compounds. Every time someone encounters your visual system and it matches what they saw before, the fluency goes up. The trust goes up. The “feels right” goes up.

This isn’t optional. It’s not a nice-to-have. It’s the architecture of how people evaluate whether something deserves their attention and their money.

Try this. Pick any page on your website and squint until the text blurs out. What do you see? If everything looks equally important, nothing is. If blocks of text crowd each other with no breathing room, the brain has to work to parse the hierarchy, and that work costs fluency. Every pixel of unclear hierarchy is a tiny withdrawal from the trust account.

Now think about your users who are over 40. Can they read your light grey text on a white background? If the answer is no, if basic visual processing fails at the level of individual characters, then nothing above it works. The user can’t evaluate your value proposition if they can’t decode the sentence. Processing fluency starts at the grapheme level. If the letters themselves are a struggle, you’ve already lost.

---

I learned this the slow way, over four years, with a brand called Simply Smart Home.

When I started working with SSH in 2020, there was no brand system. I don’t mean the brand system was weak. I mean it didn’t exist. Every piece of marketing collateral was built from scratch, each one with slightly different fonts, slightly different colors, slightly different layouts. The Amazon listings looked different from the website. The website looked different from the packaging. The packaging looked different from the social media. It was all the same company, selling the same products, and none of it felt like it belonged together.

The products were good. Digital photo frames, smart home devices, thoughtful tech for families. Price point was $100 to $180. But the presentation said $15 knockoff. Template website. Stock photography. Feature-spec copy. Nothing that said “this is a premium product made by people who care about design.”

The gap between product quality and perceived quality was enormous. And that gap was costing them everything.

---

Processing fluency isn’t something you fix with a weekend redesign. It’s infrastructure. It’s the systematic work of making every touchpoint feel like it belongs to the same family, so the brain never has to work to reconcile conflicting signals.

Year one was triage. I built the first real style guide: two typefaces (not five), a primary color palette (not whatever looked good that day), and templates for the most common collateral. The Amazon listing images alone had been produced by at least three different designers with three different aesthetic vocabularies. A customer who saw the product on Amazon, then visited the website, then opened the packaging was encountering what felt like three different companies. Each transition was a fluency violation. Each violation was an erosion of trust.

It wasn’t exciting work. It was the typography equivalent of pouring a foundation. Nobody photographs foundations. But nothing stands without one.

Year two, I started building the seasonal creative system. SSH sold gift-oriented products, which meant their visual identity had to flex across Valentine’s Day, Mother’s Day, Father’s Day, Christmas, and everything in between. Without a brand system, each season’s creative was a reset. New designer, new look, new everything. The Valentine’s Day campaign looked like it came from a different company than the Christmas campaign. With a system in place, each season became a variation on a theme. Same typography. Same layout grid. Different color palette, different photography mood, but always recognizably SSH.

By year three, the brand system was mature enough to support sub-brands. ClicSmart, the smart home security line. myLuma, the digital frame line. Disney-licensed products that had to live inside Disney’s brand guidelines and SSH’s simultaneously. Brookstone partnership products with their own visual constraints. Each sub-brand had its own personality but shared the family resemblance. You could tell they were siblings. That family resemblance is processing fluency at the brand architecture level: when a customer encounters a new SSH product line, the visual system says “you already know us, this is just a new room in the same house.”

Year four, the system was infrastructure. Seasonal palettes generated from the master system. Marketing teams could produce collateral without me touching every piece because the rules were documented, the templates existed, and the visual language was stable enough to be extended without breaking.

$1.7 million to $5 million. Same products. Same factories. Same price points. The perception changed.

---

The thing most people miss about processing fluency: the violations that hurt the most are the ones that are almost right.

There’s a paper from Bujack and colleagues in 2022 that changed how I think about color in design. They demonstrated that perceptual color space is non-Riemannian, which is a technical way of saying something designers need to understand: color perception doesn’t work the way our digital tools suggest it does.

In CSS, if you pick a blue and then shift it 3% in one direction, you’d expect the perceived difference to be proportional to the shift. It’s not. Color perception is non-linear and asymmetric. Some small shifts are imperceptible. Others, equally small in the math, are jarring. And the worst part: near-miss color deviations are disproportionately more disruptive than far-miss deviations.

Think about it this way. If your brand blue is #2563EB and someone uses #2866F0 on a banner, that’s a near miss. The brain catches it. Not consciously, not in a way the user can articulate, but the prediction error fires. “This is almost the right blue but something is off.” The brain can’t resolve whether it’s the same or different, so it keeps processing. Fluency drops. Trust drops. The feeling of “this is right” gets replaced by a subtle, unnameable sense that something is wrong.

Now imagine using a completely different color. Red instead of blue. The brain doesn’t try to reconcile that. It processes it as a different thing entirely. Different category, different prediction, no conflict. A far miss is less disruptive than a near miss because the brain doesn’t waste energy trying to match it to the existing prediction.

This is why brand police who obsess over exact hex codes aren’t being pedantic. They’re protecting processing fluency at the level where violations are most expensive. And it’s why the move toward perceptually uniform color spaces like OKLCH matters. The tools need to model how the eye actually works, not how the math says it should.

---

I keep coming back to the SSH tagline as a processing fluency case because it demonstrates something that’s hard to explain in the abstract.

I created “smart home decor” as a product category. It wasn’t a category that existed. Nobody was using that phrase. But it felt right, and that’s the point. The products were digital photo frames and smart displays. “Consumer electronics” was the accurate category. But consumer electronics processing triggers a whole set of predictions: comparison shopping, spec sheets, cheaper alternatives on Amazon, disposable tech. None of that matched the product’s actual value proposition, which was emotional connection between family members.

“Smart home decor” did something different. It triggered decor predictions: aesthetic value, fits your living space, worth displaying, permanent rather than disposable. The processing was fluent because the category name matched the experience of owning the product, even though it didn’t match the product’s technical classification.

I wasn’t inventing a false category. I was finding the one that processed more fluently against the truth of what the product actually did for people. A digital frame sits on your shelf next to other decor. It displays photos of your family. You pick the frame style that matches your room. That’s decor behavior. Calling it “consumer electronics” was the processing fluency violation, not the other way around.

Two years after I coined the phrase, Aura Frames started using nearly identical positioning. When your competitor steals your language, you know you found the category that the brain was already looking for.

This is processing fluency applied to naming, which most people don’t think of as a design decision but absolutely is. Every name, every category label, every tagline is a processing event. The brain encounters the words and either processes them fluently against existing mental models or stumbles. “Consumer electronics” processed fluently against the wrong mental model for SSH’s products. “Smart home decor” processed fluently against the right one. Same product. Different cognitive path. The path that matches reality converts better.

---

Typography is the most underrated processing fluency tool in design.

George Lakoff and Mark Johnson published Metaphors We Live By in 1980, and it’s one of those books that, once you read it, changes how you see language forever. Their core finding: abstract thought isn’t abstract. It’s built on bodily experience. We don’t just use physical metaphors for convenience. We think through them. “Happy is up, sad is down” isn’t poetic decoration. It maps to actual physical posture in those emotional states. “Argument is war” isn’t a creative choice. It structures how we actually experience disagreement (attacking positions, defending claims, winning or losing).

This matters for design because the way we describe visual and auditory experience reveals how the brain processes it. We use sensory words, the cross-modal kind, for everything. A color is “warm” or “cool.” A font is “heavy” or “light.” A layout is “clean” or “cluttered.” A brand voice is “rough” or “smooth.” None of these are literal. Colors don’t have temperature. Fonts don’t have mass. But the brain processes them through the same sensory channels it uses for physical experience.

Charles Spence demonstrated this empirically in 2011: people consistently match high-pitched sounds with small, bright objects located high in visual space. Low-pitched sounds match large, dark objects located low. These aren’t learned associations. They’re cross-modal correspondences baked into how the nervous system integrates information from different senses. When the correspondences align, processing is fluent. When they conflict, processing stutters.

This is why typography isn’t decoration. It’s the music layer of design. The spacing cadence, the weight distribution, the rhythm of headings to body text to whitespace. These create a temporal pattern that the brain processes the same way it processes a melody. Consistent rhythm equals fluent processing equals trust. Inconsistent rhythm equals stuttering equals doubt.

Two fonts maximum. Not because it’s a rule someone invented. Because each additional typeface is a new voice in the conversation, and the brain has to work to integrate voices. Two voices can have a dialogue. Three becomes a panel. Four becomes noise. The processing load compounds with each addition, and the fluency cost is steeper than most designers realize because they’ve already adapted to their own designs. The fresh eye hasn’t.

I think about this every time I see a site that uses a different font for the logo, the navigation, the headings, the body, and the call-to-action buttons. Five typefaces means five visual voices. The designer might have a rationale for each one. But the user’s brain doesn’t care about the rationale. It’s hearing five people talking at once and trying to figure out who to listen to. That cognitive work is invisible to the designer who chose the fonts deliberately, but it’s real for every first-time visitor.

---

The McGurk effect, discovered by McGurk and MacDonald in 1976, is maybe the most visceral demonstration of how cross-modal processing works. They showed people a video of someone mouthing one syllable while the audio played a different syllable. The result: people heard a third syllable, neither the visual one nor the auditory one, but a fusion of both that didn’t exist in either input.

The brain didn’t choose between eyes and ears. It merged them. And the merge produced something neither channel sent.

This matters for design because it proves that users don’t process your visual design and your copy and your interaction patterns separately and then combine them. The brain integrates across channels continuously, producing a fused perception that’s different from any individual element. Your typography style, your color palette, your image quality, your copy voice, your interaction timing: these aren’t separate design decisions. They’re inputs into a single perceptual fusion.

When those inputs are congruent, when the typography feels the same weight as the copy voice, when the color temperature matches the brand personality, when the image quality matches the price point, the fusion is clean. Processing is fluent. The thing feels true.

When they’re incongruent, the fusion breaks. And the result isn’t “the user notices the typography is wrong.” The result is a vague, unnameable sense that something is off. The user can’t point to it. They’ll tell you the site seems fine if you ask them. But they won’t convert. The prediction error is happening below the threshold of conscious access, and it’s driving behavior that neither the user nor the designer can explain through surface-level analysis.

This is why “fix the copy” or “fix the colors” is almost always the wrong diagnosis when conversion is underperforming. The problem isn’t in any single channel. It’s in the fusion. The channels are sending conflicting signals, and the brain is producing a fused perception that feels wrong without any individual element being obviously broken. You have to audit the congruence across channels, not within them.

---

A $500 product on a $50 website. That’s the most common processing fluency violation I see, and it’s the one that costs the most revenue.

Think about what happens cognitively. The user arrives with a price expectation (or discovers the price early in the visit). The brain immediately generates a prediction about what a product at that price point should look like, feel like, be presented like. This prediction is built from every other $500 purchase they’ve made. The Apple Store. A nice restaurant’s website. A boutique hotel’s booking page. That’s the reference class.

Now they’re looking at a template site with stock photography and three different font sizes that don’t relate to each other. The prediction error fires hard. Not “this site is ugly.” The evaluation is faster and more damaging than that: “something is wrong here.” The price says premium. The presentation says cheap. The brain can’t reconcile those signals, so it defaults to the safer interpretation. The product probably isn’t worth $500.

The reverse happens too. A $15 product on a site that looks like it costs $500 creates a different kind of dissonance: “this is too good to be true.” The brain predicts a catch, a scam, a bait-and-switch.

Processing fluency demands alignment. The visual presentation must match the price point, which must match the product quality, which must match the brand voice, which must match the customer service experience. Every mismatch is a prediction error. Every prediction error costs fluency. Every fluency loss costs trust.

I see this constantly in my consulting work. A SaaS company charges $200 per month but their marketing site uses free templates and system fonts. A luxury goods retailer has beautiful packaging and a website that looks like it was built in 2014. A professional services firm charges $300 an hour and sends proposals in plain-text email. In each case, the people running the business don’t see the mismatch because they know the value of what they’re selling. But the customer doesn’t know that yet. The customer is processing the presentation, and the presentation is sending a signal that conflicts with the price.

This is what I was fixing at SSH for four years. The products were $100 to $180. Good products, thoughtful engineering, real value. But the visual presentation was saying $30 clearance bin. Every time a potential customer landed on the site, their brain was running the price-to-presentation comparison, and the site was failing. The brand system wasn’t cosmetic improvement. It was the systematic elimination of price-perception mismatches across every touchpoint.

---

The practical takeaway sounds boring, but it compounds faster than anything else in design.

Boring consistency beats exciting inconsistency. Every time.

I know that’s not what designers want to hear. The exciting inconsistency is fun to design. The unexpected color. The surprising typeface. The layout that breaks the grid for emphasis. And there are times when controlled prediction errors create activation points (that’s Chapter 2 territory). But the ratio matters enormously. For every one place where you strategically break a pattern, there should be fifty places where the pattern holds.

Processing fluency is not a one-time fix. You don’t redesign a brand and walk away. It’s infrastructure that requires maintenance, enforcement, and gradual refinement. Each year at SSH, the system got tighter. The seasonal palettes got more systematic. The sub-brand guidelines got more specific. The templates got more detailed. And each year, the perceived quality of the brand went up, even when the products themselves didn’t change much.

That’s what compounding processing fluency looks like. Not a dramatic before-and-after. A slow, steady increase in how trustworthy, how professional, how right everything feels. The individual improvements are often invisible. A slightly better letter-spacing ratio. A more consistent padding rhythm across pages. The photography style guide getting one more rule that prevents a common mistake. None of these are portfolio pieces. All of them are moving the needle.

$1.7 million to $5 million over roughly two and a half years wasn’t one design decision. It was the compound effect of making everything feel like it belonged together, so the brain could stop working to reconcile conflicting signals and start evaluating the product on its merits.

Processing fluency isn’t glamorous. It’s the plumbing of perception. But when the plumbing works, everything above it works better. And when it doesn’t, nothing you build on top of it will fully land.

If you want to test this on your own brand tomorrow, here’s where to start. Pick one touchpoint, any touchpoint, and compare it to another. Your website and your business card. Your homepage and your about page. Your product packaging and your Amazon listing. Do they feel like they came from the same place? Not “do they use the same logo.” Do they feel the same? Same visual weight. Same typographic voice. Same level of quality. If they don’t, that’s your first processing fluency violation, and it’s costing you more than you think.

---

Next: The Gap, on what happens when your marketing team describes what the product does instead of what having it feels like, and how a tagline change preceded a 233% revenue increase.