Developing, maintaining and promoting the Design system of Flixbus. The design system is intended to bring consistency and Brand aligned UI and UX across all user touchpoints of the Flix brand.
User Research, UI Design
2 UX Designers, 1 Front-end Developer, 1 Agile Coach
+
Contributors
Flixbus, Flixtech dev teams
7-8 Months
Figma, Zeplin, Adobe CS Suite, Userzoom test platform
Flix Mobility, the internal tech wing of Flixbus was facing challenges to bring consistency in visual and user experience among their internal and client-facing products. To create a single source of truth in these areas the Honeycomb design system was designed and developed. A small team was responsible to oversee the development and maintenance of the design system by utilizing the existing designers and developers in the other product teams in Flix Mobility.
The challenge of this design system team was three-fold:
Creating components to enrich the design system library and keeping up with the constantly changing standard of interface elements by releasing updated design system components
Encouraging the product teams through promotional activities to adopt and use the design systems in their products and also contribute to the library
Helping product teams to solve design problems with Design system library components and following recommended guidelines
Approach
Understanding use contexts of time picker component within Flixbus mobile application, website, and Flixcar mobile application.
Benchmarking other transportation service providers like Blablabus, Omio, DB, Regio, Greyhound, Emirates airlines, etc
Benchmarking other design systems like google material, IBM Carbon, Apple HIG, Semantic UI, Shopify Polaris, etc.
Designing different approaches for time picking options like Dropdown, time dial, Tabs, Slider, and keyboard input.
Creating 12hr and 24hr varients of the approaches to test in different parts of the world
Remote testing the approaches with users from USA and Germany in the 16-65 y/o user demographic
Selecting best performing solution and design
Creating Usage and use case guidelines.
We have taken multiple different steps to promote the design system, increase adoption and encourage contribution:
Creating Design system user Personas
Publishing regular promotional materials & contribution credits
Giving visibility of the upcoming features with roadmaps
Conducting Design System onboarding sessions
Regular feedback and idea-sharing sessions
Facilitating on-site design Jams
Setting KPIs of Design system use, measuring, and publishing the numbers
Approach & Process
To understand the user need of the Design system users (aka Flixbus Tech product teams) we have decided to create personas. Our subsequent activities would be performed to address the need of these personas. To create the personas, we have followed:
Survey and Interviewing UX designers, Product Owners, Front-end and full-stack developers in the organization
Understanding perception about the design system from the survey.
Extracting needs, challenges, inspirations, goals from the interviews
Defined 3 High-level persona types based on mental model and behavior
Collected assumptive data based on firsthand experience of interacting with these persona types
Grouping similar attributes together through generalization and extremes and forming the ideal persona from those attributes.
Validated the assumptions and generalizations through 2nd phase of interviews.
Distilled and rephrased the information for easy relatability
Created infographics for instant understandability for each persona type.
To spark interest about the design system among the organization, we have decided to create catchy posters and also create contribution credit write-ups to encourage the contributing designers, POs, and developers to the design system.
We were also doing monthly Design system onboarding sessions for all new joiners in Flixtech.
To encourage adoption and to demonstrate how to effectively use the design system to solve design challenges among different product teams, I have worked with the product teams to design interfaces following the guidelines and using the components in the design system library. After designing I also had sessions with the developers about how the components have been used in the interface and what things are needed to keep into consideration while developing.
We have set KPIs for the adoption and use of the design system among the products in Flixbus. Data for KPI measurement were gathered by communicating with the developers and Product Owners, searching in the codes, or putting usage data collection scripts.
KPIs were measured for:
Number of new components requested in the quarter
Number of new adoption of the design system in products
Number of contributions per release
Number of participants in sprint planning
Amount of use of design system components in products
As the adoption of the design system increased, the internal and client-facing Flixbus products started to look brand-aligned more consistently. The Tech leadership was also considering making the design system mandatory to use in all product teams. Creating new brand themes for Flixbus’s new prominent acquisitions was more manageable and also without deviating from Flixbus’ core brand identity.
The design system can be found in the following link
https://styleguide.hive.flix.tech/