Enterprise information architecture (EIA) organizes information across an organization’s products, repositories, and services so people can find, understand, and use it. It connects shared vocabulary, classification, metadata, navigation, search, and governance across teams and systems.
In UX practice, this includes intranets, employee portals, and business applications. Teams coordinate definitions across owners and workflows: the same customer, policy, or expense claim may appear in several places.
What does enterprise information architecture include?
| Area | Question it answers |
|---|---|
| Shared vocabulary | Do teams mean the same thing by “customer,” “account,” or “approved”? |
| Taxonomy and metadata | How is information classified, described, filtered, and retrieved? |
| Objects and relationships | How do records connect to people, documents, and other records? |
| Navigation and search | How can users reach information across products and repositories? |
| Governance | Who owns definitions, resolves conflicts, and maintains the structure? |
Access rules also shape what different users can find and see. Shared definitions can support different role-specific views without requiring every team to use the same navigation.
An enterprise IA example: expense claims
Consider an illustrative employee portal connected to an expense system. An employee submits Claim #482; a manager reviews it; finance processes reimbursement.
The team defines one claim identifier and distinguishes Submitted, Approved, and Paid. Approval means the manager accepted the claim; payment means reimbursement was completed. That distinction needs to remain clear wherever the claim appears.
| User | Entry point | Information needed |
|---|---|---|
| Employee | My expenses | Claim status, receipts, and payment date |
| Manager | Claims awaiting approval | Amount, policy, and supporting receipts |
| Finance | Approved claims | Payment details and reimbursement status |
These views refer to the same claim. Links connect it to its receipts and the relevant policy. Metadata such as owner, date, and status supports search and filtering.
An assigned owner maintains the status definitions and checks how changes affect each system.
How do you start?
Start with one task that crosses a team or system boundary. Interview the people involved, inventory the records and content they use, and note conflicting labels or duplicate sources.
Agree on definitions and ownership with domain experts. Identify the authoritative source for each record or policy. Then prototype navigation, search results, and record relationships. Use card sorting to explore groupings, tree testing to check findability, and usability testing to evaluate the complete task.
Measure whether people find the right information and complete the task accurately. Search failures, wrong destinations, and time spent locating records can reveal structural problems.
How is enterprise IA different from a sitemap?
A sitemap describes a hierarchy of pages. Enterprise IA also coordinates meaning, metadata, relationships, and ownership across systems. One deliverable might be a sitemap; others include a vocabulary, taxonomy, content model, or governance plan. The appropriate structure depends on users’ work and the information involved.