Designing With Real Users in Mind

This entry is part 5 of 5 in the series May 2026 - Accessibility and Inclusion

It is possible to design a system that works perfectly — and still fails its users.

The logic is sound.The features are complete.The interface is functional.

And yet, something does not connect.

Users struggle.Tasks take longer than expected.Confusion replaces clarity.

The problem is rarely technical failure. It is often a failure of perspective.

Designing with real users in mind means moving beyond assumptions and engaging with reality.


The Problem With Assumed Users

Every system begins with assumptions.

We imagine how people will interact.We predict behaviour.We define workflows.

These assumptions are necessary. But they are limited.

They are shaped by our own experiences, habits, and expectations. When left unchallenged, they produce systems that reflect the designer more than the user.

This is where problems begin.


Real Users Are Not Ideal Users

Design often starts with an “ideal user” in mind.

Someone who:

  • understands the system,
  • follows intended paths,
  • and interacts as expected.

Real users are different.

They:

  • skip instructions,
  • misunderstand labels,
  • use systems in unexpected ways,
  • and bring diverse needs and constraints.

Design that works only for ideal users is fragile.


Observing Reality

Designing for real users requires observation.

Not speculation.Not assumption.Observation.

This includes:

  • watching how users interact with systems,
  • identifying where confusion occurs,
  • and noticing patterns of behaviour.

These insights reveal gaps between intention and experience.


Simplicity Through Understanding

Simplicity is often misunderstood.

It is not about removing features arbitrarily. It is about reducing unnecessary complexity in ways that make sense to users.

When design aligns with real behaviour, systems become more intuitive.

Buttons are where users expect them.Language reflects user understanding.Workflows follow natural patterns.

This kind of simplicity is achieved through understanding, not reduction alone.


Designing for Constraints

Real users operate within constraints.

Limited time.Limited attention.Limited familiarity with the system.

Design must account for these realities.

This includes:

  • minimising required steps,
  • providing clear guidance,
  • and avoiding unnecessary friction.

Constraint-aware design respects the context in which systems are used.


Feedback as Insight

User feedback is one of the most valuable tools in design.

It highlights:

  • points of confusion,
  • unexpected behaviours,
  • and unmet needs.

But feedback must be interpreted carefully.

Users may not always articulate the problem clearly. Their solutions may not address the root issue. But their experience is real.

Listening to feedback — and investigating it — leads to better design.


Testing Beyond Completion

Design is often considered complete once a system is built.

But real understanding comes through testing.

Testing with real users reveals:

  • where assumptions fail,
  • where instructions are unclear,
  • and where workflows break down.

This process is not a final step. It is ongoing.


Empathy in Practice

Designing with real users in mind requires empathy.

Not as a vague concept, but as a practical discipline.

It involves:

  • considering different perspectives,
  • acknowledging limitations,
  • and adapting accordingly.

Empathy moves design from self-referential to user-centred.


Avoiding Over-Design

Sometimes, in trying to accommodate every possibility, systems become overly complex.

Multiple options.Layered features.Extended workflows.

While well-intentioned, this can overwhelm users.

Designing for real users includes knowing when to simplify — not by removing necessary functionality, but by focusing on what matters most.


Clarity Over Creativity

Creative design can be valuable.

But clarity must come first.

Users should not need to interpret or guess. Interfaces should communicate directly.

Clarity reduces friction. It builds confidence.


Iteration as Responsibility

Designing for real users is not a one-time effort.

It requires iteration:

  • observe,
  • adjust,
  • test,
  • refine.

This cycle ensures that systems continue to align with real usage.


Building Systems That Serve

In a month focused on accessibility and inclusion, designing with real users in mind is essential.

It ensures that systems:

  • are usable,
  • are understandable,
  • and are effective.

It moves design from assumption to reality.


A Better Way to Design

Design is not about imposing structure.

It is about enabling interaction.

When systems are designed with real users in mind, they become:

  • more accessible,
  • more inclusive,
  • and more reliable.

Choosing Reality Over Assumption

Every design decision reflects a choice.

Do we design based on what we expect —or what actually happens?

Real users reveal the difference.

And designing for them leads to systems that truly work.

May 2026 - Accessibility and Inclusion

Welcoming the Margins (Mark 10:13–16)