Shipping features 40% faster by creating a design system
Shipping features 40% faster by creating a design system
Shipping features 40% faster by creating a design system
Josh Talks ✻ Design System
Josh Talks ✻ Design System
Josh Talks ✻ Design System
Problems 😓
The existing process resulted in extended timelines for shipping and handoff, causing delays in implementing and delivering features.
Due to inconsistent experiences across the app, users were more likely to abandon the application, resulting in a higher drop-off rate.
Process ⏩
Based on these problems, we realised the need for a design system, that could help us achieve - Consistency, Speed and improved collaboration between teams.
We followed the approach to start small and then iterate. Started with the basics, defining colours, typography, and some basic components like buttons and form fields.
We started with identifying the reusable patterns that we were currently using, and followed the Atomic design approach to break down interfaces into their smallest parts (atoms), then combine these atoms into larger, reusable components (molecules and organisms).
Goals 🎯
Establishing a design system using Atomic Design Principles that can easily scale as the app evolves.
Accelerating the shipping of features, enabling the team to conduct multiple experiments concurrently.
Bringing consistency in design elements, interactions, and flows across the entire app.
Results 🥳
With the creation of a design library, the time to design flows and screens reduced by ~ 40%
With components defined in one centralised location, developers can easily access them, resulting in a smoother handoff process.
Enhanced user experience, reducing drop-off rates, and providing users with easier navigation throughout the app.
Problems 😓
The existing process resulted in extended timelines for shipping and handoff, causing delays in implementing and delivering features.
Due to inconsistent experiences across the app, users were more likely to abandon the application, resulting in a higher drop-off rate.
Process ⏩
Based on these problems, we realised the need for a design system, that could help us achieve - Consistency, Speed and improved collaboration between teams.
We followed the approach to start small and then iterate. Started with the basics, defining colours, typography, and some basic components like buttons and form fields.
We started with identifying the reusable patterns that we were currently using, and followed the Atomic design approach to break down interfaces into their smallest parts (atoms), then combine these atoms into larger, reusable components (molecules and organisms).
Goals 🎯
Establishing a design system using Atomic Design Principles that can easily scale as the app evolves.
Accelerating the shipping of features, enabling the team to conduct multiple experiments concurrently.
Bringing consistency in design elements, interactions, and flows across the entire app.
Results 🥳
With the creation of a design library, the time to design flows and screens reduced by ~ 40%
With components defined in one centralised location, developers can easily access them, resulting in a smoother handoff process.
Enhanced user experience, reducing drop-off rates, and providing users with easier navigation throughout the app.
Problems 😓
The existing process resulted in extended timelines for shipping and handoff, causing delays in implementing and delivering features.
Due to inconsistent experiences across the app, users were more likely to abandon the application, resulting in a higher drop-off rate.
Process ⏩
Based on these problems, we realised the need for a design system, that could help us achieve - Consistency, Speed and improved collaboration between teams.
We followed the approach to start small and then iterate. Started with the basics, defining colours, typography, and some basic components like buttons and form fields.
We started with identifying the reusable patterns that we were currently using, and followed the Atomic design approach to break down interfaces into their smallest parts (atoms), then combine these atoms into larger, reusable components (molecules and organisms).
Goals 🎯
Establishing a design system using Atomic Design Principles that can easily scale as the app evolves.
Accelerating the shipping of features, enabling the team to conduct multiple experiments concurrently.
Bringing consistency in design elements, interactions, and flows across the entire app.
Results 🥳
With the creation of a design library, the time to design flows and screens reduced by ~ 40%
With components defined in one centralised location, developers can easily access them, resulting in a smoother handoff process.
Enhanced user experience, reducing drop-off rates, and providing users with easier navigation throughout the app.
