Learn Overview

Problem

Enterprise customers had no scalable way to assign, track, or measure secure-code learning.

Outcome

Delivered a scalable enterprise feature that enabled secure-code learning across teams and accelerated enterprise adoption.

The Snyk Learn platform later won a Silver Award at the 2025 Anthem Awards for Responsible Technology — highlighting both the business impact and the product’s value in advancing developer education.

My contribution

I identified key behavioural patterns from customer calls that revealed how AppSec teams were struggling to manage hundreds of developers. These insights reshaped the product direction and focus on building scalable of Assignments.

From pattern to Jobs-to-be-Done (JTBD)

From customer research, we learned that:

‍• One AppSec manager often supports hundreds of developers, they needed a scalable, low-maintenance way to assign lessons.
• Progress was invisible across teams, they needed clear tracking, completion states, and nudges before due dates.
• Enterprise customers required compliance evidence ,they needed reliable documentation of who completed what, and when.

These insights informed the core JTBD:

Figure 1: AppSec Persona JTBD

OOUX Exploration

Before designing Assignments, Snyk Learn already included lessons, learning paths, and certificates.
‍
To integrate Assignments into the system cleanly, I mapped the object model and relationships across the ecosystem. This alignment created a shared understanding between design, engineering, and PM — reduced ambiguity and ensuring we built a scalable foundation.

Figure 2: Snyk Learn's Object Glossary

Figure 3: Object relationships map

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

CTA Refinement

Using the OOUX model and JTBD insights, I revisited the four original CTAs and regrouped them into two functional areas aligned with user intent:

‍Manage Assignment → Create, edit, delete
‍View Progress → Monitor completion and performance

This simplification clarified role ownership, and made the system more scalable.

Figure 5: CTA refinement

Zoom-in: Manage assignments

I explored early interactions using post-its and rough layouts to quickly validate workflows with the team and users.

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

Initially, the model included an assignmentID and learning path association.
After discussions with engineering, PM, and content, we intentionally simplified the model — removing those relationships to create a flatter, faster-to-ship structure.This decision accelerated MVP delivery and created a more flexible foundation for future iterations.

Wireframe flow

Based on the refined object model, I created wireframe flows covering key scenarios to mange assignments:
• Creating an assignment
• Deleting an assignment
• Changing due dates

These flows helped us validate interaction logic, edge cases, and long-term scalability before moving into visual design.

Figure 7: Wireframe flow