Publish Trainings

Admins could assign training requirements by employee — and schedule future publishes — without losing track of what was already live, what was pending, and what each person still needed to complete.

Role Product Designer Company ISN Shipped

Stack

Figma

User research

Cross-functional collaboration

Problem

Training admins had no way to schedule training assignments in advance or view them organized by employee. Publishing was an all-or-nothing action — no staging, no future scheduling, no employee-level visibility. Managing large training programs meant coordinating across systems instead of working inside one.

Intervention

Designed a publish flow with future-scheduling support and an employee-level training view. Admins can set a publish date, see what each employee is assigned, and manage live and pending trainings from a single surface — without losing the current program state while planning the next one.

Outcome

Training programs became plannable. Admins could work ahead without disrupting what was already live — giving teams the ability to coordinate onboarding, compliance windows, and policy updates without scrambling at the last minute.

Impact

Schedulable

Future publish dates let admins plan training assignments in advance

Employee-level view

Per-employee training breakdown replaces program-wide guesswork

No disruption

Staging and future publishes preserve live program state while planning ahead

Design artifacts are protected

Screenshots and design files for this project are kept confidential out of respect for the client. If you'd like to review them as part of a hiring or collaboration conversation, reach out directly.

01 / Research

Research

Talked to training admins about how they were managing program rollouts — what was working, what required workarounds. Scheduling future trainings and tracking per-employee status kept surfacing as manual, error-prone work that should have been handled inside the platform.

02 / Define

Define

Defined two primary features: a future publish scheduling flow and an employee-level training breakdown. Both needed to coexist with the existing publish experience — adding capability without requiring admins to relearn a workflow they already knew.

03 / The hard call

The hard call

The employee-level view could have been a fully separate reporting surface. Instead, it was embedded directly in the publish flow — because the moment admins need per-employee visibility most is exactly when they're deciding what to publish and to whom.

"Context at the moment of decision — not one more screen away from where the work happens"

04 / Ship & Watch

Ship & Watch

Shipped and tracked how often future publish dates were being used relative to immediate publishes. Adoption of the scheduling feature validated that admins had been working around the gap — they were ready for this the moment it was available.