Merge pull request #206 from varya/posts/career-path

feat: [post] A Holistic Career Path and Challenges with Design Systems

content/posts/design-systems-career-path/index.md

@@ -0,0 +1,46 @@
+---
+title: A Holistic Career Path and Challenges with Design Systems
+
+date: 2024-08-28
+cover: varya-projects.jpg
+
+meta:
+  desc: >
+    Explore the multifaceted world of design systems through the eyes of a seasoned architect. This comprehensive guide covers key challenges, best practices, and career insights in design systems, from component development to stakeholder management. Learn how to navigate the evolving landscape of design systems, measure impact, and foster collaboration between designers and developers. Perfect for both newcomers and experienced professionals looking to enhance their skills in this dynamic field.
+---
+
+<div data-excerpt>
+
+Recently, a mentee asked me to describe the variety of challenges I faced as a design system architect, or basicaly "**what exactly do you do?**". It's a question I often hear, and it always takes me back to my own journey. As someone who started as a frontend developer and evolved into a design systems architect, I can say that the path is rarely linear—it's more of a holistic evolution, encompassing a wide range of responsibilities and skills.
+
+</div>
+
+![](./varya-hands.jpg)
+
+My 20-year career in frontend engineering always gravitated towards component-driven development. Even before the term "design systems" became ubiquitous, I was fascinated by the concept of reusable, modular code. This focus naturally led me to explore design systems more deeply and encounter an array of challenges and opportunities that have shaped my career.
+
+One of the most common misconceptions I encounter is that design systems are a one-time project. In reality, they're an ongoing process that requires constant attention and evolution. This was particularly evident in [my recent work with METRO](/projects/metro-design-system/), where I served as a product owner and project manager for their design system. The library of components was all-set, but the work didn't stop there. We continually defined workflows, conducted regular onboarding sessions, and even developed security policies.
+
+Collaboration stands as the cornerstone of success in design systems. At METRO, [I organized regular onboarding sessions](/projects/metro-design-system/), which became recognized recurring events on the company calendar. These sessions not only informed newcomers about our design system but also facilitated their integration into our workflow and promoted wide adoption within product codebases. Furthermore, the consistent presence of a design system team in both design and development in-house forums, made the design system much more recognizable and appreciated.
+
+Quantifying impact emerges as another critical aspect of design systems work is measuring impact. In a recent presentation at the Into Design Systems Conference in 2021, [I focused on translating design system value into tangible business benefits](https://www.youtube.com/watch?v=OaqBxIp15hg). It's imperative to establish metrics that demonstrate how much a company can save or earn with a design system. However, it's equally important to be realistic in your promises—overpromising can damage credibility.
+
+Balancing consistency with creativity presents another formidable challenge in design systems. In my recent [work with Bridge-the-Gap team on a project for AppOmni](https://bridge-the-gap.dev/case-studies/appomni), we tackled this by making the components fully customizable via CSS variables. The details of this approach are covered in the article [Web Components in Action — How to Build a Design System](https://bridge-the-gap.dev/blog/web-components-in-action) recently published on [Bridge the Gap](https://bridge-the-gap.dev/). This approach allows developers to easily modify the look and feel of the components without altering the core components' code.
+
+Another significant challenge is keeping up with technological advancements. For Yara, [we upgraded their React and React Native libraries to Storybook@7](https://bridge-the-gap.dev/case-studies/yara). With later projects, we also continued working with the newest Storybook versions, sometimes investing into upgrade. This refactoring may require changes in almost all stories and updating dependencies, but it ultimately improves the UI's customization capabilities based on user research insights. My colleague Irina recently ellaborated on that aspect when speking at Into Design Systems 2024, and [we published and extract of these insights on LinkedIn](https://www.linkedin.com/feed/update/urn:li:activity:7206208034535022593/).
+
+I always emphasize the importance of understanding both the technical and design aspects. My background in frontend development has been invaluable, but I've also had to study design principles to create truly effective systems. Equally important are skills in facilitation and stakeholder management. At F-Secure, where I helped develop a design system strategy](/projects/f-secure-ds-strategy/), my focus was on creating alignment among different stakeholders, establishing a clear vision, and drawing a practical roadmap with clear milestones. This multidisciplinary approach is crucial in bridging the gap between designers and developers. In my experience, one of the biggest challenges in implementing design systems is achieving buy-in from all levels of an organization.
+
+To share knowledge and foster community in the design systems field, I regularly speak at conferences, conduct workshops, and write blog articles. In my and Irina's recent talk "From Survival to Growth: Enhancing Design Systems via Seamless Collaboration", we explored ways to improve collaboration and communication within design systems teams. This presentation highlighted the importance of both horizontal collaboration between designers and developers, and vertical collaboration with stakeholders.
+
+I've also given talks on "Data-Driven Design System Management" in pair with my client manager Daniel, discussing how to use metrics and analytics to guide design system decisions and demonstrate value. In "The complete design system: what and how we could learn from the others", I examined best practices from various design systems to create a more comprehensive approach.
+
+My blog and the articles I publish on Bridge-the-Gap website feature information on practical aspects of design systems, such as "[Define your Rock-Solid Design System Components](https://bridge-the-gap.dev/blog/design-system-define-components)" which provides a detailed guide on component definition and documentation. Another article, "[Web Components in Action — How to Build a Design System](https://bridge-the-gap.dev/blog/web-components-in-action)", explores the use of Web Components in creating scalable and consistent design systems.
+
+These talks and articles aim to provide both high-level strategic insights and hands-on practical advice for design systems practitioners at all levels. By sharing experiences and fostering discussion, I hope to contribute to the ongoing evolution and improvement of design systems practices across the industry.
+
+Looking ahead, I'm excited about the potential for even tighter collaboration between designers and developers. The industry is moving away from the "design agency" model where designers work in isolation, towards a more integrated approach. This shift, facilitated by design systems, is resulting in products that more closely match their original designs.
+
+For those considering a career in design systems, my advice is to cultivate a holistic understanding of product development. Whether you're coming from a design or development background, be prepared to stretch your skills and perspectives. The field offers unique opportunities to bridge disciplines, drive consistency and efficiency, and significantly impact product quality and user experience.
+
+In conclusion, a career in design systems is both challenging and rewarding. It requires continuous learning, adaptability, and a passion for creating cohesive, user-friendly products. As the field continues to evolve, there will be endless opportunities to innovate and make a real difference in how digital products are created and used.