Learning Dashboard

Keep learners oriented around active courses, progress, deadlines, recommendations, and recent learning activity. This example brings Home and My learning together so learners and course teams can find the next task without losing context.

It includes representative records such as Product Strategy Foundations and SQL for Product Analytics. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Learning Dashboard

Template facts

Screen

Workspace

Primary action

Browse courses

Pattern

Workspace

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product and growth teams need to browse courses while keeping courses active, weekly progress and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Home gives users an obvious place to start.
  • Supporting view: My learning keeps the related context close.
  • Primary action: Browse courses stays visible when people need it.
  • First signal: Courses active shows a useful value (4).
  • Second signal: Weekly progress gives additional context (68%).
  • Sample record: Product Strategy Foundations.
  • Next record: SQL for Product Analytics.

States worth designing

  • First-use empty state: say what changed, protect progress, and offer a clear next step.
  • Data panel loading: say what changed, protect progress, and offer a clear next step.
  • Stale status or conflict: say what changed, protect progress, and offer a clear next step.
  • Action completed: say what changed, protect progress, and offer a clear next step.
  • Insufficient permission: say what changed, protect progress, and offer a clear next step.
  • Network retry: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Home → My learning → Browse courses → Review outcome

Patterns used

Workspace, Home, My learning, contextual actions, error recovery

Why these choices work

Give the main job visual priority, keep supporting signals nearby and surface exceptions where people must act.

Pay attention to home and my learning. People need to distinguish Product Strategy Foundations from SQL for Product Analytics. Keep courses active visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “Browse courses”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Course Catalog, Course Detail, Lesson Player.

Start from this in Figr

Design a learning dashboard screen inside our existing product. Use our current components, tokens and content language. Include Home and My learning views, credible records like Product Strategy Foundations, and a clear “Browse courses” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr