9 things I wish I’d known when I started building design systems
When I transitioned from freelancing to a large enterprise, my experience was limited to style guides and design standards. It was a shock to learn that I couldn’t simply tweak a button on a whim. Soon, I discovered the atomic approach to building design systems, and eventually, I created a system that unified 15 different products under one umbrella. Back then, I really wished someone had shared a few tips to make the journey easier…
Here, I share what I wish I’d known from the start.
A design system is more than just guidelines
Many designers start out thinking a design system is just a set of rules and guidelines. But a true design system encompasses much more: components, UX patterns, interaction principles, and workflows. It becomes a tool for the entire team, helping to streamline product development, standardize processes, and focus on real problems instead of repeated details.
When you create a design system, you bring digital life into existence
Building a design system is like creating a living digital organism. It will go through growth spurts, face crises, and evolve over time. You’ll need to maintain, adapt, and develop it, preparing for challenges along the way. But with each obstacle overcome, the system will become stronger, and you’ll gain invaluable experience.
Incorporate inclusivity and accessibility from the start
Inclusivity and accessibility aren’t just trends; they are fundamental aspects of a modern design system. Considering the needs of people with disabilities should be part of the initial design process, not an afterthought. An inclusive system can significantly broaden your product’s reach and show your commitment to a diverse user base.
Less is more
A successful design system prioritizes simplicity and clarity. Instead of creating numerous similar components, focus on building a few versatile, adaptable ones. This approach not only keeps the system lean but also enhances usability and minimizes redundancy.
A design system grows with the company
As your organization scales, so will your design system. It’s essential to plan for this growth by regularly assessing the system’s components, updating documentation, and ensuring that the system’s structure and tools align with the company’s evolving needs. Flexibility and adaptability will be key as the company and its products expand.
Test in real-world scenarios, not just in isolation
Testing components in isolation doesn’t reveal how they will interact within the larger product ecosystem. Real-world testing is essential to uncover unexpected issues and understand how elements behave in various contexts. This approach will help you design components that perform well in diverse scenarios.
A design system is about people, not just components
At the heart of any design system are the people who use it. Your system should make life easier for designers, developers, and other stakeholders by addressing their needs and streamlining collaboration. Engage with the team, gather feedback, and be ready to make adjustments to improve user adoption and satisfaction.
Document with examples, not just text
Clear documentation is essential, but plain text can be limiting. Including examples, illustrations, and use cases helps make guidelines more understandable and actionable. Show how each component should be used in different scenarios—this will improve consistency and make your system easier to adopt.
Avoid overcomplicating components with too many features
It’s tempting to create complex, multifunctional components that cover multiple scenarios, but this can lead to bloated designs that are difficult to maintain. Focus on creating focused, purpose-built components, and keep them flexible. This will make the system easier to manage and update in the long term.
Conclusion
Building a design system is a journey that spans the life of both the product and the company. The system requires care, flexibility, and an understanding of its value to everyone involved in the process. By following these tips, you can create a system that benefits not only your team but also the end users of your product.

Each stage of work on the design system is a step toward creating a more efficient and higher-quality product, and these insights will help you navigate this journey with fewer setbacks and greater achievements.
Back to main page
Blockchain and AI-Enhanced Health Portal
Blockchain and AI-Enhanced Health PortalAs a part of #HerHack we organized a team consist of 5 random people with different experience and build harmonised atmosphere in the team where everyone can full-fill their potential.
Case study: Integrated Crypto Transactions and Crypto Transactions Verification flow
In today’s digital banking landscape, crypto transactions are a core feature that users expect to be both smooth and intuitive. However, due to compliance requirements and regulatory checks, this process naturally involves multiple steps, which can feel complex without clear guidance.
Case Study: User-Focused Onboarding Platform for Legal Entities in a Crypto Bank
Imagine you are a manager of a legal entity looking to open an account at a new bank. Ahead of you lies a daunting array of documents, confusing terms, and legal nuances. This process can turn into a real challenge...
Crafting a Secure Identity for Swiss Safe
Swiss Safe is a company that focuses on digital solutions for the security and reliable storage of data and valuables. My role was to lead the art direction for this project and create a powerful, memorable brand that reflects the company’s core values: reliability, security, and innovation.
Multi-product Unified Design System
AD & EA Accessible, desktop and mobile-friendly global design system based on Material Design.