Learn Overview

Snyk Learn set out to make security education more accessible and actionable within the developer workflow.
‍
My role: I led the end-to-end design process across the product, from lessons and learning paths to assignments. For this case study it will be focusing on the Manage Assignment experience.

Outcome: Launched a scalable enterprise feature that enables secure-code learning at scale and now a key driver of enterprise adoption.

  1. 🧢 Role

    Product Designer

  2. 🙌 Collaborator

    Product Manager, Developers, Content  Managers, Product Designers, Product Marketing Managers, Brand Designers

  3. 🗓️ Date

    2021-2024

OOUX Exploration

A structured exercise to map core learning objects and their relationships, helping define how content should be organized and surfaced to users.

Figure 1: Snyk Learn's Object Glossary

Figure 2: Object relationships map

Figure 3: Objects, metadata, core content and CTA map, focusing on ASSIGNMENT

Jobs-to-be-Done (JTBD)

From our customer calls, we learned that one AppSec manager often supports hundreds of developers.
They needed a scalable way to assign lessons, track progress, and measure learning impact efficiently, without micromanaging.

This insight shaped the following JTBD statement, summarizing the core user goal:

Figure 4: AppSec Persona JTBD

CTA Refinement

With that understanding, I revisited the OOUX model to ensure system actions aligned with user intent.
I grouped the original four CTAs into two clear functional areas:
‍
• Manage Assignment: Create, edit, and delete assignments
• View Progress: Monitor completion and performance

This refinement clarified role ownership and simplified system logic — making it easier to scale while staying aligned with user goals.

Figure 5: CTA refinement

Zoom-in: Manage assignments

I brought post-it to start putting down on to screen, here is one example of how the manage assignments looks like.

Figure 6: Translating post-its from OOUX exploration to initial manage assignment wireframe

Initially, the Assignment model included both "assignmentID" and a "learning path" relationship.After discussions with the tech team, PM, and content manager, we decided to simplify — removing these layers to keep the structure flatter and reduce delivery time for the MVP. This trade-off allowed us to validate the workflow faster while keeping future scalability in mind.

Wireframe flow

Building on the refined OOUX model, I created a wireframe flow capturing key scenarios: creating, deleting, and updating due dates for assignments.This helped validate both interaction logic and scalability before investing in visual design.

Figure 7: Wireframe flow

Final design

After multiple iterations, here’s the final design for Manage Assignment.
‍
It balances structure and flexibility — allowing Admins to assign lessons quickly, view progress at a glance, and keep learning momentum across teams.Outcome: A streamlined MVP launch that set the foundation for scalable learning management, now contributing to measurable engagement growth across enterprise teams.

Figure 8: Manage assignment final design