Tested With Users
Card sorting and tree testing, before anything is built on it.
Most navigation reflects how the organisation thinks about itself: divisions, product lines, internal categories. Visitors do not know any of that. Information architecture services reorganise around how people actually look for things — and test that with real users rather than agreeing it in a room.
A structure everyone in the meeting understood is not evidence that anyone outside it will.
Card sorting and tree testing, before anything is built on it.
Labels people recognise rather than internal terminology.
Every extra level costs a share of the people navigating it.
Structure that produces findable URLs, not only usable menus.
Room for growth without a reorganisation every year.
Four things, and all four are testable before a line of code.
Discuss Your Structure →What belongs together, from the visitor's point of view.
What each group is called, in language people recognise.
How many levels, which directly affects how many people arrive.
Where something legitimately belongs in more than one place.
Research, structure and validation before anything is built.
Restructuring changes URLs — SEO migration covers protecting them.
Research, propose, test, then build. The testing step is what makes it evidence.
Everything that has to be placed somewhere.
Card sorting with people outside the organisation.
Built from what the research showed.
Can people find things in it, before anything is built.
With redirects where paths change.
It validates a structure before anything is built on it, and it takes days.
Participants are given the proposed structure as a bare list of labels — no design, no visuals — and asked where they would look for specific things.
It measures whether the structure works, isolated from whether the interface is attractive, which is the only way to test the two separately.
It runs remotely, needs no build, and produces a completion rate per task. A structure that fails it will fail after launch too, only far more expensively.
Because everyone specifying the navigation uses it daily and has forgotten it is specialised. Product names, division names, internal category terms — all obvious to the people choosing them.
Visitors search using ordinary words for their problem. A menu labelled with your taxonomy asks them to translate, and most do not.
The fix is testing labels with people outside the organisation, which surfaces the problem within an afternoon and is skipped almost universally.







Information architecture services organise content and navigation around how people look for things — grouping, labelling, depth and cross-references — validated with card sorting and tree testing.
Test it. Tree testing gives a completion rate per task using nothing but the labels, runs remotely, needs no build, and takes days rather than weeks.
As shallow as the content allows. Every additional level costs a share of the people navigating it, so depth should be a deliberate trade rather than a consequence of the content model.
Because visitors do not know them. Internal terminology is invisible to the people who use it daily and requires translation from everyone else, and most will not bother.
Yes, where URLs change. A restructure without a complete redirect map loses what those URLs earned — see SEO migration.
Still deciding if information architecture services is right for you?
Talk to UsNavigation structures get agreed in workshops. The categories are discussed, argued over, refined, and eventually everyone present agrees the result makes sense.
It does make sense — to a room of people who know the organisation, its divisions, its product names and its internal vocabulary. That shared knowledge is precisely what the visitor does not have.
Testing the structure with five outsiders takes an afternoon and reliably finds the categories nobody else can interpret. It is skipped because the workshop already produced agreement, and agreement feels like validation.
Send us your navigation. We will assess the structure and, where it is worth it, tree test it with real participants.
