Information architecture

Information architecture decides what exists, where it lives and what it is called. On a marketing site that means the page inventory, how pages group into sections, the labels in the menu and the URL structure. In a product it means the objects users work with, the screens and states around them, and how roles and permissions change what each person sees.

IA is not on screen itself. It is documented in sitemaps, spreadsheets and diagrams, and the interface expresses it through navigation, headings and links. Nielsen Norman Group describes navigation as the visible tip of the IA iceberg.

Why it matters for a SaaS website

SaaS sites tend to grow by accretion: a new feature page here, an integration directory there, three versions of “solutions”. Without a deliberate IA, visitors cannot tell where to start, important pages get buried, and search engines and AI answer engines see a muddle of overlapping pages. In the product, a weak IA shows up as hunting through settings, duplicated features and support tickets that start with “where do I find”. A clear structure is also what makes a website migration safe, because you know which pages map where.

How DesignMe handles it

We map structure before drawing screens. On product design projects, the first one to two weeks cover user flows and IA: core journeys, screen relationships, navigation and product logic, ending in a screen map and navigation structure. On website projects, UX foundations come first: what pages the site needs, how the story flows and what each page must say.

For N3XT we mapped every page, state and decision point of a dense payments product before designing it, iterated the structure with stakeholders across sprint reviews, then locked a final IA that every flow was built against. For Seamless.AI’s 130-page site, we rebuilt navigation around a mega menu that groups the product into scannable zones with a one-line description under every item.

Example

Say a data platform’s site has “Product”, “Platform”, “Solutions” and “Use cases” in the menu, with overlapping pages under each. A content inventory and a quick card sort show buyers think in two ways: by job to be done and by team. The new IA keeps one product section, groups use cases by team, and redirects the duplicates, cutting the top-level menu from seven items to four.

Common mistakes

• Mirroring the org chart. Users do not care which team owns a page.
• Internal jargon in labels. If customers do not use the word, they will not click it.
• Designing screens first. Layouts built before the structure is agreed get redrawn.
• Treating IA as one-off. Revisit it whenever a major feature or audience is added.