Why Great Engineering Doesn't Determine Market Success
Key takeaways
Customers do not buy technical elegance; they buy solutions to problems they care about.
Commercialization begins before requirements are written.
Some of the most exciting engineering projects create the least customer value.
Strong product development processes keep customer priorities connected to engineering decisions.
The product worked, but the market didn't care.
Engineering blamed pricing, sales execution, and marketing for the underperformance. Sales and executive leadership saw something different: customers simply did not value the problem the product was designed to solve.
Everyone was looking at the same outcome; they just interpreted it differently.
The earlier generation of this oilfield product was highly successful with strong market adoption. Its design wasn't perfect: Installation took time, and consumable components required periodic rebuilds. If maintenance was neglected, failures could occur.
Engineering saw an opportunity for improvement. So a team of three engineers spent roughly a year developing a more elegant solution. The new product installed faster, eliminated routine rebuilds, reduced maintenance requirements, and solved several shortcomings of the original design.
To be clear, engineering wasn't wrong; the new design was objectively better. The mistake was assuming customers shared the same priorities.
While engineering viewed the maintenance time and consumable costs as a problem to eliminate, customers viewed them as a manageable part of normal operations. To offset development costs and the loss of consumable revenue, the new solution also carried a significantly higher price tag.
Customers ultimately chose the less elegant solution because it met their needs at a price they were willing to pay.
Engineering had optimized for a problem customers weren't trying to solve.
Commercialization Begins Before Requirements
What made this experience particularly instructive is that engineers did interact with customers during development.
On site visits, they discussed the concept and highlighted its benefits. Customers generally responded positively.
But nobody asked:
Would you buy it?
How much would you pay for it?
Is this problem important enough to justify a higher purchase price?
There is a significant difference between a customer saying, "That's interesting," and a customer committing budget to purchase.
This distinction is one reason commercialization must begin before requirements are defined. Research from CB Insights found that lack of market need remains one of the most common reasons new ventures fail.[1]
The same principle applies inside established companies. Building something customers don't value is still building something customers don't value.
The Most Dangerous Projects Are The Most Technically Exciting
The projects that generate the most enthusiasm inside engineering organizations are rarely the projects that create the most value in the marketplace.
Elegant designs, novel technologies, and technically challenging problems naturally attract engineers’ attention — engineers enjoy solving difficult problems. That's part of what makes great engineering teams successful.
Customer pain points, however, may be much less technically exciting. Sometimes the highest-value opportunity isn't revolutionary; it's a small improvement that saves customers time, reduces risk, or simplifies their workflow.
That's why I frequently ask product development teams, “What will it take to wow our customers with this product?”
The room usually goes quiet for a minute or two. But it's also the moment the discussion shifts from cool engineering features to customer-facing value add.
The conversation changes. Teams stop talking about what they can build and start talking about what customers will actually value.
Assessing value throughout the new product design cycle
This particular product ultimately underperformed, but the lessons proved valuable to my client: The experience triggered the implementation of stronger voice-of-customer practices, portfolio prioritization, stage-gate reviews, and ultimately an Agile transformation that improved how the organization chased new opportunities.
Research consistently shows that organizations outperform when customer needs remain connected to product decisions throughout the development process.[2]
Engineering excellence creates possibilities.
Market success occurs when technical capability, customer value, and commercial reality align.
Great companies need both.
References
[1] CB Insights, The Top Reasons Startups Fail. https://www.cbinsights.com/research/startup-failure-reasons-top/
[2] McKinsey & Company, The Eight Essentials of Innovation. https://www.mckinsey.com/capabilities/strategy-and-corporate-finance/our-insights/the-eight-essentials-of-innovation
