Duration

8 months (2023)

Tools

Figma (Design, Figjam), Notion, Github, Paper

The challenge

Users needed to track their progress through pathways and campaigns, but the system didn't handle edge cases well, like archived content, locked stages, unclear status. Nobody knew what was unlocked, what was next, or what they'd already finished.

Context

A progress tracker keeps users engaged in their learning journey. It should show current status, unlocked content, and what's coming next, driving motivation and participation in the learn/earn ecosystem.

The solution

I designed a visual progress tracker that maps pathway and campaign stages clearly. The system handles edge cases (archived content, access limitations) while ensuring users always know what they've accomplished and what's next

In this case study

Discovering the research

Defining the barebones user journey

Information architecture

Prioritisation and breaking down the work

Results & outcomes

Discovering the research

Progress tracking sounds straightforward until you actually try to build one.

I started with a lot of "known unknowns." What were we tracking exactly? Completion? Time spent? State changes? What did progress even mean in a learn/earn context?

So I did what I always do. I wrote it all down. Every assumption, every question. I needed to make the mess visible before I could shape it into something useful.