Design System Development:
Establishing Consistency and Scalability in Design
Creating a strong design system is crucial for maintaining consistency and scalability in the products and services we develop. A well-crafted design system ensures a cohesive user experience across different platforms and streamlines the workflow for designers and developers.
While collaborating with the Design Ops team at Centene, I reviewed hundreds of design files from various teams and led solutions for naming and organizing design files and asset libraries within the design system.
CNC-UX/UI-01
Molecular-level UI components move from the company's shared asset library to various product App Component libraries, where they are then used in feature-specific design files.
CNC-UX/UI-02
In this example, there are two types of Figmas: design files and shared libraries. We create design files for any new design or iteration using a starter file. Shared libraries include the company's UI component library, the design kit, and the app component libraries of various products.
CNC-UX/UI-03
Here is a flowchart showing the atomic distribution of components with different nomenclatures between company, product, and project files. Atoms, molecules, and certain organisms are created and maintained inside the company's component library. In contrast, product-specific organisms, templates, and pages (or views) are created and maintained inside each product's app component library.
CNC-UX/UI-04
Here is a bird's-eye view of an organization's design system, which includes internal and customer-facing web applications, a network of nationwide public sites representing three different brands, and five unique customer segments.
