← All worknow showing ( 07 ) / 24

From lurking to participating

From lurking to participating key visual

onboard worked, but people kept working around it. i led the redesign, from auditing every flow to rebuilding the structure, and folded its patterns into stackup's design system.

Client StackUpDuration 4 months, 2024Role led the redesignTools figma, figjam, notion, clickup, paper
( 01 ) Context

a platform that functioned, and not much more.

onboard is stackup's platform for community engagement and quest creation. the first release worked, but the flows didn't connect and people couldn't find features. users joined the wrong quests and messaged admins to do things the platform should have handled.

↗︎↑ mostly black & white. brand rules and fast iteration came first.
( 02 ) Audit

i audited everything, then checked it against what people did.

i went through every screen and flow and tagged inconsistencies and friction. then i cross-referenced behaviour data: where people abandoned tasks or invented workarounds, and what they kept asking support to do for them. one question guided the rest: how do we reduce friction without removing intent?

↖︎↑ a workaround tells you what someone needs. design for that.
( 03 ) Two kinds of progress

admins and participants want different things from the same platform.

the old flow treated everyone the same. i designed it to infer who you are from where you came in and what you do, so nobody has to self-identify or get stopped at a gate. onboarding asks for just enough to move forward, then steps aside.

participants: find a community worth their time and see their own progress( 01 )
admins: set up quests quickly and track engagement without relearning the dashboard( 02 )
( 04 ) Structure

built around what people are trying to do right now.

the old structure mirrored how tribe thought about the product internally. people moved through it differently. i rebuilt it around two questions: what are they trying to do, and what do they need next? scattered management tools became one dashboard. templates moved into the workflows instead of a tab nobody opened. i tightened the visual hierarchy at every decision point.

( 05 ) Cuts

we couldn't ship everything at once.

i sorted every feature into essential, needs refinement, or deferred. some were cut entirely because the complexity outweighed the value. fewer things done well beat everything half-finished.

what we cut
what we cut
( 06 ) What changed

internal teams said it finally felt like stackup.

navigation made sense. admins could see engagement they'd never had visibility into. bottlenecks that had been there since launch were gone, and the foundation could scale, which the original was never built to do.

( 07 ) Beyond onboard

the patterns went further than onboard.

i replaced inconsistent ui elements with standard patterns aligned to stackup's updated brand guidelines, some adapted from other products and some built from scratch to fill gaps. onboard's components now power events and other tools without anyone redesigning from scratch. that felt like the bigger win.

Next track →
One hub, many communities