Interaction Excise
In short Excise is work that the tool demands but that does not move the user toward their goal. Cooper and his co-authors treat it like a tax to be hunted down and cut. For analysts, it is a simple test to run on every step of a scenario or prototype.
Based on: A. Cooper, R. Reimann, D. Cronin, About Face 3: The Essentials of Interaction Design (2007), ch. 11.
On this page
Key ideas#
Goal-directed work vs. excise#
The book’s analogy is driving to work. Driving is the task that serves your goal. Opening the garage door, starting the engine, stopping at lights and refueling are excise. The car or external rules need them, not you, but you can’t avoid them. Out of habit, people stop noticing the difference.
In software, obvious excise includes installing applications, configuring systems and making backups. The authors’ advice is to hunt excise with enthusiasm and remove it wherever possible, since effort spent on it only lowers productivity and satisfaction.
Compare total excise, not visible excise#
Experienced command-line users often complain that moving and resizing windows is excise that typing a command avoids. That is true, but the command line carries heavier excise: you must learn and remember commands before you can do anything. A graphical interface lowers excise for occasional and new users through visual clarity. The lesson: compare the total burden, including memory and learning, not just the visible clicks.
Types of excise#
- Training wheels. Features that help beginners, such as wizards and step-by-step guides, become excise once the user is an everyday intermediate. They should be easy to switch off. The book’s image: don’t weld the training wheels onto the bike.
- Pure excise. Actions nobody needs, beginner or expert. The book’s example is asking the user to pick a hardware port that the program could detect itself. The only right fix is to remove the step and let the system do it automatically.
- Visual excise. The work of decoding the screen: finding an item in a list, figuring out where to start reading, telling active elements from decoration. Heavy visual metaphors belong here too, such as a telephone, copier or filing cabinet drawn on screen. They help on day one, then waste space restating what users already know.
Keep the balance#
When reducing excise, don’t simply shift it from one group to another. Optimizing only for experts hurts beginners, and loading all the excise onto experts for beginners’ sake frustrates the experts. Either imbalance leaves part of the audience unhappy.
How to apply it#
- Walk the scenario step by step. For each step in a use case, user story flow or prototype, ask: does this move the user toward their goal, or does only the system need it?
- Label each step as goal, excise or beginner aid.
- Remove pure excise first. Replace it with automation, sensible defaults, remembered values or data the system already has.
- Reduce the remaining excise. Merge steps, prefill fields, shorten paths.
- Make beginner aids optional. Write requirements that let users skip or switch off wizards and hints.
- Put it into acceptance criteria. For example: “A returning customer can book a repair without re-entering bike details.”
Review checklist#
- Every step in the main flow serves the user’s goal or has a stated reason to exist.
- The system does not ask for anything it already knows or can detect.
- Defaults reflect the most common choice.
- Wizards and tips can be skipped or turned off.
- The screen makes clear where to start and which elements are active.
- Confirmations, forced sign-ups and re-entry steps are justified, not habitual.
Example#
The first booking prototype at The Workshop, a fictional chain of 12 bike-repair workshops, has nine steps: create an account, confirm the email address, choose one of the 12 workshops from a list, enter the bike’s make, model and size, choose a service type, choose a date, choose a time, review, and answer “Are you sure?”.
The analyst labels them. Choosing the service, date and time are goal steps. Creating and confirming an account before seeing any slots is excise. Picking from 12 workshops is excise the system can reduce by suggesting the nearest one. Re-entering the bike on every visit is pure excise for returning customers. The final “Are you sure?” adds nothing that the review step did not.
The revised flow puts service and date first and suggests the nearest workshop. Bike details are remembered, an account is offered after booking rather than before, and the confirmation message includes a cancel link instead of a dialog. Five steps remain, all of them goal-related.
Pitfalls#
- Treating every click as equal → count memory and learning costs, not just clicks.
- Keeping a wizard as the only path → offer a direct path for intermediates.
- Moving excise from customers to staff → check who absorbs the work you removed.
Sources and further reading#
- A. Cooper, R. Reimann, D. Cronin. About Face 3: The Essentials of Interaction Design. Wiley, 2007, ch. 11.