Duration

4 months (2024)

Tools

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

<aside> ‼️

A note on visual design

Due to branding constraints and the need for rapid iteration across multiple product lines, the design system prioritised functional clarity over visual innovation. Most interfaces defaulted to a neutral black-and-white palette with minimal colour usage.

</aside>

The challenge

Onboard worked, technically. But users were finding workarounds, like joining the wrong quests, tracking their own progress manually, messaging admins to do things the platform should have handled.

Context

Onboard is StackUp's platform for community engagement and quest creation. The initial release functioned but lacked cohesion — disconnected flows, features people couldn't find, and infrastructure that couldn't scale. The redesign was about fixing all of that at once.

The solution

I led the full redesign - from auditing every existing flow and component to rebuilding the information architecture, redesigning the interface, and extending Onboard's component patterns into StackUp's broader design system. The goal was a foundation cohesive enough to grow with the product.

In this case study

What the behaviour was telling us

Designing for two different kinds of progress

Restructuring around momentum, not internal logic

Cutting to what matters

What changed

Beyond Onboard: lifting the whole ecosystem

What the behaviour was telling us

I started by auditing every screen, component, and flow, tagging inconsistencies and friction points throughout. Then I cross-referenced with user behaviour data: where people abandoned tasks, where they created workarounds, where they messaged support for things that should have been self-serve.