Design Principles
Gulfs of Execution and Evaluation
Every interaction has two potential failure points: the gulf of execution (user can't figure out how to do what they want) and the gulf of evaluation (user can't tell whether what happened was what they intended).
Where it comes from
The two gulfs come from Don Norman's analysis of how interaction succeeds or fails. He identified two gaps a user must bridge: the gulf of execution (working out how to do something) and the gulf of evaluation (working out whether it worked).
Why it matters for your website
Norman identified two fundamental gaps that separate users from their goals. The gulf of execution is the gap between what a user wants to do and what the interface makes it possible to understand how to do — "how do I make this happen?" The gulf of evaluation is the gap between what happened and the user's ability to interpret it — "did that work?" Both must be bridged for an interaction to succeed. Wide gulfs are not user failures; they are design failures. A clear label closes the execution gulf before the click; clear feedback closes the evaluation gulf after it. Complexity itself is not the problem — confusion is.
The two gulfs map neatly onto the two questions a user silently asks. Before acting: 'how do I make this happen?' — the gulf of execution. After acting: 'did that work?' — the gulf of evaluation. An interaction succeeds only when both are bridged.
Crucially, a wide gulf is a design failure, not a user failure. When someone can't figure out how to do something, or can't tell whether their action worked, the interface hasn't given them enough — and the fix is a clearer label before the click, or clearer feedback after it. Complexity isn't the enemy; confusion is.
Wrong vs right
A control whose purpose is unclear, leaving the user unable to work out how to achieve their goal (a wide gulf of execution).
A clear label and obvious affordance that close the execution gulf before the click.
An action that gives no clear result, so the user can't tell whether it worked (a wide gulf of evaluation).
Clear feedback after the action that closes the evaluation gulf and confirms what happened.
Blaming users for 'not getting it' when the interface left both gulfs wide open.
Treating the confusion as a design gap and bridging it with clearer cues and feedback.
Understanding Gulfs of Execution and Evaluation
Don Norman identified two gaps that stand between a user and their goal. The gulf of execution is the gap between what the user wants to do and figuring out how to do it with the interface — 'how do I make this happen?'. The gulf of evaluation is the gap between what the system did and the user's ability to interpret it — 'did that work?'. Every interaction has to bridge both.
The two gulfs correspond to the before and after of any action. A clear label, an obvious affordance, and good information scent close the execution gulf before the click; clear, immediate feedback closes the evaluation gulf after it. When either gulf stays wide, the interaction breaks down — the user either can't act, or can't tell what their action achieved.
Norman's framing carries an important reframe: a wide gulf is a design failure, not a user failure. When someone can't work out how to do something, or can't tell whether it worked, the fault lies with the interface that left the gap — and the cure is clarity, not blame. Complexity itself isn't the problem; confusion is. It connects to affordances, feedback, and design for closure.
How Kweri checks it
Kweri can surface signals on both sides of the gulfs. For the gulf of execution, it can flag unclear labels, weak affordances, and ambiguous next steps that make it hard to work out how to act. For the gulf of evaluation, it can flag actions that appear to give no clear feedback. What it can't fully judge is how wide a gulf feels to your specific users, which depends on their familiarity and context, and how interactions behave over time. So Kweri points to likely execution and evaluation gaps and prompts you to close them with clearer cues and feedback, while real width is confirmed by testing.
FAQ
What are the gulfs of execution and evaluation?
They're two gaps a user must bridge in any interaction, identified by Don Norman. The gulf of execution is working out how to do what you want ('how do I make this happen?'); the gulf of evaluation is working out whether it worked ('did that work?').
What is the gulf of execution?
The gulf of execution is the gap between what a user wants to do and figuring out how to do it with the interface. It's bridged before the action — by clear labels, obvious affordances, and good information scent that make the right step apparent.
What is the gulf of evaluation?
The gulf of evaluation is the gap between what the system did and the user's ability to interpret it — whether their action worked and what it changed. It's bridged after the action, by clear and immediate feedback.
Are wide gulfs the user's fault?
No — Norman is explicit that a wide gulf is a design failure, not a user failure. If someone can't work out how to act, or can't tell whether their action succeeded, the interface hasn't given them enough. The fix is clarity, not blame.
How do I close the two gulfs?
Close the execution gulf with clear labels, obvious affordances, and good scent before the click; close the evaluation gulf with clear, immediate feedback after it. The goal is that users always know how to act and always know what happened.
Related principles
Every action should produce an immediate, clear response confirming it registered.
Every sequence of actions must have a clearly defined end state that tells users the task is complete — open-ended sequences create anxiety and uncertainty.
Always tell users what's happening, with clear feedback delivered in good time.
Attribution & sources
Identified by Don Norman. Catalogued from Nielsen Norman Group — The Two UX Gulfs: Evaluation and Execution.
Norman's framework for how interactions succeed or fail; the linked article is the reference used here.
See Gulfs of Execution and Evaluation on your own site
Run a free Kweri audit — a plain-English review of your site’s speed, accessibility, SEO and design, ranked by what to fix first. No login, no jargon.
Run a free audit →