Factory Studio — personas and journeys¶
Target
This page describes intended behaviour or structure. No implementation is claimed unless a section is explicitly marked Current implementation or Evidence.
Personas are the seven roles of D18 and ADR-0015, not marketing archetypes: a persona may open the screens its role may open and act where the owning platform allows. Journeys are the nine flows of the flows catalog; together they cover every experience requirement FUX-01 to FUX-12 at least once.
Personas¶
| Persona | Role | Goals | Pain points today | Work areas |
|---|---|---|---|---|
| Dana, the requester | Requester | Submit work with the right scope, profile and limits; know what waits on me | Opaque run state; toasts without outcomes | Workspace, Software Factory, Intelligence |
| Yoav, the reviewer | Reviewer | Decide on the exact proposal shown, with evidence | Approvals that drift; no separation of duties | Workspace, Quality & releases |
| Lena, the asset maintainer | AssetMaintainer | Take assets from Draft to Published with evidence; act on learning proposals | Publishing without evaluation; vendor model names | Assets, Quality & releases, Software Factory |
| Omer, the operator | Operator | Keep the Factory and products within objectives; resolve incidents with evidence | Alerts without context; rollouts bypassing gates | Operations & usage, Software Factory |
| Noa, the workspace admin | WorkspaceAdmin | Onboard projects and people under policy; control budgets, retention, residency | Settings scattered; no evidence of changes | Governance & administration, Operations & usage |
| Eli, the platform admin | PlatformAdmin | Publish policies, profiles and templates tenants may only tighten; certify publishers and connectors | Overrides that loosen controls; unverified deployments | Governance & administration, Assets |
| Maya, the observer | Observer | See state and evidence without acting | Views that imply actions she cannot take | Operations & usage, Quality & releases |
Journeys¶
| Journey | Persona | FUX covered | Page |
|---|---|---|---|
| Submit an assessment run | Requester | FUX-01, 03, 04, 08 | flow |
| Review and decide on an exact proposal | Reviewer | FUX-05, 06 | flow |
| Recover a failed or stuck run | Operator | FUX-04, 07 | flow |
| Publish an asset release | Asset maintainer | FUX-02, 05, 10 | flow |
| Govern knowledge, memory and usage | Workspace admin | FUX-01, 08, 09 | flow |
| Operate the product fleet | Operator | FUX-04, 05, 11 | flow |
| Manage editions and billing | Workspace admin | FUX-08 | flow |
| Onboard a project | Workspace admin | FUX-01, 03 | flow |
| Off-board a tenant or product and export | Workspace admin | FUX-05, 11 | flow |
FUX-12 (documented views) is satisfied by every screen linking to its catalog entry and its owning platform's design page from the help affordance of the shell.
Journey map¶
journey
title A requester's run, from submission to artifacts
section Submit
Pick scope and release: 4: Dana
Set profile and limits: 4: Dana
section Wait
Watch the timeline: 5: Dana
Approval requested: 3: Dana, Yoav
section Decide
Review exact proposal: 5: Yoav
section Finish
Read artifacts with lineage: 5: Dana
See usage by status: 4: Dana, Noa
Hold "Alt" / "Option" to enable pan & zoom