![\"The](\"/images/june/the-mom-test.png\")
\nThe goal of this series of posts is not to provide the summary of the book. The goal is to save ideas for myself for later reflections or use.
\nAs I said I've happened to launch several pet projects without proper research, which led to them being not successful among potential users. The reason behind that is believing that solving your (=my) pain will be solving other's. Although this might be true for some cases, it turns out to be false judgement for the majority.
\nThe main mistake everyone (including myself) keep making is being sure the idea is worthy of being tested. The very first and the single most important step you need to take is conduct user interviews. That's exactly the topic 'The Mom Test' covers.
\n\nShould you be working on a project of your own, planning to launch something or just have an idea you want to test out – this book is for you. You will receive the foundational understanding of what needs to be done before any idea gets into production / validation / testing phase – and what will separate you from the rest.
\nThe main takeaway from this book is you have to ask the right questions to your prospective clients and be ready to receive unpleasant responses. The goal you have in mind is building something that is truly valuable to your customers and that makes their lives better.
\nThe book provides a great example of an interview that you would usually conduct with your mom: you would ask questions that you expect to receive pleasant answers to ('Do you like this idea? Would you use it?') and your mom would provide answers you would like to hear because she loves you so much ('Yeah, that's amazing! Of course I would! It costs \\$40? I would do it anyway!')
\n\n\nQuestions you ask should cover the lives of your clients: their problems, worries, goals and limitations.
\n
\n\nYou should not be talking about what you think the potential client's problem is and they should not be telling you what product to make. Problem lays on their side, solution is on yours.
\n
\n\nYou already know how to react to compliments: avoid, ignore, come back to the main topic.
\n
This struck me as really interesting, since your natural desire is to actually enjoy the compliments and praises you receive as you think they validate your idea. Not quite.
\n\n\nThe only thing people talk about with greater interest than themselves is their problems.
\n
Love this. It made me believe I can get a lot of insights from potential users just by asking them about their pains and problems. Definitely a thing to be remembered.
\n\n\nVision / Framing / Weakness / Pedestal / Ask (Very Few Wizards Properly Ask for help)
\n\n
\n- Vision: You’re an entrepreneur trying to solve horrible problem X, usher in wonderful vision Y or fix stagnant industry Z. Don’t mention your idea.
\n- Framing: Frame expectations by mentioning what stage you’re at, and if it’s true, that you don’t have anything to sell.
\n- Weakness: Show weakness and give them the chance to help by mentioning the specific problem you’re looking for answers on. This will help clarify that you’re not a time waster.
\n- Pedestal: Put them on a pedestal by showing how much they, in particular, can help.
\n- Ask: Explicitly ask for help.
\n
Great way of framing the meeting to have the best possible outcome.
\nOverall there is an extensive list of things to remember before / in the process / after the interview in the end of the book which you can refer to anytime.
\nSome high-level thoughts and notes:
\n