How something makes you feel determines how you evaluate it — not the other way around. People do not assess the facts and then form an emotional response. They form an emotional response and then construct the facts to support it. Feeling precedes reasoning. In product design, this means the emotional tone of an interface shapes every judgment the user makes inside it.
In a series of studies published in the 1990s and 2000s, Paul Slovic and colleagues asked people to rate technologies and activities — nuclear power, food preservatives, pesticides, X-rays — on two dimensions: perceived benefit and perceived risk. In a rational world, these two ratings would be independent. Something might be high risk and high benefit (surgery), or low risk and low benefit (a routine commute). Instead, Slovic found a striking correlation: people who felt positively about a technology rated it as high benefit and low risk simultaneously. People who felt negatively rated it as low benefit and high risk. The affect — the emotional response — was setting both readings at once.
This is the affect heuristic: the use of emotional response as a quick signal for judgment. Rather than computing the expected value of a decision from first principles, the brain asks “how does this feel?” and uses that answer as a proxy for good or bad, safe or dangerous, worth it or not. The heuristic is efficient — it collapses a complex evaluation into an immediate felt sense — but it means that the emotional tone of how something is presented shapes the substance of the judgment, not just its packaging.
Daniel Kahneman integrated the affect heuristic into his broader framework as a canonical example of System 1 thinking: fast, automatic, and emotional, running alongside but often overriding the slower deliberative reasoning of System 2. For product designers, the practical implication is significant. A user who arrives at your product with a positive emotional response — from a warm onboarding email, a well-designed landing page, a delightful first interaction — will subsequently rate your product as more useful, more trustworthy, and less risky than the identical product experienced under a neutral emotional state. The affect sets the frame through which everything inside the product is then evaluated.
“If I like something, I believe it is safe and beneficial. If I dislike it, I believe it is dangerous and without merit. Affect does the work that reasoning pretends to do.”
— Paul Slovic, 2002
Notion and Confluence are direct competitors. Both are team wikis. Both store documents, notes, and project pages. Both integrate with the same tools. The difference is almost entirely in how they make users feel. Notion built its brand on warm, human, almost philosophical copy. Confluence built its on capability, enterprise credibility, and feature depth.
The affect heuristic predicts that this emotional difference will shape how users rate the products on dimensions that should be independent of feeling — ease of use, quality of support, whether it is worth paying for. Below are the actual landing pages, and below each one the real G2 user ratings from over 8,500 combined reviews.
Same category, same feature set — but the emotional tone shapes every downstream rating, including ones logically independent of warmth.
Both tools are team wikis. Both store and organize documents. Both integrate with Slack and Jira. But Notion scores 4.7 vs Confluence's 4.1 overall, 9.2 vs 7.4 on ease of use, and 8.7 vs 6.8 on quality of support — across 8,500 independent reviews. The products are not identical, so feature differences explain some of the gap. But the pattern matches exactly what the affect heuristic predicts: the warmer presentation generates higher ratings across every dimension simultaneously, including dimensions logically independent of warmth.
Notion's users do not just enjoy the product more. They find it easier to use, rate its support as better, and recommend it more — 93% vs 79%. The emotional experience of using Notion shapes the lens through which every subsequent interaction is evaluated. This is the affect heuristic at product scale: feeling precedes judgment, and judgment follows feeling's lead.
Error messages are one of the highest-stakes affect moments in product design. They arrive at a moment of user frustration, which already carries negative affect. A poorly written error compounds that affect — making the user feel the product is unreliable, the company careless, and the problem harder than it is. A well-written one can partially recover the affective state, making the same error feel minor and the product feel responsive.
Below are two error messages for the same failure — a payment that did not go through. The failure is identical. What changes is the affective charge of how it is communicated.
Error code shown. Cold language. “Contact your bank” implies the failure is the user's problem. Risk perception rises.
“This happens sometimes.” “Your order is saved.” “Nothing was charged.” The product feels safe and human.
The error in both cases is the same: a declined transaction. But the affective charge of the two messages is completely different. The first communicates the error in cold, technical terms that amplify the existing frustration — an error code, passive voice, blame redirected to the user's bank. The affect this produces colours the user's evaluation of everything that follows: the product seems less reliable, the checkout flow seems riskier, and the next attempt feels less likely to succeed.
The second uses language that normalises the problem (“this happens sometimes”), reassures the user (“nothing was charged”), and frames the next action as simple (“the quickest fix”). It does not resolve the error — the card still did not go through. But it partially recovers the affective state, meaning the user who reads it approaches the retry in a more optimistic frame. That frame makes recovery more likely.
The affect heuristic is not primarily a copywriting principle or a visual design principle. It is a principle about the relationship between emotional tone and downstream judgment — and it operates at every layer of the product, from the landing page to the error message to the cancellation flow. The designer who accounts for it asks not just “is this clear?” but “what affective state does this create, and how does that state shape what the user evaluates next?”
The most important application is sequential: the affect created early in a flow shapes the evaluation of everything that follows. A great first impression makes subsequent friction feel minor. A poor one makes subsequent delight feel insufficient. Designing for affect is not about making things feel pleasant — it is about understanding that feeling is the lens through which everything else is seen.
Slovic, P., Finucane, M. L., Peters, E., & MacGregor, D. G. (2002). The affect heuristic. In T. Gilovich, D. Griffin, & D. Kahneman (Eds.), Heuristics and Biases: The Psychology of Intuitive Judgment. Cambridge University Press. · Kahneman, D. (2011). Thinking, Fast and Slow. Farrar, Straus and Giroux. · Finucane, M. L., Alhakami, A., Slovic, P., & Johnson, S. M. (2000). The affect heuristic in judgments of risks and benefits. Journal of Behavioral Decision Making, 13(1), 1–17.