![]() This was where I would make adjustments based on the feedback I received, and create every needed component variation e.g. Next came the “ Finalize Specs □” column. The whole design team would review the work I presented, make critiques, and provide suggestions. The ticket would then move to the “ Sparring □” column, which was a fun way to say design review. Initial research, accessibility checks using WCAG, Apple’s HIG, and Material Design, and mocks would be conducted and created. Once a new component or feature was prioritized in a biweekly backlog grooming session, it was moved into the “ Exploring □” column. When a ticket was first created, it sat in the “ Backlog” column. The Kanban board I created at EagleView “Successful design patterns don’t exist in a vacuum.” – Yesenia Perez-Cruz, Sr. Let me save you a few hundred hours - designing design system components in a box with no context is a waste of time don’t do that. Frontend Developer PGS Software Design with context “Using a Design System can remove over 50% of the time needed to design, develop and test, in addition to ensuring consistency and giving your team more time to focus on what’s important: quality and innovation.” – Marcin Fuja, Sr. And You Thought Buttons Were Easy | Nathan Curtis.How To Save 35 Hours Using A Design System | Marcin Fuja.The last two metrics are a bit ambiguous and I suggest you check out these two articles if you are looking to get more granular with your KPIs: At EagleView, we collectively wanted to: increase our sprint velocity by ≥50%, free up as many design hours as possible, and increase collaboration productivity by creating a shared language between design, engineering, and product. There are several ways to measure the success of a design system. I approached my research with an open mind, soaking up as much of the knowledge as I could like a sponge. Building (And Re-Building) the Airbnb Design System | Maja Wichrowska & Tae Kim.How to Design a Dark Theme Using Material (Google I/O’19).Design Systems, when and how much? - Diana Mounter.Material Theming: Build Expressively with Material Components (Google I/O’19).Reimagining Design Systems at Spotify - Shaun Bent - Design Systems London 2019.The Future of Design Systems | Hayley Hughes | Airbnb | Awwwards Conf San Fran.The following videos were (and still are) extremely helpful to me: So, I typed “design systems” in the search bar and clicked on the first video that looked interesting. YouTube seemed like a good place to start. I realized that there were many things about design systems that I simply did not know, but how to remedy my predicament was unclear. My initiation into the design systems’ world was kind of like that, but in the dark, blindfolded, and with a lot of sharks (ok maybe not the sharks part). Throw me into the deep end of a pool and I’ll usually swim. I learn best through hands-on problem-solving. Sounds easy right? I didn’t know where to start. To make things more challenging (depending on how you look at the situation), I was given only one requirement, the Design System needed to be built in React. native and web) and applications, resulting in jarring and confusing experiencesĪ few of EagleView’s products before the Design System Customers (users) were experiencing a lack of cohesion across platforms (e.g.Designers were spending countless hours crafting one-off UIs for new products.Engineering sprints were bogged down by the development of the same components over and over again ( How many times do we need to create a button?).Onboarding designers to multiple UI libraries and engineers to multiple codebases was tedious and prone to redundancies. ![]() The leadership, design, and engineering teams had come to a consensus that they needed a design system from identifying the following problems (most of which are more common than we would like to admit): On top of that, they had multiple products in various stages of flight and on different platforms (native and web). They had a large portfolio of digital products (~20) and each looked vastly different. Once upon a timeĮagleView gave me my first shot at design systems. I hope that you find my experiences useful wherever you might be on your path in design. The following is a brief account of my journey and career in design systems. But, like many designers working on their first design system, I underestimated the feat of the task at hand. In the beginning, this concept was curiously intriguing to me. I’ve always loved the idea of approaching design systematically, with global styles, rules, and guidelines. Previously I worked at EagleView and helped design their first design system. Currently work at Microsoft on the Fluent Design System and Teams Component Library.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |