Information architecture describes how content is structured, labelled, connected and managed so that people can find what they need. In SharePoint, it covers sites, navigation, pages, libraries, metadata, search and permissions. A good structure starts with users' tasks, not with the organisation chart.
Plan sites and navigation
Modern SharePoint guidance favours a flat structure of separate sites for clearly defined topics, tasks or units of work rather than deep subsite hierarchies. Hubs can connect related sites when shared navigation, branding or discoverability makes sense. Associating a site with a hub does not change its permissions; access must be reviewed separately.
Plan global, hub and local navigation together. Use short, clear labels, group links by what users are trying to do and test the terms with employees. Microsoft explains the building blocks in its introduction to SharePoint information architecture.
Use libraries, lists and metadata deliberately
Align libraries and lists with actual workflows. Columns and content types can classify content and support views and search, but every additional field has to be maintained. Use metadata where employees can apply it consistently; do not add it merely because the feature exists. Folders can also be useful, but very deep paths make navigation harder.
Connect findability and governance
Permissions, retention, ownership and navigation should be planned together. Name owners for sites and important content, review access and outdated information regularly and document how changes are requested. Search and navigation help people find content; they do not guarantee that content is correct, current or shared with the right audience.
Test the structure with users
Ask employees to complete typical tasks: find a current policy, locate a project document or identify the person responsible. Observe where they get stuck, adjust terms and links, and test again after changes. Information architecture is ongoing work because the organisation, content and needs change.
For more detail, see Microsoft's SharePoint navigation planning guide.

