Aligning IA Strategy With Business Strategy

An information architecture strategy has to derive from the organization's actual business strategy, its unique, differentiated goals should shape how content gets structured and labeled, not the other way around. If an organization hasn't clearly articulated its strategic vision, the IA team's job includes helping surface it: interviewing key business stakeholders about the core problem they're solving, their goals, the appropriate scope of the project, and why it's happening now. If gaps or misconceptions turn up during this process, the IA team should ask the difficult questions rather than quietly working around them.

Achieving this alignment early saves real time and money later, misalignment discovered after structural decisions have been made is far more expensive to fix than misalignment caught during Discovery. Business strategy also isn't static: as an organization's competitive situation shifts, the IA strategy needs to adapt with it, which means sharing draft strategy thinking with trusted business partners early and often, rather than presenting a finished structure and hoping it matches what the business actually needed.

An information architecture is a tangible expression of business strategy, when the strategy hasn't been understood, the structure expresses the wrong thing, no matter how well it's designed.

Exercise

The scenario: A mid-sized insurance company has defined a business strategy focused on self-service, reducing calls to their support center by letting customers handle more tasks independently online. The IA team has produced a proposed information architecture for the company's customer portal.

The proposed structure organizes content primarily by internal department, Claims, Billing, Policy Administration, Underwriting, mirroring how the company's own teams are organized. Within "Claims," a customer wanting to both file a new claim and check on an existing one has to navigate two entirely separate sub-sections with no cross-links between them. The search function only searches page titles, not body content, so common self-service questions phrased in plain language often return nothing.

1. The top-level organization by internal department, Claims, Billing, Policy Administration, Underwriting, creates which specific misalignment with the self-service strategy?

It reflects the company's internal organizational logic rather than the tasks a customer actually wants to complete
It simply has too many top-level categories
There's no misalignment, department-based organization is a neutral, safe default

2. The lack of cross-links between filing a new claim and checking an existing one most directly undermines which part of the self-service strategy?

It forces customers to abandon a natural task flow and start over, increasing the odds they give up and call support instead
It's purely a visual design inconsistency
It has no meaningful impact on the self-service goal

The search function only searching page titles is a third misalignment. Propose a specific IA adjustment that would address it, and explain how it connects back to the self-service goal specifically, not just "better search" in the abstract.

Feedback

1: It reflects internal organizational logic rather than customer tasks. A customer doesn't think in terms of the company's department structure, they think in terms of what they're trying to accomplish. Organizing the portal around Claims, Billing, Policy Administration, and Underwriting as internal silos is a direct instance of designing for the business's own mental model instead of the self-service strategy's actual target audience.

2: It forces customers to abandon a natural task flow. Filing a new claim and checking an existing one are closely related tasks in a customer's mind, even if they map to different internal teams. Forcing a customer to navigate two disconnected sub-sections with no link between them increases the friction of self-service at exactly the moment the strategy is supposed to be reducing it, and friction is what drives customers back to the phone.

These three misalignments share a pattern: each one individually might seem like a minor structural or technical choice, but together they consistently undermine the same stated business goal. This is exactly the kind of finding that should surface during Discovery, before structural decisions are finalized, catching all three now is far cheaper than discovering them after launch, when customers are still calling support at the same rate the redesign was meant to reduce.

A reasonable fix for the title-only search: expand the search index to include body content, and support it with content-derived metadata using the customer's own self-service language, terms like "file a claim" or "check claim status", rather than only the internal department names the pages happen to be titled after. This directly serves the self-service goal because it means a customer typing a plain-language question is far more likely to find the right page without needing to guess the company's internal terminology first.