…to consistently address our needs for more complex patterns such as mapping or data visualizations. The constant need to modify and extend design patterns per application worked counter to the purpose of a design system and introduced inconsistency and wasted effort. Additionally, a design system that simply provided a “kit of parts” also left a lot open to interpretation. This resulted in questions and requests for additional design direction, something unmanageable even when designers aren’t outnumbered 4,000 to one. A more sustainable approach was needed.
The inclusion of design patterns created by multiple product teams not only helped fill out the design system hierarchy — but it has demonstrated how we can achieve our goals of sharing and reuse. Teams are now drawing upon design patterns which have been used in other products, and are eager to share and show off their designs to the rest of the community. Based upon the reactions in the months since the launch, the Predix community within GE is eager both to learn and share new design patterns.
… platform design team, as well as patterns contributed by teams building products on top of Predix. Launching with contributions from multiple teams allowed us to fill the entire hierarchy of the design system with content. The Platform team, as the stewards of the design system, provided most of the foundational design patterns for Principles, Basics, Components, and Templates. The product team on the other hand, provided design patterns from the more applied levels of the design system.