Product design

Cyber Training Workspace

I reorganized a fragmented cyber-training experience into a persistent workspace where learners can see assigned plans, role progress, events, and next actions without jumping between tools.

Company
Ultimate Knowledge Institute
Industry
Education Technology
Role
UI/UX Director
Year
2020–2023

Project context

Case narrative leads with the challenge and problem solved.

Enterprise training can splinter into schedules, role requirements, messages, and course lists. The workspace needed to help users understand where they are, what role path they are on, and what deserves attention next. The case is intentionally text-led for now, focusing on challenge, constraints, decisions, and problem solved.

workspace UXenterprise traininglearning pathsdashboard systemscyber readiness

Case opening

Complex workflow design, enterprise UX, systems thinking, and production-aware interface organization.

What was broken
Cyber training workflows can sprawl across plans, events, notifications, progress tracking, and role requirements.
What I owned
I structured a desktop-style workspace around persistent navigation, role context, training-plan selection, connected learning activities, calendar awareness, event discovery, and notification filtering.
What changed
The case now focuses on the challenge: connecting training plans, role progress, events, and next actions into a usable readiness workflow.
Senior judgment

Treated training readiness as a workspace problem, not a course-catalog problem, so role context and next actions stay visible.

Product clarity index

What this case teaches.

State clarified
Plans, events, progress, and notifications stay readable in one workspace.
Roles separated
Training work stays oriented around learner readiness and assigned expectations.
Handoff stabilized
Reusable panels and navigation create a practical product-system model.
Constraint

Readiness work was split across plans, schedules, role expectations, events, progress, and notification noise.

Decision

Use a persistent workspace model with assigned plan state, role context, and operational panels in one environment.

Proof

The evidence sheet connects lobby entry, Training Center, roadmap activity, calendar/progress, and notifications as one sequence.

Ownership / workflow

What I owned in the product story.

This is the enterprise workflow case: dense training obligations became a role-aware workspace with clearer next actions and reusable interface regions.

Role
UX architecture, interface direction, workspace model, product-system organization.
Scope
Lobby, Training Center, assigned plans, learning paths, calendar, events, role progress, and notifications.
Tools / workflow
Figma workspace modeling, systems thinking, component-state planning, product narrative and handoff logic.
Hiring signal
Can untangle enterprise workflow complexity without turning the interface into dashboard noise.

Challenge / response / outcome

From scattered training inputs to a role-based readiness workspace.

Cyber training workflows can sprawl across plans, events, notifications, progress tracking, and role requirements.

I structured a desktop-style workspace around persistent navigation, role context, training-plan selection, connected learning activities, calendar awareness, event discovery, and notification filtering.

Design response

The product challenge became an information-architecture problem.

  • Reframed cyber training as a workspace with context, state, and navigation instead of a flat catalog of courses.
  • Connected training plans, role progress, learning paths, calendar events, and notifications so readiness can be understood in one environment.
  • Made roadmap-style learning feel sequenced and assigned, reducing the feeling of scattered tasks across separate tools.
  • Kept the narrative focused on the workspace challenge so the case reads as product judgment instead of artifact inventory.

What to notice

Interface decisions that prove the product thinking.

  1. Role contextKeep the learner oriented around assigned readiness expectations instead of dumping them into a course catalog.
  2. Sequenced pathTurn plan cards and roadmap steps into a visible progression from next action to completion.
  3. Operational awarenessBring calendar events, notifications, and role progress into the same workspace so priority stays visible.

Mess

Role requirementsCourse listsCalendar eventsProgress trackingNotificationsOperational context

Design move

From scattered training inputs to a role-based readiness workspace.

Create a workspace model that gives each type of information a clear place: lobby, Training Center, calendar, notifications, and progress panels.

Clarity

Enter workspaceReview assigned planFollow connected activitiesCoordinate around eventsMonitor progress and notifications

Next step

Need someone to untangle a product flow like this?

Bring me in for senior product design, interface systems, workflow cleanup, and production-aware UI direction.