Thank you so much for joining us in this interview series! Before diving in, our readers would love to learn more about you. Can you tell us a story about what brought you to this specific career path?
Thank you for having me! After graduating with a master’s in Michigan, I worked as a product development engineer for a consumer accessories start-up. After some time, I wanted to expand my capabilities within a more prominent organization and pursue my career path. While searching, I found an R&D verification engineer job opening at Abbott. I started to look more into what Abbott makes, and I discovered that Abbott is significantly impacting the medical device industry in delivering the best patient outcomes. It intrigued me to be a part of such a significant impact, and the role itself suited what I was looking for. Starting from there, being an R&D verification engineer, I had to understand how the product was intended to work. This is where it began; I learned and understood how hardware, software, and firmware interact with each other to perform as one product. This helped me make better strategic verification methods and provide insights into the development of the products. From there, I grew to Lead a Systems Test Engineer role, leading product system and hardware verification activities. Curiosity, Questions, Answers, and Opportunities brought me to this career path.
Do you have any mentors or experiences that have particularly influenced your approach to product development and user experience?
One of the experiences that influenced my approach while working with a field issue. After launching a product after one year of experience, a field issue was brought to R&D’s attention. As a part of the investigation, I was assigned to go through the issue of the product in-house and find all the possible ways customers could land on the issue. Doing this investigation helped me realize that every detail is essential for a quality product, and I have incorporated the idea of being an end user in developing verification activities.
It has been said that our mistakes can sometimes be our greatest teachers. Can you share a story about the funniest mistake you made when you were first starting? Can you tell us what lesson you learned from that?
During my third month after starting at Abbott, I am working on identifying a verification method to trigger a fault condition and verify that the product responds as intended. During this process, I successfully identified the method to trigger fault conditions, but I caused permanent damage to one of the product’s major components. I was terrified that something would happen, but after interacting with broader team members, that issue was resolved. From this, I learned two things from two different perspectives. Firstly, being a person who damaged the components, I knew that when any decision or new step is considered, I must assess the impact and consequences when implementing it. Secondly, being an observer of an unintended situation, I must look out of the box and resolve the issue more smoothly instead of panicking.
What do you feel has been your ‘career-defining’ moment? We’d love to hear the lead-up, what happened, and the impact it had on your life.
I have not met the ‘career-defining’ moment yet. However, multiple moments in my life gave me confidence that I was on the path that was best and meant for me. From understanding the United States course structure, I understood that with proper research and resources, any problem can be solved. From my work at a start-up, I had an opportunity to work directly with the company’s owner. I learned a business owner’s perspective on running and the risks of business, which led to the importance of product development. From working at Abbott, I had an opportunity to learn to work with diversified people and still have one common goal by working as a team. All these moments and experiences served me to better myself in all different aspects of life by understanding, growing, and giving.
Can you tell us a story about the hard times that you faced when you first started your journey? Did you ever consider giving up? Where did you get the drive to continue even though things were so hard?
When I was working at a start-up, the first few aspects of the product that was being developed went smoothly. At one point, a sub-component challenged me to the utmost, and it felt like I was struck at that point forever. No other similar products and sub-components were available to leverage the concepts. It took two weeks to identify and complete the design. There was no consideration or option of giving up. The only thing that drove me was feeling like I had met my limit and sincerely wanted to overcome my limitations. By self-motivation, I could overcome this by thinking creatively and out of the box.
Ok, super. Thank you for all that. Let’s shift to the main focus of our interview. How do you prioritize user experience when developing a new product, and what steps do you take to ensure that the final product meets the needs and expectations of your target users?
When we talk about user experience, the user experience element usually turns into one of the aspects of product development. However, it is essential to note and remind ourselves that user experience matters most in a successful product. Using product knowledge and customer requirements/expectations, in addition to system-level verification that meets the design input requirements derived from customer requirements, I have led the path to develop the system-level verification embedded with different use cases where a customer would use the product in various scenarios and situations. Using such use case scenarios helps in understanding and identifying the vulnerabilities in the product that might affect the user experience. Developing these use case testing strategies in a project requires insights from the clinical and marketing teams to understand how a customer engages with the product, as these two are the leading teams close to users. Through collaboration with clinical and marketing teams and developing these test strategies, we can ensure that the final product meets the needs and expectations of users.
Can you share any strategies you have for effectively gathering and analyzing user feedback?
As discussed earlier, creating use case scenarios with collaboration from clinical and marketing is one of the effective ways to gather and analyze user feedback. In addition to these two teams, field service representatives also hold enormous amounts of information as they are the closer personnel to users due to their job nature. Apart from this, attending industry-specific conferences and interacting with users at these conferences are significant platforms for effectively gathering and analyzing user feedback.
Can you share an example of a time when you received user feedback that prompted you to make significant changes to a product’s user experience, and how did you approach incorporating that feedback into the development process?
I got an opportunity to go for a field visit where I could interact with physicians who use our product daily. During this visit, I took feedback from physicians while they were using the product to identify a window of opportunity to make advancements to the product. After the visit, I shared the feedback received with the product owners, and they have incorporated the feedback into the following product versions.
How do you balance the need for simplicity and ease-of-use with more complex or advanced features in a product, and what strategies do you use to make sure that users can navigate those features without getting overwhelmed?
The balance between simplicity and ease of use needs a deep understanding of diverse user information and a design that can be a modular interface that separates the product’s core features from more complex options. Users can tailor their experience without feeling overwhelmed by offering customization and adaptive interfaces. Additionally, it is essential to implement defaults and automotive repetitive taste, the most straightforward interactions while gathering user feedback that will allow for future product revisions. This approach makes sure that the product remains accessible and concise for beginners while also providing depth and functionality for the power users.
What are some of the strategies you’ve used to make your product ‘stickier’ and increase user retention?
As a system-level verification role, I can ensure that customer needs are met. In this process, a constant development effort enforces the need to interact with users and stakeholders. From these interactions, a massive window of chance can be taken to implement features and build products that meet the user’s needs. Ensuring this, the product can be sticker and increase user retention.
In your experience, what are some of the most effective ways to measure the success of a product’s user experience, and how can this data be used to continuously improve the product over time?
Quantitative metrics combined with qualitative feedback work best for measuring the product’s user experience. Analysis of user behavior by analytics tools and usability testing or surveys provides deep insight into areas needing improvement. Monitoring these metrics and gathering direct user feedback helps me identify trends, prioritize enhancements aligned with user needs, and broadcast them to the product owners. It’s the data-driven approach to obtaining the continuous iteration and optimization of the product, with the objective that the evolution of the user experience follows expectations for high satisfaction levels over time.