Information architecture should happen before interface design
Information architecture gives a product its structure before the pixels arrive. It clarifies navigation, page relationships, content groups, objects, and user paths.
A lot of product design starts too visually. The team opens Figma, sketches screens, and only later realizes the product does not know how it is organized. Navigation feels arbitrary. Objects are named inconsistently. Important workflows are buried. The interface looks designed, but the product structure is still undecided.
Information architecture should happen earlier.
IA is the product's map
Information architecture defines how the product is organized:
- What objects exist.
- How pages relate to each other.
- What the primary navigation contains.
- Which workflows are global and which are contextual.
- How users move from intent to completion.
- What labels and content groups make sense.
For a founder, IA is where the product starts becoming understandable.
Bad IA creates hidden product debt
When IA is weak, every later decision gets heavier. Designers invent page structures case by case. Engineers implement routes that do not match the mental model. Users ask, "Where do I find this?" Support tickets become product architecture feedback.
Strong IA prevents that by making the product's shape explicit before screens are polished.
Start with objects and jobs
Do not begin with navigation labels. Begin with the core objects and jobs. In a client portal, the objects might be clients, projects, files, approvals, invoices, and messages. The jobs might be upload, review, approve, comment, pay, and hand off.
Once those are clear, navigation becomes a product decision rather than a layout preference.
We created an Information Architecture reference with page inventory, object relationships, content groups, and a practical starter template.
Designing screens without IA is like decorating rooms before agreeing where the walls are.
Written by
Fab SenchuriFounder, Zenith Studio
Fab writes about AI product strategy, UX, MVP scoping, and founder-led product building.
View all from Fab Senchuri →Keep reading
How to validate an AI product idea before you build
A practical playbook for early founders: how to tell whether your AI idea is worth building, the cheapest ways to test it, and the assumptions that quietly kill startups.
Read →Playbook · 7 minFinding the core loop: how to scope an AI MVP that ships
Most AI MVPs try to do everything and ship nothing. Here's how to find the single core loop that proves your product — and scope a build you can launch in weeks, not quarters.
Read →
