A map-based operating model for seeing ownership, controls, dependencies, and escalation paths.
- Year
- 2025
- Focus
- Mapping ownership and controls
- Role
- Service design, systems mapping, product strategy, stakeholder facilitation
- Themes
- Governance, Operating models, Systems mapping, Enterprise UX
How can people navigate ownership and escalation without knowing the whole organisation by memory?
Case specimen
Mapping ownership and controls
- Messy inputs
- Product owners · Controls · Dependencies · Escalation paths
- Working frame
- Represent governance as connected roles, controls, dependencies, and decision paths rather than isolated lists.
- Decision enabled
- Help teams identify the right owner, required control, and escalation route for a product issue.
- What changed
- The atlas gave stakeholders a shared way to discuss how governance actually moves through the organisation.
The situation
Context
Complex organisations often hold governance knowledge in documents, systems, and people's heads. The product opportunity was to make that operating model visible.
Problem
Users needed to understand relationships between products, owners, controls, risks, and escalation paths without navigating multiple disconnected references.
The work
My role
I shaped the map metaphor, defined the object relationships, and facilitated conversations around how governance knowledge should be structured.
What made it hard
The difficult part was deciding what to show at each level of detail so the map helped orientation instead of becoming another complex diagram.
Process
I started with domain mapping, then translated the relationships into layers for overview, ownership, control detail, dependency tracing, and escalation.
Key design decisions
The design prioritised progressive disclosure, clear object labels, and movement from map overview to a specific next action.
What it changed
Outcome
The concept helped stakeholders see governance as a connected operating model and created a foundation for more actionable product oversight.
What I learned
Maps are useful when they help someone decide where to go next. A beautiful map without action paths is still only documentation.
What I would do differently
I would validate the information architecture with real escalation scenarios and measure whether users find the correct owner faster.