Cognitive Friction
Adaptive speed bumps — seamless for low stakes, mandatory pause for high uncertainty
Approval gates are binary: pause or do not. Cognitive Friction is a continuous axis baked into the flow itself. The system reads task stakes — criticality × uncertainty × reversibility — and inserts proportional friction: a one-second confirm for low stakes, a written rationale for high uncertainty, a 5-second cool-down + secondary signer for irreversible high-criticality steps. Builds on the aviation principle that pilots need different attention budgets for different actions, and the medicine principle that surgeons get mandatory checklists before incisions but not before pre-op chart review. From Google DeepMind's "Intelligent AI Delegation" (Tomašev, Franklin & Osindero, Feb 2026): "friction must be context-aware: the system should allow seamless execution for tasks with low criticality or low uncertainty, but dynamically increase cognitive load."
Framing
The problem
Approval gates are binary — either pause or do not. Real risk is continuous: a one-cent transaction and a $50,000 transfer cannot need the same number of clicks, but most systems give them either both no friction or both the same friction.
The pattern
Read task stakes (criticality × uncertainty × reversibility) and insert proportional friction: no friction for low stakes, a one-line confirm for medium, a written justification for high uncertainty, a cool-down + secondary signer for irreversible high-criticality. The friction policy is inspectable, configurable per workspace.
Why chat breaks here
Chat treats every turn as the same kind of action — there is no signal-carrying surface for "this one is more dangerous than the last one." Users rely on prose disclaimers and self-discipline, which fail predictably under deadline pressure.
Risks
Without context-awareness, friction degenerates into alarm fatigue — too many high-friction prompts train users to click through them. Conversely, too little friction on critical actions enables rubber-stamping.
Avoid when
All actions in the surface have approximately equal stakes (a sandbox, a draft-only tool) — a fixed friction level is simpler and just as safe.
Use when
Binary approval gates either over- or under-prompt the user for every action. Context-aware friction scales the pause to the actual stakes — flow when it is safe, structured deliberation when it is not.
DOPE evaluation
- Directability
- Users can override friction with explicit acknowledgement; system records the override for later audit
- Observability
- The applied friction level is named back to the user along with the stakes inputs that triggered it ("high criticality + low reversibility → mandatory justification")
- Predictability
- Stakes inputs map deterministically to friction intensity — users learn what a "5-second cool-down" means and trust it
- Explainability
- The friction policy itself is inspectable as a rule set — what stakes produce what friction, configurable per workspace
In the wild
- Apple · Authentication Required (tiered) (Apple) — iOS/macOS prompts scale by sensitivity: silent for app-launch, Touch ID for low-stakes purchases, Face ID + 6-digit passcode for App Store, full passcode after restart. The same OS-level pattern, applied to four different stakes tiers.
- GitHub · Branch Protection Rules (GitHub) — Different branches get different friction: main requires reviews + status checks + linear history; feature branches require nothing. Friction proportional to blast radius, configured as policy.
- Stripe · Strong Customer Authentication (Stripe) — Low-value contactless transactions waved through; high-value or unusual transactions trigger 3D Secure step-up. PSD2 codified the principle: friction calibrated to risk score, not flat per transaction.
- Anthropic · Claude Code permission prompts (Anthropic) — Claude Code gates destructive actions (rm -rf, force-push, git reset --hard) behind confirmation prompts while reversible edits flow freely — stakes-aware friction shipped in a mainstream agent, with the override itself an explicit, logged choice.
- Cognitive Agency Surrender: Defending Epistemic Sovereignty via Scaffolded AI Friction (Academic source · Xu, Shen, Yan, Ren (Cyberspace Security University of China, Mar 2026)) — Independent argument for *scaffolded* friction — designed to preserve user epistemic agency, not just gate dangerous actions. Same pattern, different load-bearing rationale (cognitive sovereignty over operational safety). Useful counter-frame.
FAQ
When should I use the Cognitive Friction pattern?
Binary approval gates either over- or under-prompt the user for every action. Context-aware friction scales the pause to the actual stakes — flow when it is safe, structured deliberation when it is not.
When should I avoid the Cognitive Friction pattern?
All actions in the surface have approximately equal stakes (a sandbox, a draft-only tool) — a fixed friction level is simpler and just as safe.
What problem does Cognitive Friction solve?
Approval gates are binary — either pause or do not. Real risk is continuous: a one-cent transaction and a $50,000 transfer cannot need the same number of clicks, but most systems give them either both no friction or both the same friction.
Why is chat the wrong fit for this?
Chat treats every turn as the same kind of action — there is no signal-carrying surface for "this one is more dangerous than the last one." Users rely on prose disclaimers and self-discipline, which fail predictably under deadline pressure.
Related patterns
- Alternative to: Approval Gates — Binary pause vs continuous friction axis. Approval gates are appropriate when stakes are uniform; Cognitive Friction is for surfaces where stakes vary by action.
- Often paired with: Autonomy Dial — Autonomy Dial sets the policy globally; Cognitive Friction applies the friction per-action based on per-action stakes. Two halves of a calibrated trust system.
- Often paired with: Capability Boundary — Capability Boundary declares what cannot be done at all; Cognitive Friction shapes how the user moves through what can be done.