Final Thoughts

Throughout this book the main theme has been using a methodology in which it promises to help uncover unmet needs and provide alternative approaches to quantify, validate customer needs and alternative views at looking at customer problems to build better solutions.

However, in reality, many organizations already do a good job at exploring and validating customer needs. The biggest problem especially for large organizations is their inability to act on that knowledge and iterate.

Most companies have enough research. Actually, they have too much research. They have customer interviews, transcripts, quant results, analytics dashboards, all sitting in folders or different intranet websites. They have customer interviews sitting in forgotten folders. They have survey data that no one analyzed. They have support tickets that reveal the same pain points month after month. They have sales teams who know exactly why deals fall through. The information exists. It just never reaches the people who make decisions. Or it reaches them and gets ignored. Or it gets acknowledged and then deprioritized when the next quarter's targets loom.

This is the paradox. The better you get at uncovering customer needs or unique insights, the more clearly you see that the bottleneck was never the research. The bottleneck was actually the organizations willingness to change.

I have watched teams conduct rigorous foundational studies, identify clear opportunities, present compelling data, and then build the exact same roadmap they would have built anyway. The research became a box to check rather than a lens to see through. "Oh we did customer research with n=600 users", this is "validated". The methodology was followed. The insights were delivered. Nothing changed.

This is not a failure of JTBD. It is not a failure of ODI or MaxDiff or any particular framework. It is a failure of translation. Of timing. Of politics. Of incentive structures that reward shipping features over solving problems. Of cultures that treat customer research as a validation exercise rather than a discovery process.

If you take one thing from this book, let it be this. The frameworks are helpful but they are not enoguh. Learning to write a proper JTBD outcome statement is helpful. Understanding the flaws in the opportunity algorithm matters. Knowing how to triangulate quantitative rankings with behavioral data matters. But none of it matters if you cannot navigate the organizational reality that determines whether insights become products or slide decks.

Chapter 11 focused on contextualization, triangulation, and operationalization precisely because these are the skills that separate research that ships from research that sits. The methodology gets you to insight. The translation gets you to impact.

I wrote this book to demystify JTBD and provide practical alternatives to the rigid ODI approach. But I would be doing you a disservice if I let you believe that knowing all the methodology is the finish line. It is the starting line. The harder work comes after. It happens in the meetings where priorities get set. In the conversations where budgets get allocated. In the moments where someone with authority decides whether customer evidence outweighs internal opinion.

The best Researchers and Product Managers I know are not just skilled at research. They are skilled at reading organizational dynamics. They know when to push and when to wait. They know how to frame findings in language that resonates with different stakeholders. They know that being right is not the same as being effective.

This is the work that no methodology can teach you. It requires judgment, patience, and a willingness to play the long game. Sometimes the most important research skill is knowing that your findings will be ignored today but remembered six months from now when the product fails for exactly the reasons you predicted.

So yes, learn the frameworks and methodologies. Practice the techniques. Run the studies. But remember that the goal was never to become a better researcher. The goal was to help your organization build things that matter to customers. That requires more than methodology. It requires influence.

The research is one input. The strategy requires synthesis. The execution requires translation. And the impact requires an organization willing to act on what it learns.

This is the paradox. The better you understand your customers, the more you realize that understanding was never the hard part.

Ways to Support This Work

If this book has helped you or your team, here is a meaningful way to say thank you - buy me a coffee ☕

Your support is greatly appreciated!