A beautiful interface can still create a terrible experience.

Why?

Because users don’t experience a screen in isolation. They experience the entire journey around it. 

Think about a public service.

A person may need to search for information, complete a form, provide documents, wait for verification, get support, and eventually reach an outcome.

The interface is only one part of that experience.

Start With the Person

The French public-service example in this episode presents a different starting point:

Start with the person, not the interface.

Understand their needs.
Make the service simple.
Make it inclusive.
Test it with real users.
Then improve it. 

That changes the question designers ask.

Instead of:

“How do we make this screen easier?”

Ask:

“What is the person actually trying to accomplish?”

Then investigate what happens before the screen, after it, where people get stuck, what other channels are involved, and what happens when something goes wrong. 

Hide the Complexity

Users shouldn’t have to understand how an organisation works to use its service.

They don’t need to know which team owns a process, which system stores their data, or which department handles the next step.

That complexity belongs behind the experience. 

Inclusion Is Part of UX

“Inclusive” shouldn’t be a final checkbox.

The better question is:

Can everyone actually use this?

Design for real life—not an idealised user. Consider different abilities, devices, levels of confidence, contexts, and ways people may need help. 

Test Before You Polish

Instead of debating whether a design is “better,” test it.

Define what you need to learn.
Test with real users.
Observe where they struggle.
Identify actionable insights.
Improve.
Test again.

Evidence beats opinions. 

The Public-Service UX Lens

A simple framework from this episode:

1. NEED — What is the person actually trying to achieve?
2. JOURNEY — What happens from start to finish?
3. INCLUDE — Who could struggle or be excluded?
4. TEST — What happens when real people use it?
5. IMPROVE — What does the evidence tell us to change?

Before shipping a complex service, ask:

Have we identified the real user need?Have we looked beyond the screen?Can users complete the journey from start to finish?Have we removed unnecessary complexity?Can people with different abilities and circumstances use it?Have we tested with real users?Are we improving based on evidence? 

Because if you only improve the interface, you might be polishing the wrong problem.

Don’t just design the interface. Design the journey.