Why Designers Fall Into the Exception Trap
When a designer sits down to sketch a navigation bar or draft a layout, the instinct is to solve the problem for the “edge case” that makes the project feel clever. That edge case often feels like a puzzle: “What if a user is browsing through a multi‑layered taxonomy? How do we keep the breadcrumb trail clear?” The idea of handling every possible scenario is tempting because it feels like we’re building something advanced, something that will impress stakeholders. In practice, it usually backfires. Users rarely encounter those edge cases. The real challenge is to create a straightforward experience that works for the majority, not the handful of super‑users who will read the breadcrumbs and navigate by them.
Design for the exception is easy to justify when you’re focused on metrics like click‑through rates or conversion funnels. You argue that a “rich” interface will differentiate your product, that a polished breadcrumb trail shows professionalism, or that an extra filtering option will help users discover content faster. Those arguments are valid, but they ignore the fact that most visitors have a single goal in mind: get to the information they need quickly and with minimal effort. When the interface is cluttered with optional features, that goal is drowned out.
Human factors research backs this up. Studies on information architecture consistently show that users prefer simplicity. They are willing to sacrifice a few advanced options for a layout that feels intuitive. A cluttered breadcrumb trail, for example, can appear as a breadcrumb trail, but it often becomes a list of links that users skim over because they aren’t sure which level they’re on. In contrast, a clean, minimal header or a single search field that is clearly labeled can capture attention immediately.
One common sign that a designer is trapped in the exception mindset is the presence of “nice to have” features that never get used. This was the case when I worked on a content management system that included a breadcrumb trail. The development team spent weeks crafting multiple breadcrumb scenarios to handle content that belonged to more than one category. We made a table of contents for each piece of content, decided how to display two parallel trails, and added an icon to toggle between them. It was a great demonstration of our coding prowess. When the system went live, the analytics dashboard showed that less than 5 % of visitors ever clicked on a breadcrumb link. The rest of the time, they either clicked the home button or used the search field. The extra code and design work had added complexity without a corresponding benefit.
The temptation to design for the exception also shows up in the way we label things. Designers love to call a feature a “breadcrumb” because it sounds technical and sophisticated. Users, however, might think it’s a navigation aid that they need to understand. If a feature has a name that is unfamiliar, users can become confused. The more we lean on jargon, the more we distance ourselves from the everyday language of our audience. By focusing on what users actually see and do, we can strip away the unnecessary terminology and create a design that feels natural.
Finally, there is a cognitive cost. The brain prefers patterns that it recognizes. When a designer adds a new element - whether a breadcrumb trail, a pop‑up, or a mega‑menu - users have to process that new element. They need to decide whether it’s relevant to their task, whether it can be ignored, and how it fits into the overall flow. If the element is an exception, it can become a cognitive interrupt that slows down the user. The exception traps the designer in a loop of “how do I make this optional without making it disappear?” The answer is to remove the option entirely. Design is about trade‑offs; if a feature isn’t essential for the majority, it should be left out.
Breadcrumbs: A Case Study in Over‑Engineering
Breadcrumb navigation has a solid pedigree in web design. The idea is simple: show the user the path they took to arrive at the current page, so they can retrace their steps or jump to a higher level. The concept works well when the navigation hierarchy is flat and well‑structured. However, when the hierarchy is deep, ambiguous, or multi‑dimensional, the breadcrumb can become a source of confusion rather than clarity.
During the development of our content management system, we had to decide how to handle content that belonged to two different categories. In a single‑category world, a breadcrumb might look like this: Home > Category > Sub‑category > Article. In a multi‑category world, the breadcrumb could branch: Home > Category A > Sub‑category A > Article and Home > Category B > Sub‑category B > Article. We built a JavaScript component that rendered both paths side by side, separated by a line. The component also included an icon that allowed users to toggle between the two paths. We wrote unit tests for each scenario, and the team celebrated the successful integration.
What we didn’t anticipate was how rarely users would interact with this component. Most visitors never clicked on the toggle icon. Instead, they used the search field at the top of the page or clicked the home button to start over. The analytics report that followed revealed that the breadcrumb trail accounted for less than 1 % of click‑throughs. The extra code added to the build process and the potential for bugs in a production environment were not justified by the negligible engagement.
Dr. Eric Schaffer, CEO of Human Factors International, discusses breadcrumbs in several studies. He acknowledges that they “increase efficiency” and “support site learning,” but he also notes that users do not use them spontaneously. The data suggests that only “super users” - those who are highly experienced with the site - find breadcrumbs useful. The majority of visitors, however, rely on other navigation cues: the top menu, search boxes, or even the browser’s back button. This mismatch highlights a key point: a feature that satisfies a niche group is not necessarily valuable to the broader audience.
Breadcrumbs can also become a visual clutter in modern responsive design. On mobile devices, screen real estate is precious. A breadcrumb trail that expands to multiple lines can break the layout and push content further down. Users on mobile devices tend to prefer simple, touch‑friendly navigation like a hamburger menu or a back button. In our case, we found that reducing the breadcrumb to a single line - just the current page title - improved the user experience on mobile devices without sacrificing navigation clarity.
In short, the breadcrumb case study illustrates how over‑engineering a feature that is already well‑known and well‑tested can lead to wasted effort. It also shows that the most “advanced” design solutions are not always the most effective. By focusing on the actual usage patterns and removing features that are rarely interacted with, we simplified the code base, improved performance, and made the interface more approachable for the average user.
Keeping the Design Simple and User‑Friendly
When you strip away the bells and whistles, a good web design boils down to a handful of core principles: clarity, predictability, and efficiency. The most common mistake is to add complexity in the name of sophistication. The opposite - designing for the obvious - means building an interface that feels familiar and solves the user’s problem without forcing them to learn a new set of conventions.
Start with a clear goal statement. Ask yourself, “What is the primary task the visitor should accomplish on this page?” The design should funnel the user toward that goal. For instance, eBay uses a single, prominently placed search box labeled “What are you looking for?” and a button labeled “Search.” This design removes the need to explain the function. The user knows exactly what to do: type a keyword and press the button. That’s the power of the obvious.
Use familiar patterns that people already know. The navigation bar, for example, should list top‑level categories, not a dozen obscure sub‑menus. If you need to display a large set of options, consider a dropdown that is triggered by hovering or clicking. The key is that the pattern should match user expectations. A common mistake is to create custom navigation widgets that behave differently from what users anticipate, causing them to double‑click or get lost.
Keep visual hierarchy simple. Use bold headings for main sections, and smaller text for secondary information. Avoid too many fonts or colors that can distract from the main content. A clean, minimalist aesthetic often helps users focus on what matters. When the design is too busy, users can feel overwhelmed and disengage before they even reach the content.
Another area where many designers slip into the exception trap is in the use of forms. A form that is overly long or includes fields that aren’t mandatory forces users to fill in unnecessary information. One strategy is to ask for the minimum required data and then provide optional fields in a collapsible section. That way, users who need to provide more detail can do so, but the majority won’t be confronted with extra fields. In practice, this reduces form abandonment rates by up to 20 %.
Test your design with real users. A/B testing different layouts can reveal which version leads to higher conversion or lower bounce rates. If a feature you think is essential doesn’t actually improve performance, consider removing it. The goal is to create an interface that works for the widest audience, not to showcase technical prowess.
When you encounter a feature that’s rarely used - like the breadcrumb trail in our content management system - evaluate its value from the user’s perspective. If only 5 % of visitors interact with it, it’s probably safe to remove it from the production build. Not only does that streamline the code, but it also cleans up the visual space, making the rest of the interface more prominent.
Design is a constant balancing act. The most successful designs are those that prioritize the user’s mental model over the designer’s love of novelty. By focusing on the obvious - providing clear labels, familiar navigation, and a single, well‑placed search field - you can create a site that feels intuitive to both casual visitors and power users alike.
For a web content management solution that emphasizes usability over bells and whistles, contact Gerry McGovern at New Thinking Newsletter for ongoing insights and best practices.
No comments yet. Be the first to comment!