Key takeaway (TL;DR)
Performance load is the combined cost of perception, memory, reasoning and physical action required to reach a goal. It is usually divided into cognitive load and motor load. JVDS believes interaction design should not be optimized solely by counting clicks. It should reduce the effort of remembering and deciding while also removing unnecessary movement and repetitive actions, seeking the best overall performance.
2. Two kinds of load: how thinking and movement work together
Every interaction requires both mental and physical effort. Total performance load has two complementary branches:
- Cognitive load — the cost of thinking and memory:
- Recognizing cues: can users quickly identify meaning through understandable icons and hierarchy, or must they search laboriously?
- Mental calculation and inference: must users remember values from the previous page, calculate a discount rate mentally or decipher obscure terminology?
- Motor load — the cost of physical action:
- Pointer movement: how far must the cursor travel between opposite sides of the screen, and how large are the effective targets?
- Keystrokes: are users forced to copy company details or identification numbers that already exist elsewhere?
- Cognitive load: remove unnecessary dependence on memory. The shift from DOS command lines to graphical interfaces illustrates a reduction in recall demands. Command lines require users to remember commands and parameters; icons and menus turn difficult recall into visible recognition. Requiring someone to remember an order number across pages or calculate a complex discount unaided adds unnecessary cognitive work.
- Motor load: optimize the physical path. This includes typing, long pointer movements, swiping and switching between input devices. Morse code gives the frequently used letter E a single dot and the rarer Q a longer pattern. Similarly, frequently used interface actions should require short movement paths and little gesture effort.
- The tradeoff between the two: reducing physical actions does not automatically reduce overall load. Replacing five clearly structured controls with one free-text field may remove clicks but require users to remember syntax, separators and ordering. The extra mental effort can outweigh the physical saving.
3. Lessons from real-world reductions in both kinds of load
Industrial design and digital hardware provide examples of reducing cognitive and motor effort together:
- Barcodes and scanning: before scanning, cashiers had to find a product label, read the price, type it and perform calculations. Barcode systems automate recognition, lookup, calculation and inventory matching, reducing mental work and bringing individual item entry below half a second.
- Remote keys and keyless entry: a mechanical key requires approaching the door, aligning a small keyhole and turning the lock. A remote needs only a button press; a proximity system can unlock when the owner carrying the key reaches the handle, removing much of the deliberate action and attention.
- Browser bookmarks and autocomplete: rather than memorize a URL containing more than twenty arbitrary characters, users select a visual bookmark or type a few initial characters. The system retrieves the address from history, transferring the memory task to the database.
4. A four-dimensional comparison for managing performance load
The following matrix helps teams make informed simplification decisions in UI/UX design and product architecture:
| Evaluation dimension | Core functions or practices | Occasional supporting functions | Unnecessary burden or false simplification |
|---|---|---|---|
| Recognition and memory | Expose important states, use familiar visual cues and group information clearly. | Reveal specialist metrics through a detail tooltip or an on-demand panel. | Require users to write down a previous calculation merely to complete the next step. |
| Action paths and movement | Use appropriately sized targets and nearby contextual actions in line with Fitts's law. | Offer keyboard shortcuts and a global command palette, such as Command+K, for advanced functions. | Place Save in an obscure corner or force repeated movement between dialogs. |
| Data input and automation | Provide useful prefill, remembered addresses and OCR extraction of business-license information. | Support CSV or Excel validation and downloadable templates for bulk uploads. | Make users manually retype company information already available inside the system. |
| Tradeoffs and validation | Reduce physical actions while retaining an understandable mental model and checks at important points. | Provide outcome previews and reversible actions for high-risk financial or data-removal operations. | Remove a necessary verification merely to save one click, causing anxiety and hesitation. |
5. Performance-oriented design in JVDS practice
In enterprise administration platforms and digital brand solutions, JVDS applies ergonomic and cognitive principles:
- Observe thinking time separately from action time: eye tracking and screen recordings help identify where a user pauses to calculate or interpret information and where the pointer repeatedly travels across the screen searching for a control. Different bottlenecks call for different changes.
- Use progressive disclosure: keep the decision cues needed for the 80% of frequent scenarios visible, while placing the 20% of infrequent advanced configuration in secondary structures. This supports a lighter entry experience without removing expert capability.
- Connect the system as a whole: shared design systems align front-end components with prototype assets so interactions remain consistent and predictable across the site. Explore our design work for experience improvements in demanding business systems.
6. Frequently asked questions
Q1: Why is fewer clicks not a sufficient measure of interaction quality?
Physical savings can come at a substantial mental cost. Combining a clear three-step wizard into one dense form with thirty complex fields increases scanning effort, interpretation demands and the risk of omission. Good simplification balances thinking and acting rather than minimizing either in isolation.
Q2: How can mobile interfaces reduce motor load?
Use comfortable thumb reach and appropriate gestures. Place frequent primary actions such as submit, confirm and filter in reachable lower-screen areas. Provide suitable swipe-back or paging gestures to reduce dependence on a small top-corner target, and enlarge the effective touch area around small interactive elements.
Q3: How do we tell whether automatic prefill helps or creates more work?
Assess accuracy and transparency. A likely correct city or familiar recipient can reduce effort when the user can quickly change it. If the system guesses in uncertain situations and makes users inspect, erase and re-enter the result, automation becomes interference.
