Skip to content
Fast Company Executive Board

The Fast Company Executive Board is a private, fee-based network of influential leaders, experts, executives, and entrepreneurs who share their insights with our audience.

Designing for the real world: How to build interfaces people love to use

In reality, user experience unfolds across noisy subways, cracked screens, low bandwidth, and moments of frustration, fatigue, or multitasking.

Designing for the real world: How to build interfaces people love to use

[Nour Studio / Adobe Stock]

Profile photo of Goran Paun

Principal, Creative Director · ArtVersion

Most digital products (including websites) are designed under ideal circumstances. Good Wi-Fi, high-resolution displays, full battery life, and focused users in quiet environments. Interfaces are prototyped on crisp monitors with fast internet and perfect lighting. Testers follow clear instructions in usability labs and edge cases are treated as exceptions.

But anyone who’s built digital products at scale knows: Real life doesn’t work that way.

In reality, user experience unfolds across noisy subways, cracked screens, low bandwidth, and moments of frustration, fatigue, or multitasking. Designing for the average user results in a product that fails many people in common, everyday contexts.

THE FALSE ASSUMPTION OF OPTIMAL CONDITIONS

Designing under the assumption of optimal user conditions can lead to a cascade of blind spots. For example, you might design assuming everyone uses a desktop, when many rely solely on mobile. Over 60% of global internet users access the web primarily through mobile devices—many of them exclusively using their phones.

Another example is assuming consistent lighting. Glare and low-light environments are common, not just in offices where screens sit next to oversized windows, but also in users’ hands. Just think of your own daily routine: Assuming full attention spans is unrealistic—people are often distracted, rushed, or stressed—and browsing for a piece of information on the fly is more common than not.

In usability testing, even the best-designed flows can falter in unideal contexts. Take a simple login screen: It can quickly become a source of frustration if someone is trying to enter a password while standing in a crowded train with limited dexterity. Temporary visual challenges—like sunlight glare on the screen—can make it even harder. And, just when you think you’re done, a two-factor authentication step suddenly pops up. This scenario is all too common.

WHAT UX DESIGNERS NEED TO UNDERSTAND ABOUT REAL USERS

To make interfaces that actually work for people, we have to accept that things aren’t always neat or predictable. Real usability means digging into the mess—different devices, different environments, different moods—and designing in a way that brings clarity out of all that chaos.

So what’s the way to get there? Start by listening, testing in the wild, and being OK with scrapping things that look good but don’t feel right.

Different Contexts

People don’t always use websites the way you want them to. Someone might look at a dashboard for a short time between meetings. Another might use a shopping app during a lunch break. A student might use an older tablet with cracked glass to get to an educational site.

When making design choices, you should always consider, “Will this work in a messy real-world setting?” Can someone do this job swiftly, with confidence, and without second-guessing themselves?

Fragmentation of Devices

Not everyone has the newest phone or a powerful laptop. A lot of people utilize mid-range mobile devices, shared laptops, or public Wi-Fi, so your design must adapt. It’s not only about making a screen smaller; it’s about putting material and functions in a different order depending on the situation.

Network Inconsistency and Load-Speed

Assuming fast internet can be a major flaw in UX thinking. Users frequently experience latency, dropped connections, or limited data plans. Progressive loading, offline states, and caching aren’t just technical features—they’re part of the user experience.

When users are stranded on a screen with a spinner and no feedback, they don’t just blame the connection—they blame the app.

Cognitive Load and Emotional State

Users come with emotions. Anxious, tired, impatient, skeptical. When you design for empathy, you think about how they will feel and what they will think.

Reducing cognitive load through better UI hierarchy, progressive disclosures, and forgiving flows (like undo, autosave, or re-entry options) can be the difference between delight and abandonment.

Accessibility and Inclusion

Temporary, situational, and permanent impairments all affect interaction. Bright sunlight can impair vision. Holding a child can limit input ability. Dyslexia, ADHD, or anxiety may affect comprehension.

Accessibility is about respect and usefulness, and UX that works for someone with a disability often works better for everyone.

METHODS FOR DESIGNING BEYOND IDEAL SCENARIOS

Recognizing the problem is just the first step. The real work starts here:

• Contextual inquiry: Observe users in their environment, not in labs. It provides you with insight into physical, emotional, and environmental constraints, and exposes how your product lives in their broader ecosystem.

• Stress-testing designs: Try using your app on 3G. On a cracked screen. With gloves. In a hurry. With your eyes closed (screen readers). These friction tests show flaws in the experience that controlled settings hide.

• Inclusive personas: We all know “happy-path personas” don’t work. Include edge cases: someone with low literacy, someone using a screen reader, someone using the product with one hand.

• Accessibility audits: Conduct real accessibility audits using tools like WAVE or Axe, but also with human testers who rely on assistive technologies.

• Error-state and empty-state design: Most designs focus on success scenarios, but UX maturity shows in how a product handles what’s missing, broken, or misunderstood. A simple error message or a well-thought-out onboarding process for an empty dashboard can help users feel better about using it.

• Mobile-first and offline-first design: Starting design from the most constrained environments forces better prioritization. If it works on a low-end mobile device with no network, it will work anywhere.

RETHINKING SUCCESS IN UX

When we measure success, metrics like conversion rate or bounce rate matter—but so does user confidence. Can they recover from mistakes? Do they feel in control?

When you design for real-world cases, recognize that you can’t make everything work perfectly, but you can make your design system flexible. Modular UI elements, robust feedback loops, and a strong information architecture all help users succeed despite messy real-world conditions.

The next time a stakeholder asks, “Why would anyone do it that way?”—pause. Maybe they wouldn’t—in a usability lab. But in real life? People move fast, make mistakes, and just want things to work.