What is information architecture?
Information architecture is the work of organizing the content of a website, an application or an intranet so that people can find and understand what they are looking for. It answers four questions: What content is there? How is it grouped? What is each thing called? And how do people get to it: through menus, search or links?
Think of it as a building’s floor plan. Visitors never see the plan, but they notice straight away whether they can find the right door.
What does information architecture cover?
- Content inventory. Which pages, documents, services and data exist; which are current and which repeat each other.
- Structure. How content is grouped and how those groups connect. A sitemap is a summary of this structure.
- Naming. The words used in menus, headings and categories. An organization’s own vocabulary is rarely the one its users use.
- Navigation. Main menus, sub-menus and in-page links: how people move from one place to the next.
- Search and classification. How content is tagged, what search finds and how filters work.
- Governance. How the structure is kept in shape as new content arrives, and who decides what.
How is information architecture different from UX and UI design?
Information architecture sets the structure of the content, UX design shapes the experience within that structure, and UI design decides how that experience looks on screen. The order matters: if the structure is unclear, even the best interface just shows people the wrong way, beautifully.
That is why we see information architecture as the bridge between strategy and UX/UI design. What research uncovers becomes a structure first, and screens second.
Why does it matter so much to organizations?
On a small site, all the content fits in a single glance. Organizations are different: dozens of departments, hundreds of pages, several audiences and years of accumulated content. At that scale, information architecture is not a design detail but a strategic decision.
People find what they came for. Citizens, customers and employees visit a site to get something done: apply for something, check a fact, find a document. When the structure follows their needs, that takes moments. When it follows the organization chart, people have to learn how the organization works first.
Content stops repeating itself. Without a clear structure, every department starts its own page, the same information lives in several places in different versions, and nobody is sure which one is current. Information architecture gives every piece of content one place and one owner.
The same questions stop coming back. Information people can’t find turns into phone calls, emails and contact-centre tickets. Findable content keeps teams from answering the same questions again and again.
The product can grow. When new services, languages or audiences are added, a good structure stretches to fit. A weak one gets a little more tangled with every addition, until it has to be rebuilt every few years.
Migrations are safe. When a site moves to a new platform, information architecture is the map of what moves, what merges and which old address points to which new page. Without that map, people and search engines both lose their way.
Search engines and AI assistants understand the content better. Clear headings, consistent naming and a sensible hierarchy make it easier for content to surface for the right questions.
Where does information architecture sit in a digital product strategy?
A digital product strategy decides what you offer, to whom and why. Information architecture shows how those decisions turn into content and structure. That is why it belongs at the start of a project, before design and development.
In our approach, it sits at the heart of Define & Explore: as we learn the goals, the users and the existing content, the outline of the structure takes shape. In Design & Develop, navigation, page templates and search are built on that structure.
It is not a one-off job either. In Optimize, we watch how people use the content and update the structure with what analytics and on-site search tell us.
How can you tell your organization needs information architecture work?
- Users or employees keep asking the same questions.
- The same information sits on several pages, in different versions.
- Menus follow department names rather than what people need.
- Nobody trusts the site’s own search; people use a search engine instead.
- Adding new content starts with an argument about where to put it.
- A move to a new platform, a merger of several sites or a major redesign is coming up.
How does an information architecture project run?
We go through the steps in detail in our guide for large corporate websites. In brief:
- Inventory and assessment. The existing content, addresses and usage data are gathered.
- Research. Stakeholders and users are interviewed to learn what people are trying to reach, and in which words.
- Structure and naming. Content groups, the sitemap and labels are shaped.
- Validation. The structure is tested against users’ real tasks and corrected.
- Hand-over into design and development. Navigation, page templates and search are designed and built on the structure.
- Upkeep. Rules and responsibilities for adding new content are agreed.
Information architecture at different scales: four examples
- İSKİ website. As İSKİ’s website was redesigned and moved to a new platform, content and data from the previous systems were brought into a new information architecture.
- Ministry of Interior websites. The structure of the websites of the Ministry and six affiliated units is organized around what citizens come to do, so they can find answers quickly and consistently on every site.
- Yıldız One. Yıldız Holding’s employee and business portal brings data dashboards, HR services, operational tools and company information into one place, organized so that people in very different businesses can find what they need quickly.
- Control Tower. Yıldız Holding’s platform for monitoring, managing and reporting on its fleet. It brings fleet status, operations and reports into one interface, structured so teams can see what needs attention and act on it.
All of them are on the Work page.
In short
- Information architecture is the structure, naming and findability of content.
- As an organization grows, it stops being a design detail and becomes a strategic decision.
- It should come before design and development, and be looked after once the product is live.
If some of the signs above sound familiar, have a look at Research & Strategy or get in touch.