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.
When clients enter your page and do nothing, the reason is often not that they are uninterested. A more common reason is that their brains have to process too many things at once, and instead of pushing through, they exit. This is a phenomenon of high cognitive load, and it occurs silently without any error notifications.
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:
Nielsen Norman Group summarizes three main ways to reduce cognitive load: avoiding visual clutter, building on existing mental models, and offloading tasks from the user's mind. Sinh Vũ employs all three in the information architecture process.
Chunking is the method of grouping separate pieces of information into meaningful units. Instead of a solid block of text, you break it into groups with clear headings, allowing the customer's brain to scan rather than read line by 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.
The final error is particularly noteworthy. Creativity in interactive design should only appear when there is a valid reason. In the absence of that reason, sticking to familiar conventions is a less stressful choice for customers and carries less risk for you.
Reducing cognitive load is not just the responsibility of the technical department, nor is it only about colors and fonts. It pertains to experience design and information architecture: organizing content in a way that makes sense to customers, clearly grouping items, and ensuring each page only requires what is necessary for that step.
Each screen should have a primary objective. 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, which 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ũ develops the information architecture for a digital experience, the question is not "how much content to include" but rather "at each step, what does the customer need to know and what do they need to do, and how can we make both as clear as possible?" This is the underlying principle throughout Sinh Vũ's approach to experience design.
Topic: Reducing cognitive load for customers in digital experiences. Sinh Vũ guide, sinhvu.com
Select each item you find appropriate, 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.
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.
Not necessarily. Visual simplicity is part of it, but reducing cognitive load also includes grouping information correctly, displaying what the customer needs instead of making them remember, and adhering to familiar conventions. A page with a lot of content can still be easy to digest if well-structured.
The clearest sign is a high dropout rate in the middle of the flow, or customers having to ask about things that were 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.
Both. The boundary is 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 the cart code from the previous step is a design flow issue. Sinh Vũ looks at these three layers simultaneously instead of separately.