![]() It’s difficult to define a set of rules that would put an end to these meetings in the future. What do you optimize for? Is it for consistency, scalability, creativity or maintainability? You can optimize for so many things - and choosing only one often sacrifices another. There are so many questions to be answered. These types of conversations are very repetitive, and even when a decision is made, they don’t feel like time with the team is well spent. “What should the configuration options look like?” I’ve noticed that a good chunk of team members’ productivity goes into endless conversations such as: “Should this be a separate component?” ![]() Things advance fast, and I try to keep up making it work for both designers and developers. Working as a designer on a design system for a large product has taught me how precious the time you spend on a single task/component is. In this article, Sasha explains why she finds the Systems Designer position so rewarding - and it’s not only because of how fast certain tools have developed to help her master challenges she faces in her work projects.Įditor’s Note: This article comes with a Figma-playground file, so feel free to jump in and explore the concept. Figma has advanced enough where it now supports some powerful concepts that can help with the flexibility and maintainability of a design system.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |