Running the Process

Good customer conversations are wasted if the learning stays trapped in one person’s head. This final chapter covers the mechanics of running customer learning as a team process — taking notes, sharing insights, avoiding biases, and making sure the whole founding team benefits from what you learn.

The Notes Problem

Most founders either take no notes or take terrible notes. After a conversation, they remember a vague impression — “it went well” or “they seemed interested” — but cannot recall the specific facts that would actually inform decisions.

“Notes are useless if they just say ‘the meeting went well.’ Write down exact quotes and concrete facts.” — Rob Fitzpatrick

What Good Notes Look Like

Good notes capture:

• Exact quotes: “We spend about 10 hours per week on this” (not “they spend a lot of time on it”)
• Specific facts: “They use Salesforce and export to Excel for reporting” (not “they have some tools”)
• Emotional signals: “She got visibly frustrated when describing the approval process”
• Commitments made: “Agreed to a 15-minute demo next Thursday at 2pm”
• Key context: Their role, company size, how you found them

What Bad Notes Look Like

• “Great meeting! They loved the idea.”
• “Very interested. Will follow up.”
• “Seems like a good fit.”
• “They have the problem we’re solving.”

These notes contain no usable information. A week later, you will not remember what was actually said.

Sharing With Your Team

Customer learning should be a team sport. If only one co-founder talks to customers, the rest of the team makes decisions based on secondhand summaries, which are always distorted.

The Team Learning Process

1. Before the conversation: Share your top three questions with the team. Get input on what to ask.
2. During the conversation: One person leads, another takes notes. Never have more than two people from your side.
3. After the conversation: Within 24 hours, share the raw notes with the team. Discuss what you learned and what it means.
4. Weekly review: Set aside time each week to review all conversations from that period. Look for patterns.

The Debrief Meeting

After each conversation (or batch of conversations), do a quick debrief:

• What did we learn that was new? Focus on surprises, not confirmations.
• What did we learn that was concerning? Be honest about signals that challenge your assumptions.
• What should we ask next time? Update your question list based on new information.
• Does our customer segment still make sense? Adjust if the data suggests you are in the wrong segment.

Organizing Your Learning

As you accumulate conversations, you need a simple system to organize insights. Do not over-engineer this — a shared spreadsheet or document is usually enough.

A Simple Learning Tracker

Create a shared document with columns for:

• Date and person — Who you talked to and when
• Context — Their role, company, how you found them
• Key quotes — The most important things they said, verbatim
• Pain level — How much does this problem actually bother them? (1-5 scale)
• Current solution — How they handle the problem today
• Commitment — What they agreed to (if anything)
• Next step — What you will do as a result

This lets you spot patterns across conversations. When three different people mention the same workaround with the same frustration, you are onto something.

Avoiding Biases

Even with good notes and a good process, human psychology works against you. Founders are biased toward confirming their existing beliefs. Here are the most common traps.

Common Biases to Watch For

• Confirmation bias: You only hear the data that supports your idea and filter out the rest.
• Cherry-picking: You share the exciting quotes and skip the concerning ones.
• Leading questions: You unconsciously phrase questions to get the answer you want.
• Premature pattern-matching: You see a pattern after two conversations and stop looking for contradictions.
• Survivorship bias: You only talk to people who are willing to talk, ignoring the people who do not respond (who might be your most important non-customers).

How to Fight Bias

• Have someone else review your notes and flag where you might be filtering
• Track disconfirming evidence as carefully as confirming evidence
• Pre-commit to your top three questions so you cannot improvise toward flattery
• Share raw notes, not summaries — summaries are where bias hides
• Rotate who leads conversations so one person does not dominate the learning

When to Stop Talking and Start Building

Customer conversations should not go on forever. At some point, you have enough data to make a decision and start building. But how do you know when?

“At some point you have to stop talking and start building. The trick is knowing when that point arrives.” — Rob Fitzpatrick

You Are Ready to Build When

• You can describe your customer’s problem in their own words
• You know what they are currently doing to solve it
• You understand why the current solutions fall short
• Multiple people in your segment have expressed the same frustration
• At least some of them have given you a commitment (time, money, reputation)
• You stop learning new things in conversations

If most of these are true, you have enough signal to build a minimum viable product. If they are not, keep talking.

The Full Process Summary

The Mom Test Process, End to End

1. Define your segment — Who specifically are you trying to help?
2. Prepare your questions — What are the scariest, most important things to learn?
3. Find conversations — Go where your customers are, keep it casual
4. Ask about their life — Follow The Mom Test rules: their life, specifics, listen
5. Deflect bad data — Recognize and redirect compliments, fluff, and feature requests
6. Push for commitment — End with a concrete next step
7. Take good notes — Exact quotes, specific facts, emotional signals
8. Share with your team — Debrief, discuss, update your understanding
9. Look for patterns — Consistent problems across conversations signal real opportunity
10. Decide and build — When you stop learning new things, it is time to build

Key Takeaways

• Take notes with exact quotes and specific facts, not vague impressions
• Share raw notes with your team within 24 hours of every conversation
• Use a simple tracking system to spot patterns across conversations
• Fight confirmation bias by tracking disconfirming evidence as carefully as confirming evidence
• You are ready to build when you can describe the customer’s problem in their own words and have real commitments
• Customer conversations are a team process, not a solo activity