Every product or service contains an Experience layer — the bridge between strategy, design, behaviour, and customer understanding. The best way to anchor this work is with a clear vision, a simple mission statement, or a manifesto. Define why you exist, include your content partner early, and ensure every output connects back to your knowledge base.

Experience Strategy sits at the heart of this section. It articulates how the different parts of your product connect, support one another, and create meaningful interactions for your customer. Ask yourself whether the strategy is fixed or evolving. The answer determines the channels, tooling, and cadence you need.

All experience-led mapping — blueprints, service maps, user journeys — should live in one accessible space. After decades spent switching from Confluence (in product environments) to InDesign and endless PDFs (in agency environments), and back again, the most scalable pairing remains Figma + Atlassian. Few systems match their combined clarity, versioning, and accessibility.

Information Architecture merges technical IA with content architecture. It captures how information flows, how it is structured, and how decisions are made. We will explore this further in a dedicated article series, but in the context of Design at Scale™, IA becomes the structural glue.

The Feature and Component Lists synthesise this knowledge into actionable design and engineering guidance. They focus not on documenting every detail but on clarifying relationships:

Features define behaviours.
Components carry information and handle data.

These pages are updated continuously, with only the latest version visible - giving business and engineering real-time visibility. Depending on delivery methodology (BDD or TDD), this space also contains user testing scenarios, sprint learnings, and design sprint archives.