Didn't have time to read - TL;DR
3 key takeaways
1
Design for reality. Real organisations are deep, inconsistent and always changing, so the platform is built to work with actual structures rather than idealised ones.
2
Make structure legible. A disciplined register tree with clear hierarchy and predictable behaviour lets users recognise their organisation instead of interpreting the interface.
3
Absorb the complexity. Navigation should carry the organisational quirks so users do not have to, keeping the structure intact while the experience becomes easier.
Organisations work within complex multi layered structures. They are constantly evolving and often inconsistent. Structures run deep. Naming overlaps. Responsibilities cut across formal hierarchies. For risk and governance teams, this is the reality they manage every day. A reality that Clew works with seamlessly.
Designing for the environment risk teams operate in
Clew connects objectives, risk and assurance across the organisation. That means the platform reflects how governance actually operates.
Risk managers need to:
Risk managers need to:
- understand performance across the organisation for executive reporting
- navigate deep structures to understand where risk sits
- work with operational users within specific parts of the business
This requires a system that works with real organisational structures, not ideal ones.
Clew already supports this complexity. The navigation strengthens how users work within it, making structure easier to understand, navigate and act on.
Clew already supports this complexity. The navigation strengthens how users work within it, making structure easier to understand, navigate and act on.
Making structure legible
The navigation redesign introduces a more disciplined organisational structure. A tree structure that makes hierarchy immediately recognisable, so users don't need to interpret it. They recognise it.
The register tree expresses:
The register tree expresses:
- clear hierarchy
- predictable expansion behaviour
- consistent parent and child relationships
Structure becomes immediately recognisable. This reduces cognitive load and increases confidence.
Key point
Users do not need to interpret the interface. They recognise the organisation they work in.
Absorbing complexity, not exposing it
One of the core principles of the redesign is that navigation should absorb complexity, not amplify it. Users should not need to interpret organisational quirks in order to do their job. That responsibility sits with the platform.
Hierarchy, filtering and context work together to present a clearer view of what already exists. The structure remains intact. The experience becomes easier to understand.
Hierarchy, filtering and context work together to present a clearer view of what already exists. The structure remains intact. The experience becomes easier to understand.
Why this matters
Users lose orientation. They rely on workarounds. They disengage from deeper parts of the system.
The redesign ensures every part of your organisation is expressed in a clear, consistent and learnable way.
The redesign ensures every part of your organisation is expressed in a clear, consistent and learnable way.
A system that assumes ideal conditions will fail in a real environment.
The outcome
A platform that absorbs your complexity, makes it clear and encourages exploration and deep understanding.
Clew is a risk and assurance platform built around the Golden Thread, the traceable link from strategic objectives to the controls that manage them and the exposure that remains. We write about making risk management a working discipline rather than a compliance exercise.