Experience and workflow maps
Record the primary user journeys alongside the backstage workflows that support them. This makes it easier to see which internal process a customer-facing change will affect.
Architecture and integration map
Document the major components, data boundaries, third-party services, environments and credentials ownership. The goal is not a diagram for display. It is a map someone can use during an incident or migration.
Evidence, not assurances
Keep accessibility checks, security decisions, performance baselines and critical journey tests close to the system. Future teams should be able to repeat the checks instead of trusting a launch-day claim.
A runbook and a next horizon
Explain deployment, rollback, backup, recovery and common operational tasks. Pair that with a ninety-day roadmap so the organisation knows what to observe, improve and defer.