Complex products often have complex organisations behind them.

Multiple teams. Departments. Systems. Rules. Processes.

But users shouldn’t have to understand that structure just to complete a task.

They have a goal. Our job is to make the journey feel manageable.

Start with the goal

Instead of asking:

“What page should we design?”

Ask:

“What is this person trying to accomplish?”

Then work backwards:

Goal → Tasks → Journey → Interface

The interface is only one part of the experience.

Design the whole journey

Look beyond the screen.

Before → During → After

Where did the user come from?

What do they need to do next?

What happens if they get stuck?

Design the journey—not just the interface. 

Hide the complexity

Your internal structure might be complicated.

The user’s experience shouldn’t be.

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

They just need to get the job done.

Give users a way forward

A good service should always answer:

“What do I do next?”

Every error path needs a next step.

Don’t leave users at a dead end. 

The takeaway

Don’t just simplify the UI. Simplify the experience.