Information Ecosystems

Every digital information space exists within a broader ecosystem, a network of interconnected users, content, business goals, and context. None of these components operates independently. The users bring their mental models and information needs. The content must serve both the users and the business. The business has strategic goals that shape what gets built and why. The context includes the competitive landscape, other information spaces the organization runs, and the channels through which people access information.

Effective information architects design for the whole ecosystem, not just the individual page or product in front of them. When one component is neglected, the consequences show up elsewhere, often in ways that are difficult to diagnose without understanding the system.

Think of it like a building: the structure, the people who use it, and the neighbourhood it sits in all affect whether the building works. You can't design just the interior and call it done.

Exercise

The scenario: Meridian is a mid-sized financial services company redesigning their customer portal. The project has been running for four months. Here's what the team has done so far:

They conducted twelve user interviews and have detailed personas representing three distinct customer types. They audited all existing content and have a complete content inventory. The development team has confirmed a CMS that supports structured content and faceted navigation.

The lead IA presents the proposed information architecture to the steering committee. The head of Marketing immediately objects: "This structure doesn't reflect our product strategy at all. We're about to launch two new product lines, and I have no idea where they'd live in this. And why are we organizing by customer type? Our competitors organize by product."

The IA is caught off guard. The project has been running for four months and this is the first time anyone from Marketing has raised these concerns.

Which component of the information ecosystem did this team neglect, and what is the most likely consequence of that neglect for the IA?

Users, the team didn't research actual customers deeply enough, so the personas don't reflect real information needs.
Content, the content inventory is incomplete, so the new product lines have no home in the proposed structure.
Business, the team designed without understanding the organization's strategy and competitive context, so the IA doesn't align with business goals.
Context, the team didn't analyse competitor information spaces, so they missed an industry-standard organizational pattern.

What should the team do now, and what does this situation reveal about when in the process business stakeholders should be involved?

Feedback

The correct answer is Business, though the competitor point in the Context option is real and worth noting separately.

The team conducted thorough user research and content analysis, but they never engaged with business stakeholders to understand Meridian's product strategy, competitive positioning, or upcoming launches. The Marketing head's objection isn't a late-stage preference: it's a foundational misalignment that has been sitting undetected for four months.

The consequence is significant. An IA organized around customer types may be the right answer for users, but if it contradicts the business's product strategy, it will be rejected, or worse, implemented and then undermined by stakeholders who route around it. An information architecture is a tangible expression of business strategy. When the strategy hasn't been understood, the IA expresses the wrong thing.

On the competitor point: the Marketing head mentions it, but it's a symptom of the business neglect rather than a separate problem. Had the team conducted stakeholder research early, the competitive landscape would have surfaced as part of understanding the business context.

What the team should do now: pause and conduct stakeholder interviews before proceeding. The IA strategy needs to be grounded in the business strategy before the structural decisions can be validated. This means going back to the steering committee, including Marketing, to understand the product roadmap, the competitive positioning, and what the portal is meant to accomplish commercially.

What this reveals about timing: business stakeholders should be involved at the very start of Discovery, before personas are created, before content is inventoried, and certainly before structural decisions are made. Their input defines the constraints within which all other IA decisions operate. Involving them at the presentation stage, after the work is done, means discovering fundamental misalignments when change is most expensive.