Designed so that customers don't have to strain their brains
When the interface makes customers think too much, they do not buy, do not fill out forms, and do not proceed. This is how Sinh Vũ resolves that.
Cognitive load is the amount of mental effort the interface requires from customers, and when it is too high, customers exit instead of trying. Reduce it through three approaches: minimize visual noise, rely on what customers are familiar with, and take on some of the work for them. It’s not about designing something eye-catching; it’s about designing in the right places.
- long content that should be broken into sections, with headings and bullet points for easy scanning
- multi-step forms or processes need to be pre-filled and suggested
- a screen with multiple options for attention that needs to be trimmed or grouped
- create unconventional interaction methods that force customers to relearn from scratch
- require customers to remember information from the previous step instead of displaying it again
When you visit a page and do nothing, it's often not because you aren't interested. A more common reason is that your brain has to process too many things at once, and instead of pushing through, you exit. This is a phenomenon of high cognitive load, and it occurs silently without any error notifications.
What is cognitive load?
Human short-term memory is very limited. The brain can only hold a certain amount of information at one time, and as the interface continuously adds more, it starts to drop off. Customers do not fill out forms not because they are lazy, but because the form is asking too many unrelated things, lacks prompts, and presents as a solid block of text.
Cognitive load comes from three main sources, all of which fall within the realm of design that can be intervened in:
- Visual noise: too many elements competing for attention at once on a screen.
- It is mandatory for customers to remember instead of recognizing: necessary information is not displayed in the right place.
- Request involves too many steps of thought in one action.
Three directions for realistic reduction
The Nielsen Norman Group summarizes three main ways to reduce cognitive load. These are avoiding visual clutter, building on existing mental models, and offloading some tasks from the customer's mind. Sinh Vũ employs all three methods when constructing information architecture.
Let customers recognize: Necessary information should be displayed in the right places. The menu should have available options, forms should pre-fill what can be inferred, and always show customers where they are in the total number of steps. The brain does not need to remember because the eyes have seen.
Chunking: the simplest tool
Chunking is the method of grouping separate pieces of information into meaningful units. Instead of a solid block of text, you should divide it into groups with clear headings, allowing your brain to scan rather than read each line.
The important principle here is that the structure must be meaningful, not rigid numbers. Do not force everything into a fixed quantity, but group logically: items that belong together should stand next to each other, while those serving different steps should be separated. When information is grouped correctly, customers can quickly scan and know which part they need.
Common errors in flow design
- A block of text without line breaks or headings: customers feel uneasy just by looking at it, wanting to exit before even reading.
- It is mandatory for customers to remember information from the previous step without displaying it again: this creates unnecessary bottlenecks.
- Stuffing too many equal choices onto one screen: customers don’t know what to prioritize, resulting in choosing nothing.
- Create unconventional interaction methods: make customers learn from scratch instead of using what they are familiar with.
The final error is particularly noteworthy. Creativity in interactive design should only appear when there is a valid reason. When there is no such reason, sticking to familiar conventions is a less taxing choice for customers and carries less risk for you.
The viewpoint of Sinh Vũ
Reducing cognitive load is not just the responsibility of the technical department, nor is it solely about colors and fonts. It involves experience design and information architecture. Specifically, it means organizing content in a way that makes sense to you, clearly grouping items, and ensuring each page only requires what is necessary for that step.
Each screen should have a primary goal. If you cannot answer the question "What does the customer need to do here?", then that screen is forcing the customer to find the answer themselves. That is unnecessary cognitive load.
Users should not have to remember information from one part of the interface to another. Options, actions, and subjects should all be displayed or easily found.
Nielsen Norman Group, 10 Usability Heuristics for User Interface Design
When Sinh Vũ builds the information architecture for a digital experience, the important question is: at each step, what do customers need to know and what do they need to do? And how can we make those two things as clear as possible? This is the underlying thread throughout Sinh Vũ's approach to experience design.
Decision checklist
Topic: Reducing cognitive load for customers in digital experiences. Sinh Vũ guide, sinhvu.com
Tick each item that applies or that you can already answer, then print or save as PDF to take with you.
If you have marked most of the signs above, this is the time to discuss in more detail. Sinh Vũ can help you review and propose a direction.
References
Nielsen Norman Group, What Is Cognitive Load?; Nielsen Norman Group, 10 Usability Heuristics for User Interface Design; Nielsen Norman Group, How Chunking Helps Content Processing; Sinh Vũ's practical experience.
Frequently asked questions
Does reducing cognitive load mean designing simply and minimally?
Not necessarily. Visual simplicity is part of it. But reducing cognitive load also includes grouping information correctly, displaying what customers need instead of making them remember, and adhering to familiar conventions. A page with a lot of content can still be easy on the brain if structured well.
When do you know the interface is making customers think too much?
The clearest sign is a high exit rate in the middle of the flow, or customers having to ask about things already displayed on the screen. You can also observe directly: if someone looks at the page for more than three seconds without knowing where to click, there is a cognitive load issue.
Is cognitive load related to content or design?
Both, and the boundaries are often blurred. A long block of text that doesn't break is a content formatting issue. A menu with fifteen equal items is an information architecture issue. Asking customers to remember a cart code from the previous step is a design flow issue. Sinh Vũ looks at all three layers simultaneously rather than separately.
This article is for reference. The scope, pricing, and specific commitments of Sinh Vũ are detailed in the proposal and signed contract.