A design system For the scientific market

In a nutshell...


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


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


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,


- Consolidated the DS Portal with detailed
- 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 in a fast-pace, we delivered an initial group of 33 components and 6 patterns. Consolidating a solid workflow to review and develop
I defined a process where the team can share and review the different designs under development. And together with the development squad supported the consolidation of the implementation process


Together with the coded components we provided a detailed design library, and adaptation for quick drafting and a extensive documentation available 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


  • 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


  • 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