Intranet Information Architecture: Guide and Example (2026)

You're looking for the expense report procedure. Is it under HR? Finance? Tools? After three clicks, you give up and message a colleague. Multiply that by every employee, every week. According to McKinsey (July 2012), employees spend 1.8 hours a day searching for and gathering information, close to a full workday every week. The figure is more than ten years old, and it still describes most intranets very well. The cause is almost always the same: a structure designed by the people who publish, not by the people who search.

What is intranet information architecture?

Intranet information architecture (IA) is the discipline of organizing intranet content so people can find it and act on it. Its most visible output is the intranet structure: the top-level sections, their subsections, then pages and documents, drawn as a tree. It is the skeleton of every corporate intranet: if it is shaky, no homepage design will save it.

Three notions often get mixed up:

• Information architecture is the overall discipline. Microsoft lists five elements: portal navigational structure, hub structure and organization, site and page architecture, metadata architecture and search experiences (Microsoft Learn, June 2026).
• The structure (or site tree) is the map of sections. It decides where each piece of content lives.
• Navigation covers the menus, links and shortcuts used to move through that structure. We cover it in our article on global navigation in the digital workplace.

Remember the rule: structure decides where content lives, navigation decides how people get there.

Microsoft gives good information architecture three goals: help people find information, help them take action, and help them understand the company's structure (Microsoft Learn, June 2026). A successful intranet structure ticks all three. It answers "where's my payslip?" quickly, leads straight to the form, and shows how the company is organized along the way, without requiring anyone to know it by heart.

4 ways to structure your intranet

Microsoft describes four organizing models (Microsoft Learn, June 2026). None is perfect on its own. Here is what each brings, and where it breaks.

Our recommendation is a hybrid model. The top level speaks the employees' language, with tasks and everyday topics. Departments and locations sit below.

Microsoft says it plainly: "Don't just think about the organization chart. Think about the information people need in their daily work." ThoughtFarmer agrees (December 2024): an IA based solely on the org chart "forces people to know who owns the content". An employee doesn't look for "Human Resources Department". They look for time off, pay and benefits.

SharePoint information architecture: think flat

This is the most misunderstood shift. Classic SharePoint stacked site collections and subsites on several floors. Microsoft admits that once built, this structure "can be inflexible and difficult to maintain". In modern SharePoint, the guidance is clear: subsites are not recommended. You create one site per topic or unit of work, and you connect them.

To connect those sites, SharePoint offers three levels of navigation:

• global navigation, shared across the whole intranet;
• hub navigation, shared by the sites in the same hub;
• local navigation, specific to each site.

The key point fits in one sentence: in modern SharePoint, site architecture and the structure people see are two separate things. The HR site can appear under "My Work Life" in the menu without technically living there. Step Two put it this way back in 2022: creating sites is about content ownership and governance, while the navigation experience is about usability and findability (Step Two, March 2022).

This decoupling is an opportunity. You can reorganize the menu without moving a single site. One constraint to keep in mind: a site can only be associated with one hub. So choose your hubs based on who manages what, and your menu based on who looks for what. For a step-by-step setup, see how to create a SharePoint intranet easily.

How to build your intranet structure in 6 steps

An intranet structure isn't decided in a meeting around a whiteboard. You build it with employees, in six steps.

1. Take a content inventory. List what exists (sites, pages, libraries) with the owner and last update date. A good share can often be archived before you even start.
2. Identify top tasks. Interview a few employees from each population (office, frontline, managers) and list the 20 to 30 things they come to the intranet to do. Internal searches with no result are a gold mine.
3. Run a card sort. Employees group content cards and name the groups themselves. Microsoft recommends it for planning navigation.
4. Draft a first version. Six to nine top-level sections, two levels below at most. A spreadsheet is enough, no mockup needed.
5. Run a tree test. Give a task ("where would you find the expense report procedure?") and watch the path people take, on the bare structure, with no visual design. Microsoft cites tree testing for validating navigation paths. If testers hunt around, the section is badly named or badly placed.
6. Launch, then review. At launch, delete the default navigation of communication sites (Documents, Pages, Site contents), as Microsoft advises. Then track searches with no result and pages nobody visits, with our intranet optimization guide.

These steps belong in your intranet requirements, before you even pick a tool. And to keep the structure clean after launch, someone has to own it: that is the job of intranet governance.

Sample intranet structure

Here is a starting structure we see working in many mid-sized organizations. It fits in six sections, and each one has an owner.

Three things to notice. The two most used sections ("My Work Life" and "Tools and Services") are worded from the employee's point of view. The org chart is a page under "Our Company", not the backbone of the menu: an interactive org chart connected to Microsoft 365 does that job far better than a department-based structure. And team spaces exist, but at the bottom of the list: they mainly serve the people who work in them.

Adapt the labels to your culture, not the logic. For inspiration, browse our examples of corporate intranets.

Naming and depth rules

A structure is also judged by its words. Six simple rules avoid most dead ends:

• Fewer than 10 top-level sections. That's the limit ThoughtFarmer recommends. Beyond it, the eye stops sorting and starts scanning.
• 3 levels at most. This is our recommendation at Jint, not a Microsoft rule. Every extra click loses some readers. Instead of digging deeper, create a site and link to it.
• Short, concrete labels. "Time off" rather than "Absence and time management". The employee's word, not the department's.
• No "Misc" or "Other" section. It quickly becomes the intranet's attic.
• One home per piece of content. Each item lives in one main section, and the others link to it. Two copies always end up diverging.
• The same word everywhere. If the menu says "Expenses", the page and the document say "Expenses" too.

Is your intranet multilingual? Translate labels as carefully as content. A badly translated menu loses international teams at the first click. We cover best practices in our article on the multilingual intranet.

Information architecture and AI: why structure matters more in 2026

For a long time, a poor structure cost clicks. With Microsoft 365 Copilot and AI agents, it costs wrong answers. An assistant answers from everything the user is allowed to see. If the expense report procedure exists in three versions, in three sections, the agent will pick one. Maybe the oldest.

That's the Jinters' conviction: a structured intranet is the foundation AI agents need to work. An agent is only as good as the information it can access. A clean structure gives it exactly what it needs: content in one place, a named owner, an update date.

Metadata, which Microsoft counts among the five elements of information architecture, plays a quiet but decisive role here. A content type, a target audience, a review date: these labels help both search and AI sort things out. To go further, read our article on the intranet chatbot.

5 mistakes that ruin intranet information architecture

• Copying the org chart. Reassuring for the people who publish, confusing for everyone else.
• Carrying the old structure over as is. An intranet redesign is the best moment to start again from tasks, not from what exists.
• Letting every department claim a top-level section. The menu swells, and nothing stands out anymore.
• Never testing with users. One hour of tree testing saves months of "I can't find it" tickets.
• Forgetting frontline employees. On mobile, the menu shrinks to a few entries. If your structure doesn't fit on a phone screen, it's too wide.

These mistakes explain many of the intranets that fail to engage employees.

Build an intranet structure that lasts

Good intranet information architecture comes down to one idea: start from what employees look for, not from how the company is organized. Six to nine sections, three levels, plain labels, a test with real users and a regular review. In SharePoint, think flat and keep site architecture separate from the menu people see.

To frame your project, download our free intranet requirements template: information architecture has its own section. Want to see what clear navigation on Microsoft 365 looks like? Discover Jint SharePoint.