A developer's guide to learning from customers without the meeting overhead
If you've been following my series on "The Mom Test" by Rob Fitzpatrick, you know we've been exploring how to have better conversations with customers. Today, I want to share what I learned from Chapter 4: Keeping It Casual.
Here's the big idea: formal meetings can actually hurt your customer learning.
Sounds counterintuitive, right? Let me explain.
The Problem with Formal Meetings
We developers love structure. When we want to learn something from customers, our first instinct is often to schedule a meeting. But Rob Fitzpatrick argues this is actually a trap.
Think about it. When you schedule a formal meeting:
- The customer knows you want something from them
- They put on their "meeting behavior"
- They try to be polite instead of honest
- Everything becomes awkward and formal
The author shares that Steve Blank, in his book "4 Steps to the Epiphany," recommends 3 separate meetings: one about the customer's problem, one about your solution, and one to sell the product. The idea is to avoid what Fitzpatrick calls the "Pathos Problem"—where you jump too quickly into emotional selling mode.
But here's the thing: setting up 3 formal meetings is incredibly time-consuming. Once you factor in scheduling, travel, preparation, and the actual meeting, a single 1-hour meeting can cost you 4+ hours of your time.
And as the author puts it: "The most precious resource in a startup is its founders' time."
The Solution: Keep It Casual
So what's the alternative? Keep your conversations casual and informal.
Instead of sending a calendar invite, just have a chat. Instead of a conference room, talk at a coffee shop. Instead of an interview, have a conversation.
Here's a great example from the book. Imagine you're at a conference and you bump into someone in your target industry. Instead of saying:
"Can I schedule a meeting to interview you about your problems?"
You say:
"Hey, I'm curious—how did you end up getting this gig?"
See the difference? One feels like work. The other feels like genuine human curiosity.
When you strip all the formality from the process, something magical happens:
- No meetings to schedule
- No "interviews" to conduct
- Conversations become fast and lightweight
- You can talk to a dozen people at a single industry meetup
The Meeting Anti-Pattern
The author introduces a concept called "The Meeting Anti-Pattern." This is the tendency to relegate every customer conversation into a calendar block.
Beyond being a bad use of time, our over-reliance on formal meetings makes us miss serendipitous learning opportunities.
Here's a funny example from the book: Imagine you're at a café, and your dream customer sits next to you. Instead of just starting a natural conversation, you psych yourself up and then fumble through an awkward pitch asking if maybe they want to get coffee sometime... at a different place.
That's ridiculous, right? You're already having coffee together! Just talk to them like a normal human being.
How Formal Is Too Formal?
Here are some warning signs that your conversation is too formal:
- "So, first off, thanks for agreeing to this interview..."
- "On a scale of 1 to 5, how much would you say..."
When you start with phrases like these, you immediately put the other person in "interview mode." They feel like they're doing you a favor, which creates an ominous atmosphere where they'll say whatever they think you want to hear.
Learning from customers doesn't mean wearing a suit and sipping boardroom coffee. The right questions are fast, interesting, and touch on topics people genuinely enjoy discussing.
Rule of thumb from the book: If it feels like they're doing you a favor by talking to you, it's probably too formal.
At their best, these conversations are a pleasure for both parties. You're probably the first person in a long time to be truly interested in the petty annoyances of their daily work.
How Long Should These Conversations Be?
This surprised me: early conversations can be incredibly short.
- 5 minutes is enough to learn whether a problem exists
- 10-15 minutes gets you into their workflow, time usage, and what they've tried before
- 30+ minutes happens naturally when you hit a topic they love (people enjoy talking about themselves!)
The longer conversations are easier to facilitate because once someone starts explaining their work, they can go into a monologue. You just need to point them in the right direction.
But here's the catch with formal B2B meetings: the duration is often determined by the arbitrary calendar block (usually 30 minutes or 1 hour), not by what you actually need to learn. You might lose:
- 5 minutes to miscellaneous tardiness
- 5 minutes to saying hello and small talk
- 10 minutes to product demos
- 5 minutes to figuring out next steps
That's half your meeting gone before you even start learning!
Putting It Together: A Real Example
The author shares a great story about trying to get feedback from busy investors who manage their dealflow with hundreds of meetings per month.
Instead of trying to schedule yet another meeting in their packed calendars, he showed up to an industry meeting and, during casual small talk, mentioned: "Our analysts kill most of them before they ever reach us."
That was it. One sentence during small talk. The investor responded with a bunch more details about how they deal with applications, pointed at some sticky notes on the wall, and shared exactly how their process worked.
It took 5 minutes. No formal meeting. No biases. No compliments. Just concrete facts.
Now compare that to someone who takes a 2-hour commute to attend a formal meeting. They might get the same information (or worse), but at a much higher cost.
The lesson? Sometimes a casual 5-minute chat is worth more than an hour-long formal meeting.
The Visionary Leap
Here's the beautiful part: once you've collected all these casual insights, you can take what the author calls the "visionary leap."
You take everything you've learned—all the problems, all the frustrations, all the workarounds—and you come up with a specific offering that makes your customers' lives better. Then you ask them to commit to it.
But you can only make this leap if you've been listening properly. And proper listening happens in casual, honest conversations—not in formal interviews where people tell you what you want to hear.
Key Takeaways
Let me summarize the main lessons from this chapter:
Formal meetings create bias. People behave differently when they know they're being "interviewed."
Casual conversations are faster and more honest. You can learn in 5 minutes what might take an hour in a formal setting.
The first conversation doesn't need to be a meeting. It works better as a casual chat.
Your time is precious. Don't waste 4 hours on meeting overhead when a 10-minute conversation would give you the same insights.
Serendipity is your friend. Be open to learning opportunities everywhere—conferences, coffee shops, random encounters.
If they feel like they're doing you a favor, it's too formal. The best conversations are enjoyable for both parties.
Rule of Thumb
I'll leave you with the book's main rule for this chapter:
"Learning about a customer and their problems works better as a quick and casual chat than a long, formal meeting."
And one more:
"Give as little information as possible about your idea while still nudging the discussion in a useful direction."
That's it for Chapter 4! The message is clear: stop hiding behind formal meetings. Get out there, talk to people like a normal human being, and you'll learn so much more.
In the next chapter, we'll explore more techniques for having effective customer conversations. Stay tuned!
This post is part of my series on "The Mom Test" by Rob Fitzpatrick. I'm a developer learning product management and customer validation, sharing my learnings with fellow developers who want to build products that people actually want. All examples and stories are credited to the original author.
What do you think? Have you experienced the difference between casual and formal customer conversations? Let me know in the comments!
Top comments (0)