The Product Market Fit Dilemma: When to Lead and When to Listen

When developing a new product, finding the right market fit is essential. It’s easy to fall into the trap of thinking your idea is perfect without thoroughly testing it with real customers. But direct contact with those customers—and listening to what they truly need—can make the difference between success and failure. As Steve Jobs once said, “People don’t know what they want until you show it to them.” However, just showing them isn’t enough—you also need to hear what they say in response.

The Temptation to Ignore the Voice of the Customer

When I was running a SaaS startup in real estate, we aimed to develop a new market analysis tool for real estate agents. We were excited—we thought we had conceptualized a user interface that was groundbreaking. It was sleek, modern, and intuitive, drawing inspiration from popular eCommerce and property search platforms. We believed the industry would embrace this innovation.

But when we showed it to experienced real estate agents, the feedback was sobering. They preferred the UX of the tools they had always used and simply wanted us to copy the old interface and add a few new features. As Jakob Nielsen famously said, “Users are reluctant to change interfaces they’ve spent time learning, even when an easier-to-use system is available.” These agents had invested years in mastering their legacy systems and weren’t excited about a change, no matter how innovative we thought it was.

To manage this, we applied the Build-Measure-Learn loop to guide our approach.

  1. We built an MVP version of the product, with just enough functionality to test the core concept. 

  2. We then measured adoption and feedback by running a pilot with both experienced and new agents, tracking how they interacted with the new interface. 

  3. Through this process, we learned that while new agents found the design intuitive, experienced agents preferred familiarity. 

Using this feedback, we iterated the product, blending familiar elements with the modern design. This iterative approach helped us refine the tool until we saw a 90% adoption rate, proving that users will embrace change if it meets their needs.

This strategy echoes the Dropbox case, where an MVP—a simple demo video—was used to gauge interest before fully developing the product. By focusing on learning from early users, Dropbox was able to validate its idea before investing heavily, just as we validated our CMA tool with both new and experienced agents.

The Danger of Moving Forward Without Direct Feedback

On the other hand, I’ve seen what happens when customer feedback is ignored or filtered through layers of assumptions. We were approached by a partner company in the healthcare space that provided a SaaS solution for home health aides (HHAs) and caregivers of elderly patients. Their idea was to create a shopping experience for aides to buy products on behalf of their patients. On the surface, it seemed like a good concept, and the company had conducted surveys and interviews with HHAs to back up their claims.

However, when we reviewed the data, the evidence was mixed at best. The feedback from the aides didn’t show any real pain points the service was addressing, but the company was convinced they had enough to move forward. When we asked to speak directly with the end customers, the partner refused, insisting that their research was sufficient. Reluctantly, but wanting to maintain a strong relationship with our partner company, we decided to take a risk and moved ahead with a minimum viable product (MVP). As we feared, it struggled to gain traction.

This reminds me of Segway, which launched with great hype as a revolutionary mode of transportation. However, Segway failed to solve a meaningful problem for most people. It didn’t resonate with consumers, and the company moved forward without understanding the actual transportation needs of its target audience. Like Segway, we pushed ahead without adequately validating our assumptions with the end users, resulting in a product that missed the mark.

Only after the failure were we allowed to speak directly with the HHAs. It was then we discovered what should have been obvious all along—the product didn’t address their real needs. Many patients preferred going out and shopping with their aides, enjoying the social interaction, rather than having products delivered. We had built something that didn’t solve a genuine problem, and the product never found its market.

Balancing Innovation with Customer Needs

These two experiences taught me that finding product-market fit is about balancing vision with customer feedback. Steve Jobs was right—customers don’t always know what they want. Sometimes, you have to lead with a bold innovation and show them something new. But that doesn’t mean you can ignore what they tell you once they’ve seen it. As Jakob Nielsen noted, “The more discoverable and intuitive the interface, the more users will be willing to explore beyond the defaults.”

With the CMA tool, we pushed forward despite initial resistance from experienced agents, confident that the modern interface would ultimately win them over. And while we faced challenges, careful iteration and a willingness to balance innovation with familiar elements led to success. In contrast, when we moved ahead with the healthcare SaaS product without fully validating user needs, the product failed to gain traction.

The lesson? Sometimes pushing forward with a vision means facing early criticism, but success comes from balancing that vision with customer feedback. Direct contact with users is vital. If you approach conversations with an open mind—accepting that your idea might not be perfect—you can strike the right balance between innovation and user needs to truly find product-market fit.

Comments

Post a Comment

Popular posts from this blog

Nike’s Bold Global Strategy: A Case Study in Rapid Digital Expansion

Image
By the early 2010s, Nike had already established itself as a leader in digital commerce, setting a high bar with its groundbreaking launches of nike.com in Japan (2013) and China (2014). These markets were a testament to Nike’s ability to deliver large-scale digital experiences, but they came with significant investment—each project took 18 months and multi-million-dollar budgets to bring to life. As the global demand for Nike’s products surged, the company faced a new challenge: could it replicate the success of these digital rollouts on a much larger scale, but with fewer resources and in a faster timeframe? The stakes were high. While Nike had cemented its position as a global digital leader, the demand for full-scale global expansion was growing rapidly. Consumers in smaller, emerging markets were eager for access to Nike’s full product line. However, building localized infrastructure in every market wasn’t a sustainable solution. Nike needed to rethink its approach—one that would ...
Read more

The Product Model

Image
  The Product Model provides a structured framework that guides product teams through the critical stages of defining, solving, and delivering solutions, ensuring a customer-centric and successful outcome. In a recent article , I discussed Product Leadership and Coaching with “The two A’s and the three P’s framework.” 2A3P sounds like a cool new android in an upcoming Star Wars movie. If so, they would be a Product Manager fluent in over 6 million languages.  To recap… Alignment and Autonomy provide your foundation for building a successful product. Alignment across the organization on what you are doing and why you are doing it is your starting point, your shared vision on the current state and the desired future state. Autonomy enables teams to determine the best way to achieve the shared vision. When leadership provides clarity on the what and why, teams are free to focus on the how, using their expertise and creativity to solve challenges and deliver results. People, Proc...
Read more

Leadership in Product Management: Alignment and Autonomy

Image
In an interview, I was asked if I had a mantra or metaphor for my leadership style. At the time, I didn’t have an answer prepared. I did some verbal tap dancing but ultimately didn’t get the job. Reflecting on that question, my answer today is Alignment and Autonomy. Leadership in product management is about providing strategy—the what and why —and ensuring the organization is aligned around it. Once alignment is achieved, teams are given the autonomy to determine how to execute the vision. This balance creates the conditions for innovation, adaptability, and success. Vision and Strategy Strategy starts with intent: defining what you want to achieve and why it matters. Leadership connects the current state to a desired future, ensuring the team understands the opportunity, value proposition, and competitive landscape. Think of strategy as a staircase. Each step represents an incremental action, building toward a stronger position. Leadership outlines a multi-year plan that enables th...
Read more