SETHJACOBS

Part 1 of 2 · July 16, 2026

Decision-Making in UX: The Two-System Concept, Part 1

Kahneman calls intuition nothing more and nothing less than recognition. Take that seriously and most of what we call good design turns into something you can design on purpose.

7 min readCognitive loadPrimingEnterprise UX

When it comes to intuition, Daniel Kahneman explains it best: intuition is nothing more and nothing less than recognition.

That line, from Thinking, Fast and Slow, sticks with me for one reason. Apply it to Kahneman’s two-system concept, the argument that two systems in your brain are in a constant fight over your actions and behavior, and it gives scientific footing to what we do every day.

Our job is to build intuitive, innovative, easy-to-use platforms. But those words mean nothing until you understand what is driving the outcome underneath them. So let’s get into it.

The two-system concept

Kahneman’s definitions, more or less as he gives them:

  • System 1 operates automatically and quickly, with little or no effort and no sense of voluntary control.
  • System 2 is slow, effortful, infrequent, calculating, and houses our ability to reason.

Which one favors intuition? System 1. Now merge the two definitions and look at what you get: a system that automatically and quickly recognizes past experiences with little or no effort.

That's what we're trying to build when we say we want an intuitive experience. We're priming someone for recognition. When it lands, it's automatic and effortless. They know how to work the thing, because of everything they have used before it.

SYSTEM 1Automatic. Fast. No sense of voluntary control.Steering a car on a familiar roadReading a word you knowKnowing a button is a buttonRecognition. This is where intuition lives,and where you want the experience to sit.SYSTEM 2Slow. Effortful. Where reasoning happens.Multiplying 17 × 24 in your headA form that invents its own rulesHunting for a control that movedEffort. Sometimes unavoidable. Usually adesign decision nobody made on purpose.
Design pushes work toward the left panel. Neglect lets it drift to the right.

What is priming?

Innovation is how we create trends, break moulds, and push past the status quo. But run it through the two systems and you can see the cost: a genuinely new pattern forces people into System 2, where they have to spend effort learning it. That's a difficult balance. Too much novelty and nobody buys in. Too little and you're indistinguishable from everyone else.

We have all watched trend after trend become a mainstay. Gradients, metro, flat, parallax, and a thousand others. Why did those stick? Repetition. People got used to them and started to expect them. That's priming.

In information architecture, priming is how we point people at what matters. It's the basis of how we build navigation and how we organize a data table. Most people arrive wanting to consume content, so most of the work goes into associating them with that content before they have to think about it.

A quick experiment

Read this sentence: He took his daughter to the aquarium.

Now finish this word: _ISH

My guess is you wrote fish. If the first sentence had been about a genie in a bottle, you'd probably have written wish. That's System 1 making the association, and it cost you nothing.

When we build an information architecture or a visual design, we're chasing those same associations. Categorize a navigation structure and you want the links (parallel or hierarchical) to associate strongly. Build a visual design and you want the cues to prime the interaction you're hoping for.

EACH LEVEL PRIMES THE NEXTFishingSaltwaterReelsFly ReelsInshoreBy the time they reach the last level, they already expect what is behind it. Nothing here is a surprise,and that is the point. A good hierarchy spends its effort making the next step obvious.Break the chain (put Fly Reels under Boats) and every level after it costs effort.
Fishing → Saltwater → Reels → Fly Reels → Inshore. Each level sets up the next, so the last one lands as a confirmation rather than a surprise.

Visual priming works the same way. Rating stars are a good example. Ask someone to rate their experience, show five outlines, and you've primed the interaction. Nobody needs the instruction. Those outlines were a new idea once too. Priming is what made them obvious.

Identifying those links, and priming people for a new pattern, is how you get innovation in the door. It's new to them, but through priming it arrives feeling effortless and familiar. And the less effort you demand, the easier everything downstream becomes. That's cognitive easing. Once someone is in it, things flow, because they're easy.

Designing for the cognitively busy

Years ago I helped a manufacturer redesign its business application. I shadowed workers on-site, watched the physical work, and learned how the software fit into their day. After a lot of conversations on the plant floor, the same comment kept coming back: make it easy.

At first I made light of it. Everyone says make it easy. But going back through the feedback I realized the physical part of their job was taking a slice out of their cognitive pie. It was depleting their systems before the software ever got a turn.

These people stand all day operating dangerous machinery with their hands. They needed an application that let them keep their attention on safe production. Give them the information they want, when they need it, and do it safely. In other words: manage their cognitive load and build the whole thing for System 1.

Sometimes you have to stand in the physical environment before you understand the limits of it. People can be mentally, physically, or emotionally cognitively busy, and you won't really get it unless you see it or hear it first-hand.

I push empathy mapping on every project for that reason. You have to empathize with what your customers need before you can build something they love.

The takeaway

If there's one thing worth keeping from this, it's Kahneman's line. Intuition is automatic recognition of past experience, helping with the current one. When someone expects something, we shouldn't hand them the unexpected.

But put in the work to learn about people in their own environment and you can do better than their expectations in the first place.

Part 2 gets into how you find the System 2 moments hiding in a product you have already shipped.