Eventscase

Multibrand Design system

Multi-brand new design system adapted to the new branding.

Role
Senior Product Designer
Focus
Time to value
Team
3 product · 5 engineers
Stack
Figma · Posthog · Metabase
Eventscase design system colour tokensEventscase product built on the design system

Speed

Faster delivery across teams


Product

Reduced UI-related bugs


Consistency

Scalable multi-product

Context

Business Context

After the pandemic, the events industry shifted toward remote and hybrid events. The company decided to take this change as an opportunity to open up to a new market.

To be ready for this new market, we started by setting a solid foundation. The company invested in a rebranding to refresh its image and reflect this new era, and also decided to build a new product. To make this possible, it was necessary to create a new design system.

Problem Framing

The product needed to adapt to each client's brand while remaining scalable and under our control. At the same time, it was essential to maintain consistency with existing product functionality, ensuring continuity for current users.

The new system also had to work across multiple products, creating a shared and coherent experience between them.

Eventscase design system foundations and components

Goal & Hypothesis

Goal

A single design system supporting multiple brands and products, built to scale with control.

Design process

Audit

We conducted a full audit of all components across the different products. From this, we created a component sheet detailing all existing elements, identifying redundancies and opportunities for standardization. This phase gave us a clear picture of the existing ecosystem.

Plan

At this stage, goals, timelines, and priorities were defined to continue evolving the products while planning a gradual integration of the new design system. This allowed us to introduce changes without breaking existing functionality or disrupting current users.

Define

We defined the visual language of the system, including layout systems, spacing, grids, breakpoints, color palette, typography, and tone. We also established naming conventions for components and tokens, aligned with the development team. This created a solid base, ensured consistency, and built a shared language across teams.

Design

Work started with creating the tokens and redesigning the core components of the system. Close collaboration with developers from early stages helped build a solid design system and Storybook. Components and tokens were documented with clear usage guidelines.

Deliver

All tokens, components, and layouts were built in collaboration with the development team. Progress was tracked using a table inventory, and components and layouts were carefully integrated into the product, replacing old ones without breaking functionality.

Solution

One design system, built to support multiple brands across a new product, with documentation that made it possible for design and development to work independently.

Design system file organizationDesign system documentation pagesButton component and its variantsEventscase product home built on the system

Next project

Renta Revamp

Simplify and automate the renta process to help users save time and money.

If you're looking for a product designer — or just want tochat about ideas — feel free to drop me a message.

Always happy to connect.

Let's talk