The Document Every Digital Modernisation Needs Before Workshops Begin

Introduction

The Domain Scope Map: A Single Reference That Resolves the Most Disruptive Workshop Question Before It Gets Asked

There is a question that derails IA workshops with surprising consistency. It arrives in the middle of a navigation discussion or a content taxonomy conversation, and it does not have a quick answer: "Wait, is that property in scope or not?"

The question is reasonable. In complex digital estates (organizations with multiple platforms, subdomains, legacy properties, recently acquired systems, and third-party dependencies), the scope question is legitimately complicated. The problem is that the answer requires a decision that has not been made before the workshop started.

An hour of a workshop intended to produce navigation decisions instead turns into a scope conversation. The scope conversation requires people who are not in the room. The next meeting is scheduled. The IA decisions are deferred.

What The Domain Scope Map Solves

The domain scope map is a single document, ideally no more than two pages, that maps every digital property in an organization's estate to its Phase 1 treatment before any workshop begins. It answers the scope question in advance for every property, in every possible direction.

The classification system we use has six categories.

1. Full Build, where the property is being rebuilt or significantly replatformed in this phase.

2. Experience Layer, where the property's platform remains unchanged, but its user-facing experience is being consolidated into a unified layer (typically a logged-in dashboard).

3. Blog Migration, where content migrates to the primary platform, but no significant IA work is required beyond the migration.

4. Assessment Only, where the property is audited but no work is executed in this phase.

5. API Layer Only, where the platform remains untouched, but its data is exposed via API into the primary experience.

6. Deferred or Further Discussion, where the property's scope is not yet determined and requires a specific decision before it can be classified.

A domain scope map does not resolve every complexity in the estate. It resolves the question of which complexities belong in this workshop and which do not.

The Unexpected Category: Further Discussion Required

On a recent program, one property could not be cleanly assigned to any of the standard categories. It was a significant revenue-generating platform, closely related to the primary digital estate, with its own technical stack managed by an external vendor. The question of what to do with it in Phase 1 depended on three things: the outcome of a vendor transition, the result of a product-market fit review, and a business model decision that had not yet been made at the leadership level.

The instinct in those situations is to include the property in scope with caveats ('subject to vendor transition timeline') and allow the workshop to proceed. We did not do that. We put the property in a separate, explicitly flagged row on the scope map with the label 'Further Discussion Required' and five specific questions that needed answers before the property could be scoped.

The effect on the workshop was immediate. Because the scope map had been distributed in advance, every participant arrived knowing that this particular property was out of scope for the workshop discussion. The navigation decisions, the taxonomy decisions, and the IA principles; none of them depended on this property being resolved. When someone raised it in the workshop, the facilitator could point to the scope map and say: 'That one is in the further discussion register. Here are the five questions that need answering and the people who own each one.'

The conversation moved on. An hour of scope derailment did not happen. The property's questions were addressed separately, with the right people in the room, on a timeline that suited the complexity of the decision rather than the schedule of an IA workshop.

What A Scope Map Is Not

A scope map is not a project plan. It does not sequence work or show timelines. It does not replace the detailed scoping of individual features or the API readiness register.

A scope map serves as a shared reference that establishes common ground about what is and is not being discussed before any technical or design conversation begins. In a workshop with ten stakeholders from different parts of the organization, each carrying a different assumption about what 'in scope' means, that common ground becomes a prerequisite for the workshop being a useful use of everyone's time.

The right time to produce it is before the first IA workshop. The right audience for it is everyone attending any of the IA workshops. And the right test for it is a simple one: if any participant can point to a property in the estate and ask 'what are we doing with that', the scope map should have the answer, or it should explicitly state that the answer is still being determined and why.

Preparing for your first IA workshop and want a scope map that holds up? Let's build one with you.