Nowadays, we’re demanding more from design systems than ever before. As design systems become more commonplace and standard, their problem set expands. The ol’ PDF style guide won’t cut it anymore. Design systems need to be flexible, accessible, customizable, available in different languages, successful across different platforms, and able to fold our socks.
The definition of a design system is changing. The idea of one brand = one design system, this-is-all-you-need set of components and rules, is being pushed aside for something far more flexible and far more integrated. There are several reasons why this is happening.
TL;DR The secret to getting a team to create design principles they understand and care about is to connect them back to individuals’ values, things everyone can relate to.
A Google search of “design principles” results in many beautiful examples of tenets forged within the hiveminds of today’s design-driven tech companies. They’re succinct. They’re powerful. They’re “carve-into-marble” worthy.
I’m assuming if you’re reading this article that you have read another preachy explainer on design principles before, but for the sake of comprehensiveness, a quick refresher. Design principles are a set of statements that offer a point-of-view on best practices. …
Product designer @ New York Public Radio. I get excited about design for social good and ethics in technology.