Ideas — Dashboard Designs (one per role)
Every dashboard must satisfy the design principle: answer “what’s the next behavior I expect, and what fires if it doesn’t?” for the user in front of it. Below: what each role’s home screen should foreground, derived from the flows + user stories.
Participant dashboard
Foreground: my current phase + my next action. - A phase ribbon (Prepare → Engage → Practice → Apply → Reflect → Adjust) with “you are here.” - One primary CTA = the next expected behavior (e.g., “Submit your action plan,” “Log your first application”). - Locked-resources tile (visible-but-greyed) as the return hook. → locked resources - IS intro video on the workshop card. → intro video - Application gate countdown in Apply (“48h to your first try”). - Certificate appears (gated) only after survey. No scores anywhere.
Instructional Strategist dashboard
Foreground: who’s stuck + what to do about it. - Priority queue (top of screen): new engagements + stuck participants. (From image5.png “New ‘Needs attention’ items?” gate.) - Context Brief entry per upcoming engagement, available ≥3 days out. → context layer - Strategist Insights strip: % logged in, % watched intro, pulse aggregates, outliers. - Time-to-apply panel with the 24h/48h/5d thresholds rendered as the actual decision view. - Mark complete as a deliberate, consequential action (it fans out to survey + certificate + tracking window). - Per-participant data is one click behind an explicit, logged action (patterns by default).
Learning Administrator dashboard
Foreground: readiness in, impact out. - School Context Profile status card (“complete / needs update,” <5 min, timestamped). - Cohort Snapshot per upcoming engagement. - Participation monitor — logins, pulse-completion, gaps (aggregates only, [C3]). - Cohort outcomes / school-impact view — completion, application rate + speed, repeat-application rate, evidence; exportable for leadership. - Next-engagement signal lands here first (LA-first rule) — the renewal champion surface. → business loop
Platform Manager dashboard
Foreground: coherence + signals. - Engagement setup pipeline (HubSpot pull or manual entry → content association). - Video approval queue. → intro video - Publishing rules editor (4 visibility states, defaults + per-engagement override log). → content visibility - Cross-engagement analytics — filterable by readiness / change load / priority; at-risk + high-perf flags. → metrics - Renewal/expansion + case-study outbox to HubSpot. - Guardrail enforcement status (no individual scores, patterns-only).
Content Creator dashboard (provisional)
Foreground: the backlog + the definition of “done = application-oriented.” - Gap-driven backlog fed by PM + IS signals, ranked. → content creator questions - Authoring surfaces for workshop intro text [B1], pulse MCQs [C2], microlearning. - Microlearning library with the gap-matching taxonomy. - (Aspirational) impact feedback — did my item move time-to-apply for the cohorts that got it? - Blocked on the working session — see content-creator-role.
Cross-dashboard conventions
- Shared phase vocabulary on every screen (the 6 stages). → cycle
- Every metric ties to application speed or frequency — never raw completion.
- Every view drives a next action — no read-only dead-ends.
- Aggregates by default, individual data behind a logged action.
- Color/shape language from the flowcharts (Appendix A): blue = phase header, green = standard step, purple = new-in-v3, yellow diamond = decision, orange = nudge/intervention.
Related
- Data model · Feature ideas
- Flow images
image2–image16in source-docs