Tell me about a time when you had to change your initial decision based on new information or input from others.

Example Answers

E-Commerce Specialist

Sure, happy to share an experience with you. At my previous role as a product manager for an e-commerce platform, we were working on a redesign of our checkout flow to reduce cart abandonment rates. We had initially planned on introducing a new feature that would allow users to create an account during the checkout process.

However, during a user testing session, we observed that a majority of users were hesitant to create an account as they found it to be a barrier to completing their purchase. Additionally, we received feedback from our customer support team that users were also struggling with the password reset process for existing accounts and were becoming frustrated.

Upon gathering this feedback, I realized that our initial decision may have a negative impact on our conversion rates rather than a positive one. After consulting with the team, we decided to pivot our design and remove the mandatory account creation feature during the checkout flow instead.

The impact of this change was significant - our cart abandonment rates decreased by 30%, and we were able to increase our conversion rates by 25%. Additionally, we received positive customer feedback, and our customer support team reported a reduction in call volumes related to account issues.

Through this experience, I learned the importance of gathering user feedback and actively listening to the input of other team members. While we had a plan in place, it was ultimately the feedback from our users and customer support team that led us to change direction and achieve better results. Moving forward, I made it a point to prioritize user research and validation throughout the product development process.

Mobile App Guru

One of the most important aspects of product management is to be able to adapt quickly to changing circumstances or new information. There have been many instances in my career as a product manager where I have had to change my initial decision based on new information or input from others.

One example that comes to mind was when I was working on a social networking app that was designed to help users share photos and videos with their friends and family. We had initially designed the app to have a robust commenting system, where users could leave comments on photos and videos and have conversations with their friends.

However, after conducting some user research and talking to our beta testers, we discovered that the commenting system was actually causing more harm than good. Many users felt intimidated or uncomfortable leaving comments, particularly on photos that were highly personal or emotional.

Based on this feedback, we decided to remove the commenting system entirely and focus on other engagement metrics, such as likes and shares. This was a difficult decision, as we had already invested a lot of time and resources into developing the commenting system.

However, the impact of the change was almost immediate - we saw a significant increase in user engagement and retention. By removing the commenting system, we had made the app less intimidating and more accessible to a wider range of users. We also learned an important lesson about the importance of user feedback and the value of being open to changing course based on new information.

Overall, this experience taught me that the key to success as a product manager is to remain open to feedback and to be willing to change course when necessary. It can be easy to become attached to a particular feature or design, but ultimately the only thing that matters is whether it is successful in engaging and retaining users.

Consumer Electronics Enthusiast

Certainly. As a product manager, there have been times when I've had to make difficult decisions based on incomplete or conflicting information. One instance that comes to mind is when I was working on a consumer device that was designed to be used in homes. Initially, I believed that the device needed to have a standalone mobile application to control it, and I began to design the user interface for the app.

However, during the development process, we received feedback from our user research group indicating that many potential customers found the app to be too complicated and overwhelming. They preferred a simpler, more intuitive interface that could be accessed directly from the device itself.

I realized that I needed to change my initial decision to include an app and instead focus on creating a great user experience for the device. I conducted additional research, and we ended up reworking the device's interface to make it more user-friendly and less dependent on the app.

The impact of this change was significant: our user research group reported much higher satisfaction rates, and we saw increased interest from our target demographic. Additionally, our manufacturing costs were lowered since we no longer needed to build and maintain a separate mobile app.

Through this experience, I learned the importance of humility and openness to feedback. It's essential to listen to the people who will be using your product and be willing to make changes when necessary. By doing so, you can create a better experience for your customers and ultimately drive business success.

Enterprise Software Savant

Absolutely. One example of a time when I had to change my initial decision in light of new input was during my time managing a large-scale enterprise software project. I had initially decided to use a certain technology that I believed would work well for our needs and fit within our timeline. However, during a routine check-in with the development team, one of the senior developers raised concerns about the chosen technology and explained that it would likely cause significant technical debt down the line, making it difficult to maintain and upgrade the software.

I realized that I needed to take a step back and do more research to understand the long-term implications of our technology decisions. This involved reviewing the latest industry research and reaching out to experts in the field for their input. It also meant sitting down with the development team to hear their perspective and concerns in more detail.

Ultimately, I decided to change our chosen technology based on this new information. Although this caused a delay in the project timeline, it was clear that it was the right decision in the long run and would save us significant headaches down the line. The team as a whole was supportive of this new direction, and we were able to make up the lost time through other efficiencies in the development process.

Reflecting on this experience, I learned a valuable lesson about the importance of being open to new information and input from others. As a product manager, it can be tempting to rely on one's own expertise and instincts, but it's crucial to stay humble and receptive to others' perspectives, especially when working on a complex project. Through this experience, I also learned the importance of taking the extra time to research and vet technology decisions thoroughly to ensure that they align with the long-term goals of the project and the organization.

SaaS Strategist

Sure, I'd be happy to answer that question. Here's an example of a time when I had to change my initial decision based on new information:

In my previous role as a product manager for a SaaS company, we were in the process of releasing a new feature. My initial decision was to include the feature as part of our premium subscription package. However, after presenting the idea to the marketing team for feedback, they suggested that the feature would have a wider appeal if it was included in our lower-priced subscription plan as well.

I discovered this new information through open communication and collaboration with my colleagues, specifically through gathering feedback from the marketing team.

After weighing the pros and cons, I decided to change my initial plan and include the feature in both subscription packages. This decision led to an increase in customer retention, as it provided more value for our lower-priced plan and encouraged customers to upgrade to the premium plan for additional features.

In retrospect, this experience taught me the importance of seeking feedback and collaboration from colleagues with different perspectives and skill sets. It also reinforced my belief in prioritizing customer needs and desires in product decision-making.

Cybersecurity Expert

Sure, I'd be happy to share an example of a time when I had to change a decision based on new information and input from others.

In my previous role, I was managing a cybersecurity product that was designed to protect businesses from email-based threats such as phishing and malware attacks. We had initially planned to develop a feature that focused solely on detecting and blocking malicious links in emails, as this was identified as one of the biggest threats at the time.

However, during a customer research study where we interviewed our target audience of SMBs and enterprises, we started to hear more about the growing threat of email-based ransomware attacks. This was a newer and more sophisticated type of threat that was usually spread through attachments rather than links. During the study, we discovered that many of our customers were more concerned about mitigating the impact of ransomware attacks on their business operations than just blocking malicious links.

Based on this new insight and feedback, we decided to pivot our product development focus to also include advanced threat protection against ransomware attachments. This decision required a significant amount of work such as building detection engines that could scan email attachments for the signs of ransomware, and integrating with additional third-party security vendors. However, we knew this pivot was the right decision from both a customer and market perspective.

The impact of this change was significant. We were able to launch a more comprehensive product that satisfied our customers increased need for visibility and control over these emerging threats. As a result, this led to an increase in customer satisfaction and sales revenue for our organization.

What I learned from this experience is the importance of continually listening to our customers and market trends to inform our product development decisions. It's essential to be agile and willing to pivot our strategy if necessary to ensure that we're meeting our customers' needs and staying relevant in the ever-evolving landscape of cybersecurity.