This End-to-End UX research journey began by the Azure Client X team initially approached me seeking insights for their VSCode extensions SDK, aiming to enhance the VSCode Teams extension for pro Microsoft 365 developers. However, through a meticulous analysis leveraging the customer-driven engineering funnel, I uncovered compelling insights that challenged the narrow focus on pro users. It became evident that catering solely to this segment would restrict our market potential, considering they represent just ~6% of the entire potential user base. In response, I championed a shift in mindset towards embracing growth opportunities, advocating for a refined research goal centered on 'How might we expand the impact and reach of the VS Code extension for various types of Teams developers.'

As part of the continuous discovery research project for the Visual Studio team, I spearheaded a comprehensive two-week research initiative aimed at unraveling the ideal code searching experience within Visual Studio (VS) while contrasting it with the preferences of Rider IDE users. Embracing the Hypotheses Progression Framework (HPF) guidelines, I meticulously curated a diverse cohort, engaging Professional VS users, New-To-VS adopters, and dedicated Rider IDE enthusiasts. The research ended up with resonating with customers strong inclination of code ownership ('the search should NEVER block my code') and the wish to never have their natural workflow interrupted when performing such actions.

AI-assisted development continues to captivate attention within the realm of software development. For professional developer customers, establishing trust and fostering a sense of ownership in their development processes stand as pivotal factors. Interestingly, our research revealed a fascinating insight: when suggestions' appearance and functionality are meticulously crafted, these discerning customers exhibit a subtle willingness to explore bolder options, effectively learning through hands-on implementation. To begin the task of enhancing our understanding of key themes related to developers' interactions with AI, I initiated a culture of continuous discovery. This involved starting with the method of closely collaborating with product teams to conduct weekly evaluative research initiatives. Through these systematic efforts, we were able to uncover a wide range of intriguing topics and areas that had not been fully explored, presenting opportunities for innovation and improvement. Our research focused on examining developers' perceptions of code ownership, their sense of responsibility, the trust they place in AI, and the nuanced roles assigned to AI within their workflows. The end goal we achieved was to reveal deep layers of insight that could guide future enhancements and innovations in our product offerings, ensuring that they more effectively meet the needs and expectations of our users.

To initiate the task of evaluating the efficacy of the redesigned VSCOM landing page and the dedicated VS product page, our team at VS.com set out with a clear objective: to broaden our appeal to day-to-day developers by embodying values that are modern, attention-grabbing, inspirational, and conducive to learning and engagement. Under the leadership of the VSCOM Product Manager (PM) and with the collective effort of stakeholders, I began by refining our research objectives to focus on establishing a set of robust design principles for the new VSCOM design. Our method involved a comprehensive approach that included both qualitative and quantitative research techniques. We planned to gather feedback from new-to-Visual Studio customers to assess the effectiveness and reception of our redesigned pages. Our approach was two-fold: First, we aimed to refine and solidify the design principles guiding the new VSCOM aesthetic and user experience. This foundational step involved workshops, stakeholder interviews, and competitor analysis to ensure our design principles were not only innovative but also aligned with industry standards and user expectations. Second, we set out to empirically assess customer perceptions through surveys, usability testing, and analytics to compare the new design with the existing version and benchmark it against competitors. The end goal of our efforts was to ascertain whether the redesigned VSCOM pages effectively attracted and resonated with our targeted audience, conveying the set of values we aimed to embody. By achieving this, we hoped to not only enhance the user experience but also establish VSCOM as a forward-thinking, user-centric platform in the competitive landscape of development tools.

Within the realm of Customer-Driven Engineering (CDE) workshops, I've been instrumental in orchestrating dynamic, interactive sessions designed to empower both individuals and teams. These meticulously crafted workshops serve as a catalyst, aligning product development strategies authentically with user needs. Taking up a mentor role, I've guided and facilitated these workshops spearheading a transformative shift from a Know-It-All to a Learn-It-All mindset for the participating teams, which are typically a mix of different roles within the organization. Notably, among the teams I've had the privilege to work with, two were elected as winners from a pool of 9-10 CDE teams. This recognition provided them with the esteemed opportunity to present their learnings and innovative ideas to Senior Leadership. This success underscores the impact of instilling customer-centric values and methodologies, culminating in tangible achievements within the organization.