Tithi Mondal

Guide7 min readUpdated

What Is Information Architecture? A Plain Guide for Owners

What is information architecture? A plain guide to sitemaps, menu structure, navigation planning and card sorting, and how they affect design cost.

By Tithi Mondal, UI/UX Designer

Read inहिन्दीবাংলাमराठीதமிழ்తెలుగుગુજરાતી

What Is Information Architecture? A Plain Guide for Owners: cover illustration

A coaching centre has a website with 40 pages. There are courses, fees, results, teachers, batch timings, admission forms and old notices. A parent wants one fact: the fee for the Class 10 maths batch. She clicks "Courses", then "Class 10", then "Maths", and finds no fee. She gives up and phones the centre. The pages were fine. The organisation was the problem.

Information architecture is the way a website or app organises its content and names its sections, so people can find things without thinking. Designers shorten it to IA. It is the plan behind the menu, before any colour or font is chosen.

What is information architecture, in plain words?

Information architecture is the arrangement of your content: what goes where, under which name, and in what order. Think of a good kirana shop. Rice, dal and oil sit in clear sections, and the owner puts the most asked items near the door. A visitor finds things without asking.

A website needs the same care. Information architecture answers four questions.

  • Which pages or screens should exist?
  • How should they be grouped?
  • What should each group and button be called?
  • How will a person move from one to another?

The last question is called navigation. Navigation planning means deciding the menus, links and buttons that carry a person through the structure.

What does good information architecture look like? A coaching centre example

Good information architecture matches the way visitors think, not the way the owner's office is organised. Return to the coaching centre with 40 pages.

The owner's first menu copies the office: About Us, Departments, Notice Board, Downloads, Gallery, Contact. A parent does not think in departments. A parent thinks: "Which batch is right for my child, what does it cost, when does it start, how do I join?"

A better structure has five top-level items: Courses, Fees and batches, Results, Teachers, Admission. Under "Courses" the visitor chooses a class. Each class page shows the subjects, the batch timings and the fee on the same page. An "Apply" button sits on every course page.

The content did not change. The grouping and the labels changed. For a small organisation, this single change often does more than a new colour scheme. I cover the wider planning of such sites in coaching institute and school website design.

What is the difference between a sitemap and a menu structure?

A sitemap is the full list of pages on a website, drawn as a tree. A menu structure is the smaller set of those pages that appear in the navigation. The sitemap is the plan of the whole building. The menu is the signboard at the entrance.

A sitemap for website planning may list 40 pages. The menu should show only 5 to 7 main items, because people cannot scan 20 items at once. The remaining pages stay reachable through the main sections, through links inside pages, through search and through the footer.

ItemWhat it isWho sees it
SitemapTree of every page and how pages group togetherOwner, designer, developer
Menu structureThe labels in the header, footer and mobile menuEvery visitor
NavigationThe full set of ways to move around, including links and buttonsEvery visitor

Note that "sitemap" also means an XML file that tells Google which pages exist. That is a different thing. Here I mean the planning drawing.

On apps, the same idea appears as a bottom tab bar or a side drawer. The choices are explained in mobile app navigation patterns.

Why does a business owner need navigation planning?

Navigation planning saves visitors from effort, and effort loses customers. A visitor who cannot find the price in 10 seconds usually leaves or sends you a WhatsApp message asking for it.

The benefits for an owner are practical.

  • More enquiries. The path to the contact form or WhatsApp button is short and clear.
  • Fewer repeated questions. Fees, timings and delivery areas are easy to find, so your staff answer fewer calls.
  • Easier growth. When you add a new service, you know where it belongs. The site does not turn into a pile.
  • Clearer pages for search engines. Related pages sit together, which helps people and search engines understand your site.

A restaurant is a good case. A visitor wants the menu, the address, the opening hours and a way to order. Those four items should be one tap from the home page. I describe this in restaurant and cafe website and menu design.

How does a designer plan information architecture?

A designer plans information architecture by listing all content, grouping it, testing the groups with real people, and then drawing the sitemap and menu. The work happens before wireframes, so the screens are built on a sound structure.

My usual order is this.

  1. Make a content inventory. I list every page and every piece of content you have or need. A spreadsheet is enough.
  2. Learn what visitors want. I ask you who visits and what they ask on the phone. This links to user research for startups.
  3. Group the content. I sort items into groups that make sense to a visitor.
  4. Name the groups. Plain words win. "Fees" beats "Investment in education".
  5. Draw the sitemap and the menu. One page of boxes and lines.
  6. Check it. I test whether a person can find five things quickly.

Card sorting explained simply

Card sorting is an exercise where people sort cards, each with the name of one page, into groups that feel natural to them. You write "Fee structure", "Batch timings", "Topper list" and so on, one per card. You ask 5 to 10 people to put the cards into piles and name each pile.

If most people put "Fee structure" and "Batch timings" together, those two belong together. If the piles get names like "Admission", you have found a good menu label. It costs almost nothing. You can use paper cards and ask relatives, parents or old students. Card sorting does not replace a designer's judgement, but it replaces guessing.

What should the finished information architecture plan contain?

A finished plan contains a sitemap, the menu labels for desktop and mobile, a note on where each page links, and the main user paths. It should be one or two pages that you can read in five minutes.

Look for these items.

  • A sitemap with no more than 3 levels of depth. Deeper pages are hard to reach.
  • A main menu of 5 to 7 items, with plain labels.
  • A footer list for items such as privacy policy, refund policy and careers.
  • The place of the most important button, such as "Call", "WhatsApp" or "Apply".
  • A list of pages that are deliberately left out of the menu, and why.
  • A short list of the three to five tasks visitors must finish easily.

The plan then feeds the next steps. The paths turn into user flows, which I explain as a plan of the steps for one task. The structure turns into wireframes, covered in wireframe vs mockup vs prototype.

What mistakes break information architecture?

The biggest mistake is organising the site like your company instead of like your customer's questions. Others follow from it.

  • Internal words in the menu. Customers do not know your product codes or department names.
  • Too many menu items. Twelve items hide the three that matter.
  • Hiding the price. "Contact us for a quote" on every page makes people leave.
  • Deep nesting. A page four clicks away is a page few people see.
  • One page in two places with two names. Visitors cannot tell whether they have already seen it.
  • Ignoring the phone menu. Most Indian visitors use mobile. A menu that works on a laptop may fail on a small screen. See mobile first website design.

How does information architecture affect cost and timeline?

Information architecture adds a short planning step at the start, and it reduces rework later. A clear structure also means fewer changes during revision rounds.

I quote website design by the number of screens and user roles. A site with 40 pages needs more planning than a site with 6. A small business site can have its structure settled in a few days, within a typical 2 to 4 week project. Two to three revision rounds are included. Payment is 50% to begin and 50% on completion. For price factors, see website design cost in India.

If your website has grown messy, or you are planning a new one and want the structure right first, I can help through website design.

Frequently asked questions

What is the difference between information architecture and navigation?

Information architecture is the whole plan of how content is organised and named. Navigation is the part visitors touch: the menus, links and buttons that follow that plan.

How many items should a website menu have?

Usually 5 to 7 main items. More than that makes the menu hard to scan, especially on a phone.

Do I need information architecture for a small website?

Yes, but it can be quick. Even a 6 page site benefits from clear labels and a clear path to the contact or WhatsApp button.

Is information architecture the same as UX design?

No. It is one part of UX design. UX design also covers flows, screen layouts, wording and testing.

Working on something like this?

Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.

Your details go only to Tithi and are used only to reply to you. No newsletters, no sharing.

Have a product in mind? Let us design it properly.

Tell me what you are building. I will reply with questions, a rough timeline and a quote.