The cognitive architecture of crypto UX

Three breaks in one flow

A single on-chain transaction: connect wallet, approve token access, set gas parameters, sign the payload, wait for confirmation, verify the result. At every step, something breaks cognitively. The failures are not novel. They have names, authors, and decades of research behind them. Three frameworks map onto one flow, and nobody in the industry seems to have noticed.

First failure: the user cannot act

A crypto wallet has six or more invisible states: connected, disconnected, locked, wrong network, pending approval, insufficient balance. Jef Raskin identified this exact class of problem in The Humane Interface and called it the mode problem. The user's mental model of the system's state diverges from the actual state, and the interface provides no signal to close the gap. Don Norman formalized this as the Gulf of Execution. In most software, a mode error wastes time. In financial products, a mode error is a loss.

Second failure: the user cannot tell

The Doherty Threshold, established by IBM research in 1982, found that cognitive flow breaks when system response exceeds 400 milliseconds. On-chain confirmation can take much longer than that. Norman's Gulf of Evaluation describes what happens in that void: the user has no way to assess the system's state, so they guess, retry, or panic. Uncertainty destroys trust faster than bugs do. A bug is a known problem. Uncertainty is an unknown one.

Third failure: the user cannot choose

Gas settings, slippage tolerance, token approvals. Hick's Law predicts that decision time increases logarithmically with the number of equally probable options. When every option looks equally meaningless, the user stalls. Jared Spool calls this the Knowledge Gap: the distance between what the user knows and what the interface demands they know. Most teams respond by adding tooltips, which paradoxically widens the gap by signaling complexity. The fix is progressive disclosure and smart defaults that collapse the decision space to what actually matters.

Failures compound

These three failures do not occur in isolation. They compound. A user who cannot tell if their wallet is connected, cannot evaluate whether the previous transaction landed, and cannot parse the gas options for the next one arrives at a single moment of total confusion. The interface has not failed in one way. It has failed in three simultaneous, reinforcing ways.

Solutions already exist

Every one of these problems has published solutions. Progressive disclosure for Hick's Law. Optimistic UI for the Doherty Threshold. Explicit state indicators for Raskin's mode problem. The research exists. The implementations do not.

Diagnose first

Diagnose before you design. Never prescribe a fix until you can name the failure.