Good IA reduces thinking, bad IA creates it

You land on a page, start moving through it, and everything feels straightforward. You don’t have to stop and work things out. You don’t have to double-check what something means. You just move.

Then there are other times where it’s the opposite.

You’re not stuck, exactly. Nothing is completely broken. But you find yourself pausing. Reading something twice. Hovering for a second longer than you should. Trying to make sure you’ve understood what’s in front of you before committing to the next step.

That’s thinking.

And most of the time, it’s unnecessary.

Good information architectureservice×Information ArchitectureImprove navigation, content structure, and findability so users can understand where things are and how to move through them.Open service→ removes that burden almost entirely.

When a systemglossary×SystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term→ is structured well, users don’t feel like they’re navigating it.

They feel like they’re progressing through something that makes sense.

Each step follows naturally from the last. The way things are grouped feels predictable. The labels don’t need interpreting. You don’t have to ask yourself, is this the right place because it’s already obvious.

You’re not making decisions about the systemglossary×SystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term→.

You’re focusing on what you came there to do.

That’s usually the point people miss.

IA isn’t just about organising content neatly.

It’s about reducing the amount of thinking required to use something.

And when it’s done well, it almost disappears.

I’ve watched users move through well-structured journeysglossary×Pain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term→ without saying much at all. No commentary, no hesitation, no need to explain what they’re doing. They just move from one step to the next, completing what they came to do without frictionglossary×FrictionFriction refers to anything that slows users down or makes it harder for them to complete a task. It can be caused by poor design, unnecessary steps, unclear messaging, or technical issues.Open glossary term→.

If you asked them afterwards, they probably wouldn’t describe it as exceptional.

They’d say it was easy.

That’s usually the best outcome.

Because the goal isn’t to impress people with how something is structured.

It’s to remove the need for them to think about it in the first place.

Bad information architectureservice×Information ArchitectureImprove navigation, content structure, and findability so users can understand where things are and how to move through them.Open service→ does the opposite.

It forces users to interpret things that should be obvious.

They have to work out where something might live.

They have to translate internal language into something that makes sense to them.

They have to decide between options that aren’t clearly distinct.

None of that is part of their goal.

It’s effort created by the systemglossary×SystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term→.

And it adds up quickly.

A single moment of hesitation doesn’t seem like much.

But when it happens repeatedly, across a journeyglossary×Pain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term→, it starts to change how the whole experience feels. What should be simple becomes tiring. What should be obvious becomes something you have to double-check.

Confidenceglossary×ConfidenceConfidence is the level of certainty in a decision or outcome based on available evidence.Open glossary term→ drops.

And when confidenceglossary×ConfidenceConfidence is the level of certainty in a decision or outcome based on available evidence.Open glossary term→ drops, behaviourglossary×BehaviourBehaviour refers to how users interact with a system, including actions, patterns, and responses.Open glossary term→ changes.

Users slow down.

They backtrack.

They abandon things they would have completed if it had felt easier.

Not because they can’t do it.

Because it’s asking too much of them.

That’s the real cost of poor IA.

It’s not always visible in a single interactionglossary×InteractionInteraction refers to any action a user takes within a product and how the system responds. It includes clicks, taps, gestures, and inputs that drive the user experience.Open glossary term→.

It shows up in accumulation.

I’ve seen teams try to solve this by adding more guidance. More labels, more explanations, more options to make things clearer. But that often makes things worse.

Because it increases the amount of thinking, not reduces it.

Clarityglossary×ClarityClarity is how easily users can understand what is happening and what they need to do.Open glossary term→ doesn’t come from adding more.

It comes from organising things properly in the first place.

When the structure is right, you don’t need to explain it.

It explains itself.

And that’s usually the signal you’ve got it right.

Not when users say it’s clever.

Not when stakeholdersglossary×StakeholderA stakeholder is any individual or group with an interest in a product, project, or outcome, including internal teams and external parties.Open glossary term→ say it looks neat.

But when no one has to stop and think about how it works.

Because good information architectureservice×Information ArchitectureImprove navigation, content structure, and findability so users can understand where things are and how to move through them.Open service→ doesn’t demand attention.

It quietly removes the need for it.