All work

Studytube

A skill-based learning platform for teams. I rebuilt its design system from the ground up and helped redesign onboarding so more new users reach their first lesson.

Role
Design System Owner and Product Designer
Team
4 product designers and a UX researcher
Platform
B2B SaaS web: LMS, LXP and authoring
43% → 59%first-lesson conversion
+37%relative growth in activation
1 systemacross LMS, LXP and authoring
4product designers and a UX researcher

Studytube helps organisations develop the skills their teams need through personalised learning, structured content and data-driven development. Two problems stood in the way:

  • The design foundation was inconsistent, which slowed delivery for the multiple teams working across the platform.
  • A significant drop-off after registration: only 43% of new users reached their first lesson.

I joined an existing UI design team and took ownership of rebuilding Studytube’s design system from the ground up, while designing and improving selected product features and flows.

I worked in a cross-functional design group of four product designers and a UX researcher. I built the system’s foundations and core components; the other designers built pages, blocks and larger components on top of it.

  • Created and maintained the Studytube design system.
  • Defined foundations: colour tokens, typography and component patterns.
  • Rebuilt and improved core components and interaction states.
  • Established documentation and usage guidelines.
  • Supported adoption across multiple product teams, so LMS, LXP and authoring share one language.
  • Connected the design system to the coded library in Storybook, our first project with it. Every component change came as a pull request with a Chromatic visual diff, and design reviewed it before merge.

Hypothesis. We believed that if new users chose a goal first and got a personalised path, more of them would reach their first lesson. It held: first-lesson conversion grew from 43% to 59%.

Together we ran user interviews, analysed product behaviour and reviewed key funnel metrics. We mapped the onboarding journey, found the main friction points and designed a new flow that helps users understand the product and reach their first learning experience faster.

  1. RegistrationCreates the entry point.
  2. Goal selectionReveals learner intent.
  3. Personalised pathsConnect intent to content.
  4. First lessonDelivers the first value moment.

We also simplified the authoring flow so content teams can move from idea to publish with confidence: brief, content, knowledge check and publish, with a live preview of the lesson.

  • First-lesson conversion grew from 43% to 59%: +16 percentage points, about 37% relative growth.
  • One consistent design system adopted across multiple product teams.

How we measured: the design lead tracked the onboarding funnel in the product analytics and opened each daily with the numbers; designers had no direct access. Results reflect the work of the whole product team.

The work combined design-system ownership with product design, research and measurable activation improvements. studytube.com

  • Design system
  • Onboarding
  • Activation
  • B2B SaaS
  • Research

Agree on one source of truth with developers on day one. We first documented the design system in Zeroheight, then found that developers worked in Storybook. For a while we kept both, then dropped Zeroheight and moved everything to Storybook. Today I would ask developers where they already work before writing a single page of documentation, and start there.

Next caseSAPDesign system pilot: 5 input components from 3 libraries became one reference Input, with docs, versioning and Storybook.

Need someone to lead
your
design team?

I’m looking for a Head of Design role, remote from Spain. English, Ukrainian and Russian, intermediate Spanish.