Every component library gets “discovered.” As the first stage of the library development process, discovery activities identify component candidates and enable a unified vision of what’s essential, what’s nice to have, and what can be thrown out before you even begin building any assets.

Once a library is discovered, information architects can collaborate with other disciplines to organize the library, build out relevant assets, document the taxonomy and guidelines on usage, and ultimately publish and promote adoption of the library when it’s ready for prime time.

Such discovery can emerge from a range of activities, which include:

• During Design: Creating a component-based design solution can lead to numerous efficiencies during the design process. That said, it is very difficult to realize a formalized, long-term component library during rapid design cycles that push towards implementation. The library discover process includes an evolution of the components themselves as well as the classification model that organizes them. Such efforts can derail a project’s process and focus, or simply be abandoned as deadlines approach.
• Analyzing a Design System: A designer familiar with a design system approach and component strategy can independently assess that design system to recommend a component library. Beginning with independent research of a production system based on scope defined by the organization, the designer can apply their own knowledge along with best practices to identify reusable components in context.
• Workshop Exercises: Nothing beats the energy of getting a team together to mutually decompose an existing design system and arrive at a component library together. From information architects to visual designers, from coding technologists to site strategists, from ux leads to directors, the more you involve, the easier you gain consensus and create a baseline for adoption and practice over time. Eightshapes has facilitated numerous component discovery exercises for teams large and small; at a high level, teams slice up screenshots with scissors, organize the multitude of variations, and work on grouping, labeling, prioritizing, and archiving the results. All the while, individuals work together to discuss assumptions and clarify component roles and approaches with EightShapes experts.
• Code Architecture: Often, a component library may be derived from an implemented code base, content management system, or other technical architecture. While there may be incongruities with the preferred modularity of the user experience, there are numerous advantages to adopting a technical baseline as the foundation for the library, including shared nomenclature and implicit buy-in from the technical team(s).