Customizability, because on the way, you will need to improve your design with the user intent data.

For me, it’s all about flexibility. You want a system that can grow with your project and team. Something too rigid will feel like a straitjacket down the road. Also, good documentation is key – you don’t want to spend all your time deciphering how things work. A design system should make life easier, not harder!

For me, it’s all about flexibility. You want a system that can grow with your project and team. Something too rigid will feel like a straitjacket later on. Also, check if it fits well with your existing tools and workflow – no point in picking something that makes life harder! Lastly, good community support is a big plus.

For me, it’s all about flexibility. You want a system that can grow with your project and team. Something too rigid will feel like a straitjacket later on. Also, good documentation is key – you don’t want to be guessing how things work. Lastly, make sure it fits your brand and design philosophy, not the other way around!

A design system can be compact but must be consistent, based on simple principles, and customizable. It might have only 20 components, but we can easily scale it to 100 or more when new user scenarios require it in the future. In contrast, massive design systems with hundreds of pages of poorly organized documentation will inevitably lead to inefficiency and confusion over time.

For me, every project has its own set of challenges and a design system that's flexible can make a real difference

To my mind it is scalability and adaptability to support the product’s growth, evolving requirements, and consistency across teams and platforms