Description

Brink DS is the new design system for Frontiers platform, a digital scientific publisher. The system includes a code library, a design library and a quite extensive documentation through a Brink DS Portal

Purpose

Offer a seamless product design development to
promote experience consistency and effective implementation

Scope

All products part of Frontiers Platform

Role & Responsibilities

Product design manager: Build the strategy, Pitch the project, present results, Advocate for the project, Help the team to create their workflow and routines, Actively participate in the agile ceremonies,

Outcomes

- Consolidated the DS Portal with detailed
documentation
- Code library + Design library synced
- Support workflow and new features request protocol
- Early adoption started

Visit the Brink DS Portal

Releasing version 1.0

Working at a fast pace, we delivered an initial set of 33 components and 6 patterns, consolidating a solid workflow for review and development.

I established a process for the team to collaborate on and review designs in progress. Working alongside the development squad, I supported the streamlining of the implementation process.

Results

Along with the coded components, we provided a detailed design library, a quick drafting adaptation, and extensive documentation accessible through the Brink Portal (Zeroheight).

Distribution of assets and resources

We distributed all the resources by using 3 different tools: Figma, Zeroheight and Storybook. I worked to enable a strategy for this purpose. Promoting checkins of the sync states and reviews of the integrity of data/documentation displayed

Defining proper routines with engineers

I worked supporting the consolidation of the different interactions with devs, to ensure an effective unfolding process for the DS

Consolidating the collaboration

Brink DS is working as north star for the collaboration dynamic between designers, PMs, and developers a long the whole catalog of products

Impact

Presenting a clear case of an agile implementation with a scope for the whole organization
Demonstrated a strong collaboration between designers/developers as a possible workflow
Released an alpha in 3 months and estimated the MVP for 7 months
Quick pace for a maturity process

Takeaways

Define the specific product requests in terms of user needs
Tagging step for the early adoption process
The benefits of consolidating the project in people terms (Impact on teams)
Quick pace for a maturity process

A design system For the scientific market

In a nutshell...