WS27 Experience Architecture · Product Blueprint v1
Connected service relationship model
A non-linear product model showing how real working situations and CYA encounters enter through Action, Return or Explore, resolve in a Useful Experience, and connect to human-led activity, campaigns, programs or personal continuity only when useful.
Read the analysis01 · Entry can begin outside the product
Preserve the situation that brought someone here.
- Real working situation
A participant knows what is happening now, even if they do not know what content they want.
- CYA encounter
A live session, workplace visit, campaign, conference or practitioner can become a direct digital entry point.
- Existing relationship
Recent, repeated, saved, live or program continuity can shorten the route to something already trusted.
02 · Behaviour
Action / Return / Explore
Behavioural modes, not proposed navigation labels.
- ActionHelp me now
Recommendation before catalogue. Ask only what changes the answer.
- ReturnSomething I know works
Recent and trusted experiences remain close without requiring a dashboard ritual.
- ExploreI want to browse
Search, filters and richer taxonomy are legitimate when deliberate discovery is the participant’s intent.
03 · Centre of participant value
Useful Experience
A short practice, longer practice, live experience, campaign resource, program moment or another useful intervention. The architecture exists to shorten the route here, not to maximise content consumption.
04 · Appropriate continuity
Continue only when continuing is useful.
- End here
A useful experience can be complete without manufacturing another step.
- Human-led
Practitioner relationships, live sessions and workplace delivery can continue the same service.
- Campaign / event
Context is preserved from the moment that brought the participant into the Studio.
- Program
Structured continuity orchestrates useful experiences without importing LMS mechanics by default.
- Personal continuity
Recent, saved and repeated experiences can be remembered when identity creates enough value.
What changed
The model removes the content portal as the organising centre. Search, filtering, live experiences, campaigns, programs and personal history still exist where they solve a participant job, but none is allowed to define the whole Studio by default.
Evidence treatment
The model is reconstructed as ordered semantic groups rather than a flattened diagram image, preserving its relationships for keyboard, enlarged-text and assistive-technology use.
This is architectural evidence. It records the adopted product model and its relationships; it does not claim participant behaviour or full implementation of every continuation path.