A governance product for helping teams understand product, risk, and third-party oversight.
- Year
- 2026
- Focus
- Governance without overload
- Role
- UX strategy, dashboard design, workflow modelling, stakeholder alignment
- Themes
- Enterprise UX, Governance, ServiceNow, Dashboards, Systems thinking
How can teams understand ownership and risk across a complex organisation?
Case specimen
Governance without overload
- Messy inputs
- Product ownership · Control status · Risk signals · Operational actions
- Working frame
- Connect product, owner, control, and risk objects into a role-based view of what requires attention.
- Decision enabled
- Help teams move from passive reporting to knowing who owns the next action and why it matters.
- What changed
- Stakeholders could discuss governance as operational stewardship instead of another dashboard layer.
The situation
Context
Product governance sits between business accountability, technical platforms, and operational controls. The experience needed to support different users without becoming another reporting layer.
Problem
Teams needed to see what required attention, understand ownership, and act on product risk without stitching together information from multiple systems.
The work
My role
I designed dashboard structures, prioritisation views, object relationships, and governance journeys that could work inside an enterprise platform environment.
What made it hard
The difficulty was not showing more data. It was deciding which signals deserved attention and how to create a useful path from insight to action.
Process
I worked from stakeholder interviews, artefact reviews, and workflow mapping to define core objects, views, decision moments, and escalation patterns.
Key design decisions
The design emphasised role-based summaries, ownership clarity, status explanations, and action surfaces that made governance feel operational rather than bureaucratic.
What it changed
Outcome
The work established a product direction for a more coherent governance experience and helped align stakeholders around shared product and risk language.
What I learned
Enterprise dashboards become useful when they are designed around decisions and responsibilities, not around every metric available.
What I would do differently
I would invest earlier in a shared domain model so every screen, control, and metric could map back to the same conceptual structure.