Concept map

Screens by intent

Not a hierarchy, a map of screens grouped by what the person is trying to do. Six intents (A to F) derived from the flows and jobs. Each node carries a short job-tag; no X.Y numbers, no states, no content cards, those belong to the detail layer.

flowchart TD
    subgraph GA["A. Get started (acquire + sign up)"]
      gs1["Landing / home
Main, item 1"]
      gs2["Pricing
item 1"]
      gs3["Sign up
item 1"]
      gs4["Log in
supporting"]
    end
    subgraph GB["B. Set up wellbeing (onboarding)"]
      sw1["Company setup
J6"]
      sw2["First program confirm
Main, J6, item 2"]
      sw3["Invite team
Main, item 3"]
    end
    subgraph GC["C. Run wellbeing and read the pulse"]
      rw1["Dashboard
E1, J1, J2"]
      rw2["Team pulse detail
J1, J2, E1"]
      rw3["Threshold alert
J2"]
      rw4["Program library
Main, J6"]
      rw5["Program detail / manage
Main, item 2"]
      rw6["Check-in setup
J2, J4, item 3"]
    end
    subgraph GD["D. Team and check-ins"]
      tc1["Team roster
Main, item 3"]
      tc2["Check-in, employee
J3, J4, E2"]
      tc3["Pre-Q1 disclosure
J3, E2"]
      tc4["Questions
J4"]
      tc5["Check-in complete
J4, E2"]
    end
    subgraph GE["E. Prove it and upgrade (owner)"]
      pu1["Share with owner
J1, J5, S2"]
      pu2["Invite owner + upgrade
S2, item 8"]
      pu3["Owner dashboard
J1, J5, item 8"]
      pu4["Monthly owner digest
S2, item 8"]
    end
    subgraph GF["F. Account and utility"]
      au1["Plan / subscription
item 1, item 8"]
      au2["Privacy center
J3, E2, item 4"]
      au3["Notifications
J4, items 9-10"]
      au4["Account
supporting"]
      au5["System: 404 / 500 / cookie
all"]
    end
    gs3 --> sw1
    sw3 --> rw1
    rw1 --> tc1
    rw6 --> tc2
    tc2 --> tc3
    tc3 --> tc4
    tc4 --> tc5
    rw2 --> pu1
    pu1 --> pu2
    pu2 --> pu3
    rw1 -.-> au1

Navigation Model

Global navigation is the shortest path for the primary persona to her main job, not "what to put in a menu." Each global item is an entry into a job-cluster. The owner and employee surfaces have no multi-tab nav by design.

Global navigation (operator app)

Trade-off: "Owner" is only ~monthly-frequency and could be a contextual "Share this result" action instead. It is kept global because the owner dashboard is the paid feature and J1 / J5 / S2 score 3 for Priya. Reversible if usage shows it is rarely a fresh entry.

Depth: taps to the main job for Priya

Global / contextual / deep

Global (always visible): the 4 job tabs (Dashboard, Programs, Team, Owner) plus Settings utility. Owner surface = single dashboard; employee surface = no nav.

Contextual (inside a flow): "Share this result with your owner" (on a positive milestone), "Set up check-in" (inside a program), "Resend invite" (inside roster), threshold-alert banner (on the Dashboard when it fires), pre-Q1 privacy disclosure (inside the check-in), upgrade prompt (on a free-tier limit).

Deep (rare): Plan / subscription change, Privacy center detail, Notification cadence, Account, and the one-time onboarding wizard.

Traceability Matrix

Screens (rows) by jobs (columns). A tick means the screen participates in closing that job. An empty row is an orphan screen; an empty column is an orphan job. Both are defects, surfaced and resolved below.

Orphan screens (empty rows)

Orphan jobs (empty columns)