Defensiveness: Users Aren’t Unable — They’re Afraid to Use It
When AI features sit unused, postmortems often blame “not enough user education,” ship another onboarding modal, and still nobody uses them. The real reason is often defensiveness: they understood your feature — then decided not to touch it. This lesson first checks whether you yourself are defensive, then unpacks three sources of defensiveness, and finally flips the three levers one by one across five toys you play yourself.
Before we talk about users, look at yourself. Six questions — answer from your real reflexes. When you’re done, we’ll draw your defensiveness profile.
Those six questions came in pairs, one pair per kind of defensiveness. Each has a psychology source, and each has a line users mutter to themselves. The shared pattern: defensive users rarely say “I’m defending” — they say “it’s not that useful,” and never open it again.
Data defensiveness
The higher-value the scenario (contracts, financials, customer lists), the more sensitive the data — and the stronger the defensiveness. The paradox: AI is most valuable precisely in high-value scenarios, so data defensiveness blocks the value from landing. Training toggles often exist, but users don’t know; not knowing, they brace for the worst.
Competence defensiveness
The #1 killer of internal tools. Employees read “using AI” as “admitting I’m replaceable,” and usage data as performance surveillance. This defensiveness never gets spoken — it shows up as “I tried it; not that useful.” Lesson 12 on cognitive offloading unpacks the other half: what they fear is looking replaceable.
Responsibility defensiveness
A rational calc: AI saves two hours, but if it errs you own the whole failure — expected value goes negative, so not using it is correct. When an AI feature’s responsibility boundary is fuzzy, user defensiveness is rational. Lesson 5 on trust calibration offered the fix: keep a human sign-off in the loop (HITL), make clear who confirms and who owns it — only then can you talk about lowering defensiveness.
Defensiveness has three antonyms: sense of control, reversibility, and transparency. Each has experimental backing, and each can land as a concrete UI change. The three interfaces below are stuck in high-defensiveness mode — flip the switches and watch the same UI go from “scare them off” to “dare to try”, with the defensiveness score updating live.
① Sense of control
Averill (1973)② Reversibility
Shneiderman’s golden rules③ Transparency
Dinev & Hart (2006)A hundred explanations of reversibility on paper beat one click of your own. Below is a high-stakes batch action — notice what you feel at each step: how long you hesitate before Apply, and how it feels once you see Undo is available.
These three features are stuck at low usage because of defensiveness. Each offers three candidate moves — pick what you’d ship, and the defensiveness index updates live. Careful: each set buries one placebo that looks like a cure, and one of them is a real fake switch.
You’re the PM for AI customer service. Human agents are expensive, and you fear everyone will bolt to a real person. Where does the “hand off to a human” button go? Two variants have each run for a month — bet first: which side has the higher hand-off rate? Tap the side you pick.
What this lesson wants to share
- For low usage, check defensiveness first: audit the data, competence, and responsibility axes before talking user education
- High-risk actions always get draft state + undo: drop the bar to try from courage down to curiosity
- Say where data goes in plain talk: pair it with a verifiable status, e.g. “Deleted”
- Put the exit in plain sight; never ship a fake switch: fake control that gets found out rebounds defensiveness even higher