When service spans multiple contexts, the member experience depends on identity, benefits and service history remaining continuous throughout.
CASE FILE / 10 · ECOSYSTEM / EXPERIENCE
Multi-service Membership Experience
When service spans multiple contexts, the member experience depends on identity, benefits and service history remaining continuous throughout.

PROJECT CONTEXT / DESIGN JUDGEMENT
Understand the operation before deciding how the system should appear.
We organised unified identity, benefit rules, cross-context experience into a clear information hierarchy so each role can see state, take action and understand what comes next.
Identity core, Service network, Experience evolution remain connected so interface, workflow and back-office capability can evolve on one route.
ANONYMISED VIEW / DESIGNED FOR EXPLANATION
An illustrative redesign explains how the system works.
This visual has been recreated from project experience to explain product structure and workflow relationships. Names, roles, states and figures are not client production data.

SYSTEM MODEL / THREE CONNECTED LAYERS
Multi-service Membership Experience is more than a single interface.
Identity core
Accounts, profiles and authorisation
Service network
Benefits, orders and contextual response
Experience evolution
Feedback and service strategy adjustment
TEAM CONTRIBUTION / DELIVERY MATERIAL
The team's contribution should leave usable artefacts for the next stage.
The scope below summarises work that NINENAV core team members contributed to or produced across the relevant project experience, with outcomes teams can use, hand over and maintain.
- 01Information and benefit model↗
- 02Service interface prototypes↗
- 03Unified identity engineering plan↗
CAPABILITIES / RELATED WORK
Capabilities demonstrated in this case
Working through a similar problem? Start by clarifying the boundary.
Discuss a project ↗