Designing for Every Mind: Cognitive Diversity for Platform UX

Designing for Ecosystems, Not Personas

Personas are useful tools for aligning product teams. However, for complex systems, they can oversimplify reality. Many platforms do not serve just a single type of user. Instead, they support entire ecosystems.

For example, an ecommerce platform might serve users in the following roles:

• customers browsing and purchasing products
• sellers managing product inventory and listings
• warehouse operators tracking stock movement
• delivery partners managing logistics
• customer-support agents resolving issues

Each of these types of users operates within a different context, uses different devices, and has different expectations of the system. Despite these differences, platforms often present uniform user interfaces or workflows, expecting them to work equally well for all users. This leads to friction because the needs of these various users are fundamentally different.

Designing for ecosystems requires understanding how users’ roles interact, where their journeys overlap, and where they diverge.

Lesson: Real-world platforms must serve users in multiple, interdependent roles.

Principle: UX design must support entire ecosystems, not just individual personas.

The Many Facets of Digital Literacy

Many treat digital literacy as a binary condition. They assume that users either are or are not tech savvy. In reality, digital literacy exists on a spectrum.

Some users hesitate before clicking a button because they fear making irreversible mistakes. Other users expect speed, shortcuts, and efficiency. In many cases, the same person might behave differently depending on the context, device, or urgency.

Designing for an assumed average user creates problems. Beginners feel uncertain and overwhelmed, while experienced users feel slowed down or even obstructed. Effective systems accommodate both ends of this literacy spectrum. They provide guidance, clarity, and reassurance for less experienced users, while enabling faster interactions for more experienced users.

This approach aligns with long-standing usability principles that emphasize reducing cognitive load and supporting different levels of user expertise, as researchers like Don Norman and Jakob Nielsen have discussed.

Lesson: Digital literacy is a fluid state and is context dependent.

Principle: Good systems build confidence for beginners while enabling efficiency for experts.

When Familiarity Outperforms Innovation

Many see innovation as an indicator of strong design. However, for task-oriented systems, familiarity often proves to be more effective.

On one project, I was designing a workflow for contractors who needed to add specific elements that would later become part of their contract. The existing system used a large, exhaustive form that included every possible variable, even though some were irrelevant for many contracts. Users had to scroll both vertically and horizontally to navigate through many unnecessary fields, making the user experience cumbersome to use.

To improve this user experience, I designed a dynamic list builder. Users could add only the relevant elements, modify them easily, and arrange them appropriately. This user interface was well structured, flexible, and significantly cleaner than the original form.

I was confident in this approach because I had implemented a similar solution for another global client. In that case, the users were government officials and policy makers working in structured environments, and the solution had improved efficiency.

However, this time, the context was very different. The contractors using this system were often working at construction sites or completing tasks after long work hours. Their environment, device constraints, and familiarity with digital tools differed significantly from those of the users for my previous project.

When we conducted usability testing, the results were clear: not a single participant could complete the task successfully. After multiple attempts and two or three hours into testing, one user asked a simple question: “Could we just have a table?” That table was exactly what I had tried to replace. We reverted to a table-based structure, and task completion improved immediately.

This experience reinforced a well-established usability principle: users rely on familiar patterns, especially when performing critical tasks. As Steve Krug famously emphasized in Don’t Make Me Think, users prefer user interfaces that are easy to understand with no additional effort.

Lesson: Users prefer familiar structures when completing important tasks.

Principle: When clarity and novelty compete, clarity should take precedence.

Navigating Design Trade-offs

UX design is rarely about finding perfect solutions. It is about choosing between design trade-offs.

While working on a job portal, I faced a common challenge. A shorter application form made it easier for candidates to apply, improving conversion rates, but left recruiters with insufficient information, increasing their effort in screening applications. Expanding the form improved the data quality for recruiters but led to higher drop-off rates among applicants. Both approaches solved one problem while creating another.

The final solution required balancing these competing user needs. We identified the most critical information that was necessary at the initial stage and deferred the gathering of additional details to later steps in the process.

This type of compromise reflects a broader principle in UX design: optimizing for one stakeholder often impacts another, requiring deliberate prioritization.

Lesson: Design problems often involve competing priorities.

Principle: Good UX design balances users’ needs, business goals, and operational efficiency.

Culture Shapes How Users Engage with Technology

Culture plays a significant role in how users interpret and interact with digital platforms. When designing for global audiences, two common approaches are translation and localization. Translation focuses on changing the language, while localization adapts the experience to cultural expectations, including visual design, content, and interaction patterns. Most platforms operate somewhere between these approaches.

Frameworks such as Hofstede’s Cultural Dimensions help explain how various cultures differ in areas such as decision-making, trust, and communication styles. These cultural differences have direct implications for design, as highlighted by the cross-cultural UX research of Aaron Marcus and others. Jo Chang’s UXmatters column, UX Across Cultures, often explores Hofstede’s cultural dimensions

The impacts of cultural context become clearer when we examine real-world examples. For instance, Gerber once introduced baby-food packaging that featured a smiling baby in markets where packaging typically represents a particular product. In regions with lower literacy levels, this led to confusion about what a product contained, a case frequently cited in international marketing literature.

Similarly, McDonald’s faced backlash in China for an advertisement that depicted kneeling as a humorous gesture. According to reports from China Daily, people perceived that posture as humiliating within their cultural context, leading to public criticism and an apology from the company.

Cultural differences are also visible within digital platforms. Comparing the Web sites of University of London and the Chinese University of Hong Kong reveals distinct design approaches that are shaped by cultural values. The former site emphasizes individual choice and direct action, while the latter reflects institutional identity and contextual richness. These differences align with broader patterns of individualism, hierarchy, and long-term orientation.

Lesson: Cultural context influences users’ perceptions, behaviors, and trust.

Principle: Global platforms must align with local cultural expectations.

Context Is Part of the User Interface

UX design exists not only for screens. It exists for the environments in which users interact with systems. Connectivity, device quality, lighting conditions, and time constraints all affect usability. A feature that performs well under ideal conditions might fail within constrained environments.

For example, users might struggle when using data-heavy user interfaces on low-bandwidth networks, and complex workflows might break down on smaller devices or under time pressure. This principle reinforces an important idea: usability is not just about user-interface design. It is about how well a system performs under real-world conditions.

Lesson: External conditions directly influence the user experience.

Principle: Treat context as an integral part of the user interface.

Such contextual factors often intersect rather than operate in isolation. Connectivity constraints can amplify usability challenges for low digital-literacy users, while cultural expectations could influence how users respond under time pressure. Mapping these overlapping conditions helps reveal where systems are most likely to fail in real-world scenarios, as Table 1 shows.

Conclusion: Designing for Real-World Complexity

While the idea of designing for an average user might seem convenient, it does not reflect reality. Modern platforms serve a wide range of users with various levels of digital literacy and different cultural backgrounds and environmental constraints. Designing for this diversity requires more than visual refinement. It requires understanding complexity and designing for it intentionally. In practice, this means questioning assumptions, validating decisions with real user feedback, and letting go of solutions that do not work in context.

Good UX design is not about validating design intent. It is about enabling users to succeed in their specific realities. The real challenge is not designing for users like us. It is designing for conditions that we may never fully experience.