Menu

IA

Taxonomy Design

A practical information architecture method for creating clear, scalable structures that organise content in ways users can actually navigate.

How to use taxonomy design to create categories, relationships, and naming systems that make content easier to organise, scale, and find.

4 min read

What it is

design is the of organising content, products, or information into a clear, logical structure.

It defines how things are grouped, labelled, and related to each other across a .

This includes categories, subcategories, tags, filters, and naming conventions.

Unlike or testing methods, design is about creating the structure itself, often informed by and data.

The goal is to create a that is easy to navigate, scalable, and aligned with how users think.

Taxonomy design is most useful when the problem is not just confusing labels or broken paths, but the lack of a coherent structure underneath the whole system.

When to use it

Use this method when structure and organisation are critical.

It is most useful when:

You are designing or restructuring a large content set
Users struggle to find things
You are building navigation, filters, or search systems
You are scaling a product or content platform
You need consistency across a system

It is less useful when:

Content is small or simple
You have not yet understood user behaviour
You need to validate rather than create structure
Taxonomy design is often informed by card sorting, tree testing, and analytics.

Key takeaway

Use taxonomy design when you need to create a durable structure that can support navigation, labelling, search, and growth across the whole system.

How to run it

Set up properly

Be clear on what needs organising, what people are trying to do with it, and what you are working inside: existing , editorial capacity, legacy URLs.

Gather the and first. A designed from the org chart will reflect the org chart, and users do not work there.

Run the method

design is structured and iterative. You are building a that has to survive content nobody has written yet, which makes it as much a forecasting exercise as a design one.

  1. Audit what exists before you categorise anything. You cannot design a structure for content you have not counted.
  2. Group items into categories that reflect how people look for them rather than how the business produces them.
  3. Define the and the relationships, including where something legitimately belongs in two places. Pretending everything has one home is what breaks later.
  4. Create labels that are consistent in form as well as wording: all nouns or all verbs, one level of specificity, no internal jargon.
  5. Test the structure with real users and real tasks, then revise. A that has never been tested is a .

Focus on simplicity and together. The test of a is not whether today's content fits, but whether next year's content has an obvious home.

Capture and make sense of it

The value comes from creating . Check the structure against:

  • Whether categories make sense to users rather than only to the team
  • Whether the is shallow enough to navigate confidently
  • Whether labels are clear, consistent and free of internal language
  • Whether the absorbs new content without a special case

Refine based on testing and , and write down the rules you applied. An undocumented drifts within two content cycles.

What to look for

Focus on:

Structure: logical grouping and hierarchy
Clarity: easy-to-understand categories
Consistency: alignment across the system
Future fit: whether next year's content has an obvious home
Findability: how easily users locate content

Where it goes wrong

Most issues come from:

If the structure doesn’t match user thinking, it will fail.

Structuring around how the business produces content rather than how people look for it
Building for today’s content, so next year’s has no obvious home
Mixing forms of label (verbs, nouns, product names) within one level
Pretending every item has exactly one home, which is what breaks taxonomies later
Shipping without testing, leaving a hypothesis in production

What you get from it

Done properly, this method gives you:

A structure that reflects how people actually search
Labels consistent enough to extend without a special case
Rules written down, so the taxonomy does not drift within two content cycles
A foundation navigation and search can both be built on

Key takeaway

It helps you organise things in a way that actually works.

Get in touch

If this sounds like something you need, we can help you organise your content so it’s simple, scalable, and easy to navigate.

No guesswork. No assumptions. Just structure that works.

FAQ

Common questions

A few practical answers to the questions that usually come up around this method.

What is taxonomy design in UX?

It is the process of organising content into structured categories and relationships.

When should you use taxonomy design?

Use it when building or improving content structure and navigation.

How is it different from card sorting?

Card sorting informs structure, while taxonomy design creates it.

What does a taxonomy include?

Categories, subcategories, tags, filters, and naming conventions.

Does taxonomy design improve UX?

Yes. It makes content easier to find and navigate.

Quick take

If your content is messy or hard to navigate, fix the structure with taxonomy design.

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services.

Previous feedback

I had a fantastic experience working with Andy. One of his most impressive achievements during our time at NHS HEE was masterminding a deeply complex information architecture for a new platform that brought together a large number of legacy websites.

Will Parkhouse

Senior Content Designer