INFORMATION
ARCHITECTURE
ORGANISATION
Group by user goals
LABELLING
Recognition over recall
NAVIGATION
Orientation system
SEARCH
Escape hatch + diagnostic
TAXONOMY
Invisible infrastructure
Information Architecture in UX Design
5 CORE PRINCIPLES · 7-STEP PROCESS · 2026
gokhanmeric.com/blog
## Information Architecture Is the Most Underrated Skill in UX Design
**Information architecture (IA)** is the practice of organising, labelling, and structuring content so users can find what they need — and do what they came to do — without friction. It’s not visual design. It’s not copywriting. It’s the underlying logic that determines whether a product feels intuitive or confusing from the very first click.
After 20+ years designing digital products across enterprise, fintech, logistics, and e-commerce, I’ve come to believe that information architecture is the single highest-leverage skill in UX. Not animations. Not colour palettes. Not even copywriting. The *structure*.
In this guide, I’ll share the IA frameworks I use across every project — tested at Beko (50,000+ employees, 15+ countries), Ekol Logistics, and Flowvoy’s AI-powered omnichannel operating system.
—
## What Is Information Architecture?
Information architecture operates at the intersection of three forces: **content** (what exists), **context** (why users are here and what constraints apply), and **users** (what they know, expect, and need).
Good IA is the difference between:
– A user who opens your app and immediately knows where to go
– A user who opens your app, clicks around aimlessly for 45 seconds, and rage-quits
When information architecture is done well, users don’t notice it. They simply feel at home. When it’s wrong, no amount of beautiful visual design saves you.
—
## 5 Core Information Architecture Principles I Apply to Every Project
### Principle 1: Organise Around User Goals, Not Company Structure
Users build mental models as they navigate. If your navigation groups items by internal department logic (`Finance → B2B → Reporting → Export`) rather than user task logic (`Download my invoice`), you’ve already lost them.
At Ekol Logistics, I inherited a cost management interface structured around the company’s org chart. After running card sorting sessions with actual users, we restructured the navigation around task flows. Time-on-task dropped by 40%.
### Principle 2: Label for Recognition, Not Recall
Vague labels — “Manage”, “Settings”, “More” — create cognitive overhead. Specific, action-oriented labels — “Edit my profile”, “Download invoice”, “Add a product” — enable recognition, which is faster and lower-effort.
When I joined FlixBus (Kamil Koç), relabelling the booking flow alone — before any structural changes — lifted conversion by a measurable percentage.
### Principle 3: Make Navigation an Orientation System
Users need to know three things at all times: *Where am I? Where can I go? How do I get back?* For complex enterprise systems, I use **dual navigation**: a global primary nav for top-level orientation and a contextual secondary nav for feature-level movement.
### Principle 4: Treat Search as a Diagnostic Tool
What users search for tells you exactly where your IA has gaps. If 2,000 users per month search for “invoice”, the word “Billing” in your nav is probably wrong.
### Principle 5: Taxonomy Decisions Made Early Last Forever
At Beko, I defined the taxonomy for the Oliz app’s product catalogue — scaling across 15+ countries and 4 languages. Getting this right in month one saved months of rework in year two.
—
## My Information Architecture Process: Discovery to Delivery
**Step 1 — Stakeholder Interviews:** Understand business goals, existing pain points, and what success looks like.
**Step 2 — User Research:** 5–8 contextual interviews. What words do *they* use, not your product team?
**Step 3 — Content Inventory:** Map everything that exists: every screen, section, content type, and data entity.
**Step 4 — Card Sorting:** Open card sorting reveals natural groupings. Closed card sorting validates your proposed structure. Tools: [Optimal Workshop](https://www.optimalworkshop.com), [Maze](https://maze.co).
**Step 5 — Tree Testing:** Test your navigation structure before building a single wireframe. The cheapest usability test you’ll run.
**Step 6 — Sitemap & Flow Diagrams:** A sitemap the entire team can read and navigate from.
**Step 7 — Wireframes:** Now, and only now, translate validated IA into wireframes.
—
## Common Information Architecture Mistakes in 2026
**Navigation that grows organically** — Audit and prune quarterly.
**Designing the homepage first** — Most users don’t enter through the homepage. Design interior pages first.
**Ignoring mobile IA** — Plan for progressive disclosure: show less by default, reveal more on demand.
**Treating IA as a deliverable, not a practice** — Build governance into your process from the beginning.
—
## IA Tools I Use in 2026
– **Figma** — sitemaps, flow diagrams, wireframes
– **FigJam** — collaborative card sorting
– **Optimal Workshop** — tree testing at scale
– **Maze** — unmoderated usability testing
– **Notion** — content inventories and taxonomy documentation
—
## Closing Thoughts
When information architecture is wrong, no amount of beautiful UI saves you. When it’s right, even a rough prototype feels intuitive.
—
*Related reading: [What Is a UI/UX Architect?](/blog/2026/06/16/what-is-a-uiux-architect/) · [UX Strategy That Sticks](/blog/2026/06/16/ux-strategy-aligning-design-decisions-business-outcomes/)*
*Have questions about your product’s information architecture? I offer [UI/UX Architecture consultancy](https://www.gokhanmeric.com/#contact) for startups and scale-ups globally.*
