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 CASE / REDACTEDUnified identityBenefit rulesCross-context experience
Redesigned explanatory system view for Multi-service Membership Experience

PROJECT CONTEXT / DESIGN JUDGEMENT

Understand the operation before deciding how the system should appear.

01 / CONTEXT

When service spans multiple contexts, the member experience depends on identity, benefits and service history remaining continuous throughout.

02 / DESIGN FOCUS

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.

03 / OPERATING LOGIC

Identity core, Service network, Experience evolution remain connected so interface, workflow and back-office capability can evolve on one route.

SYSTEM MODEL / THREE CONNECTED LAYERS

Multi-service Membership Experience is more than a single interface.

J1

Identity core

Accounts, profiles and authorisation

J2

Service network

Benefits, orders and contextual response

J3

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.

  1. 01Information and benefit model
  2. 02Service interface prototypes
  3. 03Unified identity engineering plan

Working through a similar problem? Start by clarifying the boundary.

Discuss a project ↗