Special Topic · AI Product Psychology: Design the Feeling

Nine Books to Thicken This Chapter

From Kahneman, Norman, Cialdini, and Thaler to The Media Equation: nine books unpack nineteen principles every PM needs, each with an AI product application and a lesson to revisit; pick by the problem your product has now, then take a quick principle-matching quiz

THE QUESTION THIS PAGE ANSWERS

ANSWER FIRST

What is the key idea behind “Nine Books to Thicken This Chapter”?

From Kahneman, Norman, Cialdini, and Thaler to The Media Equation: nine books unpack nineteen principles every PM needs, each with an AI product application and a lesson to revisit; pick by the problem your product has now, then take a quick principle-matching quiz

DECISION RULE

Turn taste into a behavior the product can repeat. The useful outcome is not a nice opinion. It is a visible rule, a small example, and a way to tell when the experience falls below the bar.

TRY NEXT

Capture one before-and-after example that shows the quality bar without extra explanation.

WATCH FOR

Polish that improves the surface while leaving the user's uncertainty untouched.

How to use this list. Reading all nine cover to cover takes about three months; most PMs don’t make book two. A more practical path: pick one current product pain below—the shelf and cheat sheet light up matching books and principles; read the lit ones first. Each card footer says where to start; skip freely.
Step 1 · Pick your current pain

Tap a pain point—the shelf and cheat sheet below will shift together.

Shelf · nine books
One boundary up front. The variable rewards and investment loop in Hooked are as powerful as they are controversial. Everything in this chapter uses psychology to remove friction: make waiting less painful, align trust with ability, help users dare to use it. Using the same toolkit to manufacture anxiety and trap attention is another road—and products on that road end up fighting regulators and reputation. Read it to recognize the mechanisms; whether and how far to use them is your call.
Principle cheat sheet · nineteen, each with an AI application
Principle · sourceOne-line ruleAI product applicationRevisit
Principle-matching quiz · see the scene, name the principle
Don’t leave right after the cheat sheet. The four scenes below come from real AI product reviews; each stands on one principle from the table. If you can name it, the sheet is in your head; if not, skim once more.

Turn the feeling in “Step 1 · Pick your current pain” into a judgment

“Tap a pain point—the shelf and cheat sheet below will shift together” points out that AI has lowered the bar for making something usable. The skill readers need is noticing what is wrong and turning that feeling into an actionable requirement.

Watch the user's next action, not just the surface

Turn “Tap a pain point—the shelf and cheat sheet below will shift together” into observable questions: does the user know what happened, what to do next, and how to recover from an empty or failed state? Does the hierarchy make the important information visible first?

  • Lessons are compressed; books are the concentrate : citing the original beats citing slides when you persuade engineers and bosses
  • Read by pain, not by shelf order : what’s useful to you is often just two or three chapters
  • Nineteen principles are a toolbox : scan the cheat sheet before a design review—faster than flipping books on the spot

Pretty is not the same as usable

Apply “Tap a pain point—the shelf and cheat sheet below will shift together” to a second screen or flow. Record one moment of hesitation and the user action after the change; observable behavior is stronger evidence than polish alone.

From “Step 1 · Pick your current pain” to “Shelf · nine books”

“Step 1 · Pick your current pain” grounds the problem in “Tap a pain point—the shelf and cheat sheet below will shift together”. “Shelf · nine books” then moves it toward “One boundary up front. The variable rewards and investment loop in Hooked are as powerful as they are controversial. Everything in this chapter uses psychology to remove friction : make waiting less painful, al…”. Together, they show that the lesson is not just a conclusion to remember, but a claim with conditions.

Carry the judgment into the next situation

For experience work, turn abstract impressions into user actions: did the person understand the state, find the next step, recover from an error, and want to continue?

  • “Step 1 · Pick your current pain”: Tap a pain point—the shelf and cheat sheet below will shift together
  • “Shelf · nine books”: One boundary up front. The variable rewards and investment loop in Hooked are as powerful as they are controversial. Everything in this chapter uses psychology to remove friction : make waiting less painful, al…
  • “The closing point”: Psychology is for removing friction : manufacturing addiction is the other edge of the same blade—don’t touch it

The final “The closing point” brings the discussion to “Psychology is for removing friction : manufacturing addiction is the other edge of the same blade—don’t touch it”. The useful thing to carry forward is knowing which judgments must be revisited when input, scale, or risk changes.

What this section wants to share

  • Lessons are compressed; books are the concentrate: citing the original beats citing slides when you persuade engineers and bosses
  • Read by pain, not by shelf order: what’s useful to you is often just two or three chapters
  • Nineteen principles are a toolbox: scan the cheat sheet before a design review—faster than flipping books on the spot
  • Psychology is for removing friction: manufacturing addiction is the other edge of the same blade—don’t touch it
Mark as learned Your reading progress updates automatically
← PreviousNext →

Keep reading

The next useful article in the thread.

ARTICLE DISCUSSION

Leave one useful thought here.

Keep the idea that clicked, the question that stayed open, or a small note for the next learner.

Discussing Nine Books to Thicken This Chapter AI Product Psychology: Design the Feeling
3discussionsArticle discussion · synced with the Circle
View in the learning circle
AM
Asha MorganContent editor
INSIGHTField note

I turned one judgment from this article into a small experiment I could run today. Knowing what to observe next is more useful than simply remembering the conclusion.

ARTICLE DISCUSSION7 helpful
LH
Lin HarperIndie developer
INSIGHTInsight

After reading this, I first looked for the conditions behind the idea instead of copying the method into a project. That order made the later trade-offs much clearer.

ARTICLE DISCUSSION5 helpful
KM
Kiki MooreProduct operations
QUESTIONQuestion

When this judgment reaches real work, which constraint should be added first? I am curious which step matters most between reading and the first practical attempt.

ARTICLE DISCUSSION4 helpful