I’m assuming you're familiar with what a design generalist is; if not, feel free to check out my other blog on the subject.

There are two ways to upskill in a new vertical or domain: actively, by starting from the basics, or passively, by observing and learning from what others are doing. I’ve done both. While my primary skill is Product Design, my adjacent skills include Design Systems, Data-Driven Design, Frontend Code, and Product Management.

My first exposure to coding came from my brother, who was studying BCA while I was in seventh grade. I used to sit beside him and watch him code in C++ for his assignments. I didn’t understand much of the syntax or structure, but I could grasp the purpose behind each line of code. Although I didn’t gather a lot of technical knowledge back then, I often flipped through his books, even if I barely understood them. But my curiosity was sparked. Later, I went to a hostel, and that exposure to coding diminished.

I went on to pursue a degree in Computer Science and Engineering, driven by my passion for learning and a keen interest in various fields of engineering—be it physical, digital, or automotive. I began coding in C, C++, Java, Oracle PL/SQL, HTML, CSS, assembly language, and .NET, among others. However, my primary interest always gravitated toward web development. I even attended an upskilling course on web design to gain a stronger foothold in the subject. Until my graduation, I didn’t realize that web design and web development were distinct fields. My first stint at Wipro brought that reality to the forefront.

During my college years, I actively worked on projects such as redesigning the college website, developing websites for annual fests, building a canteen attendance solution, and working on freelance projects like DiscountPlanet, an aggregator for discounts and coupons from offline and online stores. These experiences helped me understand the value of merging design with functionality.

Fast forward to 2022, I began using data to gain insights into user behaviors, actions, and events. At Wipro, I worked on various aspects of data—database management, data migration, data analysis, and data visualization. Although my time with each of these roles was brief, I gained a significant understanding of how to handle data for various purposes. My past skills enabled me to collaborate effectively with Product Analysts and Product Managers to create data-driven designs. One such project was the FedMobile Home Screen revamp, catering to a user base of 5 million MAUs. Incorporating features like LRUs (Last Recently Used), quick links for customization, and prioritizing widely used modules, data guided my design decisions. It helped me craft solutions for existing users while also experimenting with new features and discovery methods.

As a designer, I’ve worked closely with 5-7 Product Managers (PMs) depending on the product and project. Initially, I was a passive observer, learning the process and questioning the reasoning behind certain decisions for clarity. Over time, I began actively participating in product roadmaps, providing valuable insights into which modules to prioritize to help grow revenue, enhance user experience, and improve customer retention.

The role of a Product Manager is multifaceted—from setting product strategies, defining the scope of features, and collaborating with marketing and sales teams to tracking metrics, working with tech and QA teams, overseeing releases, and much more. While it’s impossible to learn everything, I made it a point to collaborate with PMs whenever possible to gain insights into their processes. Being closely involved in the product management process allowed me to fill in for PMs when they were on leave or occupied. Assuming a PM takes 3-4 weeks of leave a year, I was able to step into their shoes during those periods, effectively gaining 15-20 weeks of hands-on product management experience annually—without hindering my design responsibilities. This exposure significantly broadened my skillset in product management.

In 2024, I decided to revisit the basics of coding with a renewed focus—this time with the goal of becoming a true design generalist. I started actively learning again, diving into HTML, CSS, Tailwind CSS, JavaScript, and React. Rather than just reading through documentation, I spent time converting my designs into functional code, following best practices to ensure quality. This process has not only strengthened my collaboration with tech teams but also enhanced my ability to create seamless handoffs, write documentation, and provide code snippets.

Becoming a design generalist isn’t something that can or should happen overnight. It’s a journey that unfolds naturally over time. Rushing it might cause you to lose touch with the core skills that make you an expert in your primary field. However, expanding into adjacent skills—whether it’s coding, data-driven design, or product management—leads to better collaboration, more efficient workflows, and a wider breadth of knowledge.

In the age of AI, specialization will always have its place, but for designers like me, becoming a generalist feels like the way forward. It allows me to navigate complex, multi-disciplinary projects while staying adaptable and informed. And while I believe this approach works best for me, it’s important to acknowledge that it might not be the right path for everyone. But for those who enjoy learning across fields, I can confidently say it’s been a rewarding journey.