Decision Fatigue

In 2011, a team of researchers published an analysis of 1,112 parole decisions made by Israeli judges over a ten-month period. They found that the probability of a favourable ruling — parole being granted — started each session at around 65% and dropped steadily toward zero as the session continued, before resetting after a food break. The judges were not getting harsher with each case on principle. They were running out of the cognitive resources required to make considered decisions. The default when depleted was denial — the path of least resistance.

This is decision fatigue: the deterioration in the quality of decisions made after a long session of decision-making. It was named and studied systematically by Roy Baumeister and colleagues, who proposed that willpower and decision-making draw from the same limited cognitive resource — one that depletes with use and recovers with rest. The finding that this resource is genuinely finite, and that depletion produces measurable changes in decision quality, has been one of the most consequential results in applied psychology.

For product designers, the implication is direct. Every step in a checkout flow, every option in an onboarding wizard, every setting in a configuration screen is a decision. Each one costs cognitive resource. By the end of a long flow, the user is not the same person who started it. They are more impulsive, more likely to accept defaults, more likely to abandon, and more likely to defer. Designing a long flow without accounting for decision fatigue is designing for the alert, fresh version of the user — who left several screens ago.

“Making decisions uses the very same willpower that you use to say no to doughnuts, stick to your budget, and hold your tongue when provoked.”
— Roy Baumeister & John Tierney, Willpower, 2011

A typical checkout — counting every decision as it accumulates

Most designers think about individual steps in isolation — “this step asks for shipping address, this one selects delivery speed.” Decision fatigue requires thinking about the cumulative load across all steps. Below is a checkout flow where every decision is counted. Watch the cognitive load bar as you progress through it.

Each radio button, dropdown, checkbox, and field you encounter is a decision. Click through the steps and see how many you've made by the time you reach payment.

By the time most users reach the payment screen of a typical e-commerce checkout, they have made between 15 and 22 individual micro-decisions. Payment is the step that matters most — it is the one where the user commits real money. But it arrives at the end of a depleting flow, when cognitive resources are lowest. This is one reason cart abandonment rates are highest at checkout, and one reason why one-click purchase systems — which collapse the entire decision burden into a single previously-stored choice — convert at dramatically higher rates.

Salesforce vs Linear — the real cost of “just a few more fields”

Salesforce and Linear are both B2B SaaS tools. Both require an account to use. Both ask for an email address. But the free trial signup experience is so different that they effectively demonstrate the two poles of decision fatigue in real products — one optimised for data collection, the other for the user arriving at the product as fast as possible.

A Salesforce free trial collects 11 fields before the user sees a single screen of the product. Linear collects one field — an email address — and gets you to a workspace in under 30 seconds. The products differ significantly in complexity and audience, but the contrast in signup philosophy is still the clearest real-world illustration of decision fatigue thinking in product design.

Linear does not give the user fewer choices — it makes choices on their behalf. Role, company, and team size are collected during onboarding after the user has seen the product, not before. Terms are implicit rather than a checkbox requiring an active decision. The difference in cognitive load between these two flows is not subtle. By the time a Salesforce user clicks “Start my free trial,” they have expended the same decision-making effort that a Linear user will not spend until they are deep into their second session.

Applying this to your work

Decision fatigue is a lens as much as a principle. Applied to a design, it asks: how many decisions has the user already made by the time they reach this screen? Applied to a flow, it asks: which of these decisions are necessary, and which are being asked out of habit or data collection convenience rather than genuine user need? Applied to a form, it asks: what is the minimum we need to know right now, and what can wait until after the user has experienced value?

The hard part is institutional. Removing decisions from a flow often means removing data points from the company's database, removing options from the product team's roadmap, and removing flexibility from the user. Each of these is a cost. The argument for bearing those costs is that a user who arrives at the key moment — purchase, commitment, upgrade — with cognitive resources intact is measurably more likely to make the decision you want them to make.

Baumeister, R. F., Bratslavsky, E., Muraven, M., & Tice, D. M. (1998). Ego depletion. Journal of Personality and Social Psychology, 74(5), 1252–1265. · Danziger, S., Levav, J., & Avnaim-Pesso, L. (2011). Extraneous factors in judicial decisions. PNAS, 108(17), 6889–6892. · Baumeister, R. F., & Tierney, J. (2011). Willpower: Rediscovering the Greatest Human Strength. Penguin Press.