Nova: Peris, let me paint a picture for you. You've spent months, maybe even years, perfecting a design. It's elegant, it's efficient, it's a marvel of engineering. But what if the problem it solves so beautifully... isn't a problem anyone actually cares enough about to pay for?

Peris Karanga: Nova, that's the nightmare that keeps every entrepreneur, especially in engineering, up at night. You can fall in love with the elegance of your own solution and completely miss the mark on the market. It's a terrifyingly common trap.

Nova: It is! And that's why we're diving into Rob Fitzpatrick's "The Mom Test" today. It's this brilliant, practical guide on how to stop people from lying to you about your business idea. And we're going to look at it through the lens of an entrepreneur in the engineering and manufacturing world.

Peris Karanga: Which is a world full of solutions looking for problems, so this is a much-needed conversation.

Nova: Exactly. So today we'll dive deep into this from two perspectives. First, we'll explore the simple but powerful rules of 'The Mom Test' itself—how to ask questions that get you the truth. Then, we'll discuss how to become a master data analyst in these conversations, separating the worthless noise of compliments from the golden signal of real customer commitment. Ready to build a better blueprint?

Peris Karanga: Let's do it. I'm ready to take the test.

Nova: So, the core premise of the book is that everyone, from your mom to a potential enterprise client, is wired to lie to you when you ask for their opinion on your idea. Not maliciously! They lie because they want to be supportive, they like you, or they just want the conversation to be over.

Peris Karanga: It's the path of least resistance. Saying "That's a great idea!" is so much easier than "I would never, ever use that, and here's why." That's a socially awkward conversation nobody wants to have.

Nova: Precisely. And Fitzpatrick tells this perfect story to illustrate the danger. Imagine an entrepreneur, a son, who has an idea for a digital cookbook app for the iPad. He goes to his mom and asks, "Mom, do you think this is a good idea?" He pitches the features, the price... and of course, she says she loves it! She's his mom!

Peris Karanga: Of course. She's not evaluating a business plan; she's supporting her son.

Nova: Exactly. So he takes this "validation," quits his job, pours his savings into building the app... and it completely flops. Nobody buys it, not even his mom. He got a false positive because he asked the wrong questions. He failed The Mom Test.

Peris Karanga: That story is painful because it's so real. In manufacturing, a compliment could be a potential client saying, "Wow, that's a really innovative piece of machinery!" But that doesn't mean they'll rip out their existing, functioning production line to install it. The compliment is free; the switching cost is enormous.

Nova: That is such a great point. The cost of the compliment is zero. So, how do we fix this? The book gives us three simple rules. One: Talk about their life instead of your idea. Two: Ask about specifics in the past instead of generics or opinions about the future. And three: Talk less and listen more.

Peris Karanga: I love the clarity of that. It's a simple algorithm for a better conversation. The second rule, "ask about specifics in the past," really resonates with an engineering mindset.

Nova: How so?

Peris Karanga: Well, in engineering, when something fails, we perform a post-mortem. We don't ask, "What do you hypothetically think might go wrong in the future?" We ask, "What specifically happened? Walk me through the sequence of events that led to the failure." We're gathering concrete data about past events to inform future designs. This is the exact same principle, but applied to customer problems.

Nova: That's a fantastic connection. You're not asking, "Would you use a cookbook app?" You're asking, "Tell me about the last time you used a recipe. What was that experience like?"

Peris Karanga: Right. You're not asking the client, "Would you buy my new, faster machine?" You're asking, "What were the production numbers on your main line last month? What were the primary causes of downtime? How much did that downtime cost you?" You're excavating their reality, not pitching your fantasy.

Nova: You're excavating their reality! I love that. And that's the whole point. The book uses this analogy of an archaeological dig. The truth is a fragile artifact buried underground. If you go in with a bulldozer—"ISN'T THIS A GREAT IDEA?!"—you'll smash it to pieces. You have to use brushes and carefully dig.

Peris Karanga: And the answers to those specific, past-focused questions are the brushes. They gently uncover the real shape of the problem you might be able to solve. Or, just as importantly, they reveal that there's no problem there at all.

Nova: Okay, so that's a perfect transition. If we're not supposed to listen to compliments like "That's a great idea," what we listening for? That brings us to our second point: separating the signal from the noise.

Peris Karanga: The data analysis part of the conversation. My favorite.

Nova: I figured it would be. Fitzpatrick says there are three types of bad data we get all the time: Compliments, which we've covered. Fluff, which is generic claims and hypothetical future promises like "I would totally buy that!" And Ideas, as in feature requests.

Peris Karanga: The feature request trap is a big one. A customer says, "You should add a blue button," and you run off and spend a month adding a blue button without ever asking they think they need it.

Nova: You are channeling this book perfectly. That's exactly the point of another great story. A team was talking to finance professionals who were complaining about managing spreadsheets. Their initial request was for a better messaging tool to save time. The team could have just built that.

Peris Karanga: The blue button.

Nova: The blue button! But instead, they asked a crucial question: "Why do you even bother sending all these emails?" And the answer wasn't about saving time. The real, underlying problem was that they needed to be absolutely certain everyone was working from the latest version of the spreadsheet.

Peris Karanga: Ah, so the problem wasn't communication efficiency. It was version control. A completely different problem space.

Nova: Completely! Asking "why" revealed the root cause. And that insight is the difference between building a slightly better email tool and building Dropbox.

Peris Karanga: You know, that is exactly like the "5 Whys" technique we use in manufacturing for root cause analysis. A machine stops. Why? The fuse blew. Why? The circuit was overloaded. Why? The motor drew too much current. Why? The bearing was seizing. Why? It wasn't lubricated. The problem isn't the fuse; it's the lack of lubrication. The feature request is the fuse. You have to dig for the lubrication schedule.

Nova: Yes! That's the perfect analogy. So, if we're ignoring compliments and digging past feature requests, what's the "good data"? The book says it boils down to one thing: Commitment. It's the only signal that cuts through the noise.

Peris Karanga: And commitment isn't just a verbal "yes."

Nova: Never. It's a real currency. The book identifies three main types: Time, Reputation, and Cash. Are they willing to give you an hour for a follow-up meeting with their whole team? That's a time commitment. Are they willing to introduce you to their boss or another key decision-maker? That's a reputation risk for them. Are they willing to sign a letter of intent or, even better, give you a deposit? That's a cash commitment.

Peris Karanga: That's a tangible framework. In my world, a real commitment might be a client agreeing to dedicate their own engineering resources to a joint pilot program. That's a huge signal. It means they're not just curious; they're invested in finding a solution. A pre-order for a new piece of equipment is great, but a signed letter of intent that I can take to my investors to secure funding for the production line? That's gold. That's real validation.

Nova: That's the real validation. Anything short of that—a compliment, a "keep me posted," a "sounds interesting"—is just noise. It's fool's gold. And the job of the entrepreneur is to be a data scientist who relentlessly filters for the signal of commitment.

Nova: So, as we wrap up, it feels like we've landed on two incredibly powerful, actionable ideas from "The Mom Test" for any entrepreneur, but especially for someone with an engineering background.

Peris Karanga: I think so. For me, the two big takeaways are, first, reframe your questions to be about their past problems, not your future solution. Become an archaeologist of their workflow.

Nova: I love that. And the second?

Peris Karanga: The second is to treat the conversation as a data-gathering mission where the only valid signal is commitment. Filter out the noise of compliments and fluff, and measure success by whether the customer is willing to give you their time, their reputation, or their money.

Nova: Beautifully put. The book offers a simple, practical way to start implementing this immediately. Before your next customer meeting, or any meeting where you need to learn something, take two minutes and write down the three most important questions you need to learn the answers to. And importantly, these should be the scary questions—the ones that could potentially prove your idea is bad.

Peris Karanga: I'd add to that: and be prepared to love the bad news. Finding out your idea is flawed on paper is infinitely cheaper and faster than finding out after you've built the factory. The goal isn't to get a 'yes.' The goal is to get to the truth.

Nova: A perfect final thought. Get to the truth. That's the test. Peris, thank you so much for digging into this with me.

Peris Karanga: This was fantastic, Nova. A great reminder to stay curious and ask better questions.