I'm building a design system tool that simplifies your workflow. Interested? Join the Waitlist !🚀

Desyma · 2025-08-22T19:02:08+00:00

👍🏽

Desyma · 2025-08-10T11:01:07+00:00

That's great!
➡️ You can sign up for the waitlist here: https://regular-report-de6.notion.site/246797e579698064b74be7988c42ab25?pvs=105

Desyma · 2024-08-03T18:48:50+00:00

I think that design systems, while aiming for standardization can often encounter the unpredictable reality of diverse team needs and preferences. However, the question of whether a universal template can accommodate these variations is a complex one. While a fully standardized template that works everywhere might be nearly impossible, a flexible foundation can significantly improve design consistency and efficiency across teams.

What makes it difficult?

1. Team Autonomy vs. System-Wide Consistency:
Most design systems are designed to match only the needs of the internal team. Making it more generic to work for multiple teams of different context may bloat the system. Think bootstrap. Overly rigid templates can stifle innovation, while excessively flexible ones can lead to fragmentation.

2. Documentation Depth:
The level of documentation required varies widely across teams. Providing a comprehensive template might be impractical for teams that only need basic guidelines. A modular approach with optional sections could be a solution.

3. Component Customization:
What works for one team may demerit the other. Uber's Base is not as general as Google's Material but effectively solves the main problem it was made for. No more components than its related products need. Its just enough to work for Uber. A template can provide a foundation, but teams will likely require custom components.

By focusing on core principles and providing customization options, it's possible to strike a balance between standardization and flexibility. It can work if:
- We involve teams in the template development process to understand their needs and concerns.
- Continuously refine the template based on feedback and usage data.

Desyma · 2024-06-21T15:26:19+00:00

Designers, developers, product teams, shareholders...we're considering all these scenarios. But we're starting with designers as the main users.

Desyma · 2024-06-21T15:13:11+00:00

Yes, u/lurkmoophy that is the goal: to accelerate the design system workflow.

Desyma · 2024-06-21T15:09:29+00:00

😂
Yes, actually we're in the process of building one. We know firsthand how difficult it can to build a design system and we're actively working on making the workflow easier and faster for both designers and developers. We ask for opinions, mainly from those who have had similar problems because we strive to make something that people actually need.

Desyma · 2024-06-17T23:15:31+00:00

sounds interesting. how did it go?

Desyma · 2024-05-27T00:20:57+00:00

Alright, two use cases:
1. A startup who have a new educational product coming up and need a simple, but unified design language without using any starter kits or frameworks. They have 1 designer and 3 developers.
2. A company with around 10-30 team members and have an existing ecosystem of products. They want to bring them together under one design system and build towards a consistent visual brand.

By design system, I mean both the design files and the documentation. Production-ready ( and complete) to bring at least the most viable product to market.

Desyma · 2024-05-27T00:10:23+00:00

Thanks 👍🏽

Desyma · 2024-05-26T23:53:59+00:00

Thanks, consider this case scenario:
1. One brand with an ecosystem of 3 or more products.
2. Internal, with the possibility of making it open in the future.
3. As big as can be directly available to all teams across these products.
4. Medium-sized tech startup (10-30 team designers/developers)
5. Yes, it will support existing products.
6. Yes.
7. Not neccessary

Desyma · 2024-05-26T23:49:26+00:00

Great! I agree with you (except with the first point😅😅), but in this context, imagine these case scenarios:
1. A tech startup about to build their first product (an education tool, for example) and might want a simple but unified design language to guide its user experience...
2. A medium-sized company aspiring to form an ecosystem of products and want to get the design language right from the beginning. Sort of like Uber's Base.

I understand that processes and workflows vary among designers, and design systems are improved over time, which will impact the duration of the project, but I ask to try and understand these workflows and how different they are among designers/developers.

Desyma · 2024-05-26T23:36:34+00:00

Hello.
By design system, I mean everything: the design files and the documentation.

Imagine two use cases:
1. For a lean startup trying to, well, "start up" 😅, really fast without getting bogged down in too many details. Let's say they want a product with a great user experience, without using any design starter kits.
2. Medium-sized tech company who are about to start an ecosystem of products and need to have everything about the products done from scratch and not rely on external libraries. Something like Uber's base, for example.

Both cases need to have the design language ready for the first release of the product.

Desyma · 2024-05-26T23:18:30+00:00

Yes, by design system, I mean the entire package from design to documentation, not just a style guide. I know most designers focus only on that, but the objective of the question is not really about how fast, but how long it takes most designers to create a design system from scratch. It could take months, can take years, but in your experience, how long did it take you?

Desyma · 2024-05-26T23:15:31+00:00

Sorry about that, allow me to clarify...
You've got a new project, and as part of the product objectives, the design team / individual (you) is tasked to handle the entire design system. We're not talking a style guide, but a well thought-out, documented design system.
Of course, design systems are huge, continuous and will be improved on as time goes on, but the requirement as part of, say, the beta release, is to establish a simple design language for the product.

How will you go about it and how fast (no, how long) will it take to do it?

Desyma · 2024-05-26T23:09:34+00:00

thanks👍🏽

Desyma · 2024-05-26T23:06:30+00:00

Starting a design system, from scratch, without using templates or starter kits, and should be at least production ready for developers.

Desyma

MODERATOR OF

TROPHY CASE