Duration

1 month (2024)

Tools

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

The challenge

Five products. One compounding problem. As StackUp's suite of apps grew, design decisions made in isolation started showing, with different button states here, inconsistent spacing there, components rebuilt from scratch because nobody knew the canonical version.

Context

We were already using Flowbite as our component library, but without a proper design system anchoring things, inconsistencies had crept in across every product. My job was to audit what existed, build a framework for prioritising what to fix, and leave behind something the team could actually use.

The solution

I audited components across 6 applications, built a scoring system to triage 100+ components by usage, complexity and business value, and created a modular documentation structure designers and developers could navigate independently.

Feedback

… “Through her meticulous approach, she uncovered a range of inconsistencies that had crept into our applications over time. Shantini's design system wasn’t merely a style guide; it became a foundational tool that brought clarity and cohesiveness across a suite of apps. Her work enabled our team to create a more unified experience, which greatly enhanced user satisfaction and streamlined our internal processes for future development.”

— Christopher, Head of Product from Tribe

In this case study

What I was solving for

Structure

Scope

Template

Foundation

Components

Goal

Three things needed to happen in parallel, and none of them could wait for the others:

1. Audit existing components to identify inconsistencies and gap

2. Defining how we wanted to showcase components and specs for future scalability

3. Creating a prioritisation framework to guide the team in refining and standardizing components

<aside> <img src="/icons/apple_lightgray.svg" alt="/icons/apple_lightgray.svg" width="40px" />

Why this matters

Without clear priorities, teams fix what's loudest rather than what's most impactful. A scoring system shifts that - where decisions become strategic, not reactive.

</aside>

Structure

Stats at a glance

• 5 products
• 8 explored experiences
• 7 foundational elements
• 100+ components/patterns

I pitched the team a modular structure before writing a single line of documentation. Modular meant teams could find what they needed without wading through everything else. Each section stood on its own.