Status: Accepted v1.0
Owner: OSHUN Design + Product + Engineering
Last Updated: March 26, 2026
Implements: V1-UX-049
Related:
docs/releases/v1/reports/current-state-redesign-inventory.mddocs/releases/v1/specs/surface-redesign-ranking.mddocs/releases/v1/design/customer-visual-thesis.mddocs/releases/v1/design/admin-visual-thesis.mddocs/releases/v1/specs/todos.md
1. Purpose#
This document defines before/after experience scorecards for the highest-impact OSHUN V1 surfaces.
The scorecards translate redesign language into measurable experience targets across six axes:
- clarity
- delight
- ergonomics
- speed-to-value
- trust
- cross-domain cohesion
2. Scoring Scale#
1: absent or unacceptable for V12: functional but friction-heavy or visibly below the target bar3: serviceable but inconsistent4: strong and reliable5: launch-grade and thesis-aligned
before scores reflect the current repo state captured in the redesign
inventory.
after scores are the minimum acceptable post-redesign targets for V1.
3. Scope Note#
These scorecards focus on P0 and P1 surfaces from
docs/releases/v1/specs/surface-redesign-ranking.md.
P2 and P3 surfaces inherit the cluster-level targets of the closest matching
scorecard and do not need separate launch-blocking scorecards yet.
4. Customer Web and PWA Scorecards#
| Surface | Priority | Clarity | Delight | Ergonomics | Speed-to-value | Trust | Cohesion | Why target matters |
|---|---|---|---|---|---|---|---|---|
| Shared shell chrome and persistent overlays | P0 | 3 -> 5 |
3 -> 4 |
3 -> 5 |
3 -> 4 |
4 -> 4 |
3 -> 5 |
The shell sets the tone for every authenticated web journey. |
| Home dashboard | P0 | 2 -> 5 |
2 -> 4 |
2 -> 5 |
2 -> 5 |
3 -> 4 |
2 -> 5 |
Home is the main time-to-value surface and currently carries too much dashboard gravity. |
| Explore and discovery | P0 | 2 -> 5 |
2 -> 4 |
2 -> 4 |
2 -> 5 |
3 -> 4 |
3 -> 5 |
Discovery has to feel broad without becoming noisy or generic. |
| Search results | P1 | 3 -> 5 |
2 -> 4 |
3 -> 4 |
3 -> 5 |
3 -> 4 |
3 -> 5 |
Search should feel fast, scannable, and obviously cross-domain. |
| Activity timeline and inbox | P1 | 3 -> 5 |
2 -> 4 |
3 -> 4 |
3 -> 4 |
3 -> 4 |
3 -> 5 |
Activity must summarize progress without turning into a noisy notification wall. |
| Library and continuity | P1 | 3 -> 5 |
2 -> 4 |
3 -> 4 |
3 -> 4 |
4 -> 4 |
3 -> 5 |
Library is the preserve surface and needs stronger continuity confidence. |
| Profile and operator handoff | P1 | 3 -> 5 |
2 -> 3 |
3 -> 4 |
3 -> 4 |
4 -> 5 |
3 -> 5 |
Profile has to feel clear, governed, and distinct from operator work. |
| Onboarding | P0 | 3 -> 5 |
2 -> 4 |
3 -> 5 |
3 -> 5 |
3 -> 5 |
2 -> 5 |
Onboarding must quickly explain one shell and five domains without overload. |
| Domain route experience | P0 | 3 -> 5 |
2 -> 4 |
3 -> 4 |
3 -> 4 |
3 -> 4 |
2 -> 5 |
This is the major shared surface where cross-domain cohesion either works or fails. |
| Assistant, continuity, and disclosure surfaces | P0 | 3 -> 5 |
3 -> 4 |
3 -> 4 |
3 -> 4 |
3 -> 5 |
3 -> 5 |
Trust, disclosure, and memory handling must feel premium and legible. |
| Public welcome landing | P0 | 2 -> 5 |
2 -> 5 |
3 -> 4 |
2 -> 5 |
3 -> 4 |
2 -> 5 |
This is the first impression and public conversion surface. |
| Public domain marketing pages | P1 | 2 -> 4 |
2 -> 4 |
3 -> 4 |
2 -> 4 |
3 -> 4 |
2 -> 5 |
Domain marketing has to explain differences without fragmenting the brand. |
| Public download and install page | P1 | 3 -> 5 |
2 -> 4 |
3 -> 4 |
3 -> 5 |
3 -> 4 |
3 -> 5 |
Distribution success depends on a clean app-store and install handoff. |
| Global loading, error, degraded, and not-found states | P0 | 2 -> 5 |
1 -> 4 |
2 -> 5 |
2 -> 5 |
2 -> 5 |
2 -> 5 |
Failure and recovery states are beta-tested and must feel calm instead of broken. |
5. Customer Mobile Scorecards#
| Surface | Priority | Clarity | Delight | Ergonomics | Speed-to-value | Trust | Cohesion | Why target matters |
|---|---|---|---|---|---|---|---|---|
| Mobile shell, tab layout, and persistent helpers | P0 | 3 -> 5 |
3 -> 4 |
4 -> 5 |
4 -> 5 |
3 -> 4 |
3 -> 5 |
Mobile shell ergonomics determine whether OSHUN feels coherent on the go. |
| Home tab | P0 | 2 -> 5 |
2 -> 4 |
2 -> 5 |
2 -> 5 |
3 -> 4 |
2 -> 5 |
Mobile home must support one-handed time-to-value, not just compressed dashboard density. |
| Explore tab | P1 | 2 -> 4 |
2 -> 4 |
2 -> 4 |
2 -> 4 |
3 -> 4 |
3 -> 5 |
Explore needs better scan rhythm and lower discovery friction. |
| Activity tab / notification inbox | P1 | 3 -> 5 |
2 -> 3 |
3 -> 5 |
3 -> 4 |
3 -> 4 |
3 -> 5 |
This is where mobile continuity and notification trust converge. |
| Library tab | P1 | 3 -> 5 |
3 -> 4 |
3 -> 4 |
3 -> 4 |
4 -> 4 |
3 -> 5 |
Library should feel durable and low-friction on smaller screens. |
| Profile tab | P1 | 3 -> 5 |
2 -> 3 |
3 -> 4 |
3 -> 4 |
4 -> 5 |
3 -> 5 |
Profile is the governance surface for customer mobile. |
| Domain detail route | P0 | 2 -> 5 |
2 -> 4 |
2 -> 5 |
2 -> 4 |
3 -> 4 |
2 -> 5 |
Domain detail is where the five domains either harmonize or fracture on mobile. |
| Notification and alert settings components | P2 | 3 -> 4 |
2 -> 3 |
3 -> 4 |
3 -> 4 |
4 -> 5 |
3 -> 4 |
Important support surfaces, but not first-wave redesign blockers. |
| Offline and degraded-state surfaces | P1 | 4 -> 5 |
2 -> 4 |
4 -> 5 |
4 -> 5 |
4 -> 5 |
3 -> 5 |
This is a real strength and should be preserved while made calmer and more premium. |
| Dedicated mobile onboarding route | P0 | 1 -> 5 |
1 -> 4 |
1 -> 5 |
1 -> 5 |
1 -> 5 |
1 -> 5 |
The missing onboarding route is a launch blocker because the product needs a real mobile first-run story. |
6. Admin Web and Studio Scorecards#
| Surface | Priority | Clarity | Delight | Ergonomics | Speed-to-value | Trust | Cohesion | Why target matters |
|---|---|---|---|---|---|---|---|---|
| Explicit admin shell boundary and operator chrome | P0 | 3 -> 5 |
2 -> 4 |
3 -> 5 |
3 -> 5 |
4 -> 5 |
3 -> 5 |
The operator shell has to feel intentionally different from customer space without becoming visually harsh. |
| Studio root cockpit directory | P0 | 2 -> 5 |
2 -> 4 |
2 -> 5 |
2 -> 5 |
3 -> 5 |
2 -> 5 |
Operators need a real cockpit home, not a launcher list. |
| Identity, access, and policy cluster | P0 | 2 -> 5 |
1 -> 3 |
2 -> 5 |
2 -> 4 |
3 -> 5 |
2 -> 5 |
These are high-trust operator surfaces where ambiguity is unacceptable. |
| Review, audit, notification, and retention cluster | P0 | 2 -> 5 |
1 -> 3 |
2 -> 5 |
2 -> 5 |
3 -> 5 |
2 -> 5 |
This is the closest current shape to the eventual admin product and must become launch-grade. |
| Reliability, incident, and launch-readiness cluster | P0 | 2 -> 5 |
1 -> 3 |
2 -> 5 |
2 -> 5 |
3 -> 5 |
2 -> 5 |
Operators must be able to scan, respond, and recover without noise or disorientation. |
| Integration and composition cluster | P1 | 3 -> 4 |
1 -> 3 |
2 -> 4 |
3 -> 4 |
3 -> 5 |
3 -> 4 |
Important operator workflows, but not the first admin redesign gate. |
| Design system governance cluster | P2 | 3 -> 4 |
2 -> 3 |
3 -> 4 |
3 -> 4 |
4 -> 5 |
3 -> 4 |
Specialist workspaces need polish, but they are not the first cockpit bottleneck. |
| Navigation, discovery, and context-governance cluster | P2 | 3 -> 4 |
2 -> 3 |
3 -> 4 |
3 -> 4 |
3 -> 5 |
3 -> 4 |
Important, but downstream from the first operator-shell wave. |
| Isis operator family | P2 | 3 -> 4 |
1 -> 3 |
2 -> 4 |
3 -> 4 |
3 -> 5 |
3 -> 4 |
The most launch-relevant specialist family still needs a more finished operator presentation. |
7. Admin Mobile Scorecards#
| Surface | Priority | Clarity | Delight | Ergonomics | Speed-to-value | Trust | Cohesion | Why target matters |
|---|---|---|---|---|---|---|---|---|
| Dedicated admin mobile app shell | P0 | 1 -> 5 |
1 -> 3 |
1 -> 5 |
1 -> 5 |
1 -> 5 |
1 -> 5 |
The product does not exist yet despite being launch-critical in the PRD. |
| Queue triage and urgent approvals | P0 | 1 -> 5 |
1 -> 3 |
1 -> 5 |
1 -> 5 |
1 -> 5 |
1 -> 5 |
This is the defining admin-mobile use case and currently has no dedicated surface. |
| Incident and on-call companion | P0 | 1 -> 5 |
1 -> 3 |
1 -> 5 |
1 -> 5 |
1 -> 5 |
1 -> 5 |
Admin mobile must support urgent escalations and incident awareness to satisfy the PRD. |
8. Exit Use#
These scorecards are not abstract commentary. They are the redesign acceptance targets for the next UX work.
A surface should not be considered redesign-complete until evidence exists that
it has met or exceeded the after targets on its applicable scorecard.