L&D Training Intake & Operational Tracker

Interactive Training Intake & Prioritization Platform Prototype

The Problem

Learning & Development teams in a health plan receive a constant stream of training requests from across the organization — Quality, Member Services, Provider Networks, Clinical Operations. Without a structured intake, these arrive through email, hallway conversations, and spreadsheets, making it hard to see the full backlog, judge what matters most, or tell requesters where their project stands.

Critically, not all requests are equal: those tied to regulatory deadlines and quality metrics like HEDIS and CAHPS carry far more weight than routine support. The team will need a way to capture demand consistently, prioritize it objectively, and move it through to delivery transparently.

The Product & Target Audience

The product, designed and developed using Claude Design, is a single split-pane dashboard with two role-based experiences. Requesters use a guided intake wizard that scores each request the moment it's submitted; the L&D team works an operational backlog queue that sorts itself by strategic priority and carries each ticket from triage to delivery. One shared source of truth replaces the email-and-spreadsheet status quo. The dashboard is designed for use by the following audience:

• The Requester - Department staff & managers

Anyone across the health plan who needs a learning solution built. They submit requests and stay informed on progress — without chasing status updates.

• The Receiver - L&D/ID Teams

The team that triages the backlog, decides sequence, builds the training, and moves each request through to delivery. 

Key Features

Guided Intake Wizard - Captures initiative name, department, quality-program alignment, urgency tier, performance gap, and modality — including a free-text "Other" modality with inline validation.

Live Priority Scoring - A Strategic Priority Score (0–100) calculates as the form is filled, weighting healthcare quality metrics and regulatory deadlines most heavily.

Self-Sorting Backlog -New requests drop into a shared queue that re-ranks itself high-to-low by score. A sort toggle also offers low-to-high and most-recent views.

Role-Based Views - A Client Portal and an L&D Receiver view. A passcode gate keeps queue controls staff-only; requesters see status but can't change it.

Status Workflow - The L&D team advances each ticket (Triage → In Production → Delivered) or removes completed items so they leave the client view.

Session & Notifications - A demo employee-profile selector binds a requester email to each ticket; advancing a ticket fires a simulated email notification.

Design Decisions

The following design decisions influenced the overall appearance, flow, and function of the product:

Split-pane layout

Intake on the left, live operational data on the right — so submitting and its consequence (a ranked queue) are visible at once. Collapses to a stacked view on narrow screens.

High-contrast palette

A clinical teal-and-navy system signals trust appropriate to a health plan. Amber is reserved exclusively for regulatory and priority signals, so urgency reads instantly. Color always carries meaning.

Role-aware panes

The intake form is hidden from the L&D side — staff never submit requests, so that pane becomes a Pipeline Console showing stage counts, regulatory load, and scoring weights.

Session over login

Rather than a tedious account login, a demo profile selector simulates an active session and binds a requester identity to each ticket — enough to drive notifications without auth friction.

Smart defaults

Selecting a profile pre-fills the requesting department but leaves it editable for on-behalf-of requests. Micro-interactions — live score, flash-in cards, toasts — keep the system feeling responsive.

Deliverables

Interactive Prototype - The full working web app with both portals, as a self-contained standalone HTML file that runs offline.

Narrated Video Walkthrough - A ~2-minute onboarding video with recorded voiceover, captions, and a guided cursor for training new staff on both portals.

Future Considerations

Development considerations for future development are as follows: 

Persistence & backend - A database and accounts so submissions survive refresh and real users sign in.

Real notifications - Wire the status workflow to an email service — progress updates at each forward stage, with an opt-out.

Reporting - Throughput, average time-in-stage, and regulatory-load trends for L&D leadership.

Score transparency - A breakdown popover on each ticket showing exactly how its priority score was composed.