Chapter 9: Conclusion and Cheatsheet

Core Idea

You’ll keep making mistakes; the author still slips into pitch mode in important meetings. Notice them, review as a team, and improve. Process helps, but sometimes the fastest route is to skip it and act directly. (This is a short chapter. Most of its value is the author’s own summary list, condensed below.)

Frameworks Introduced

• It’s going to be okay: most bad conversations can be fixed, and people want entrepreneurs to succeed. If the venture fails anyway, thank the people who supported you.
• Hack it (the Gordian Knot): Alexander cut the knot instead of untying it. Don’t spend hours perfecting a validation plan when you can just ask directly.
  • When to use: whenever planning how to learn something starts taking longer than learning it.
  • How: ask whether one direct action (a phone call, a request) would answer the question now.
• Results of a good meeting:
  • Facts: concrete, specific facts about what they do and why they do it, as opposed to compliments, fluff, and opinions.
  • Commitment: they show they’re serious by giving up something they value, such as meaningful amounts of time, reputation risk, or money.
  • Advancement: they move to the next step of your real-world funnel and get closer to a sale.

The Author’s Cheatsheet (condensed)

• Key skills and where they’re taught: asking good questions (Ch 1, 3); avoiding bad data (Ch 2); keeping it casual (Ch 4); pushing for commitment and advancement (Ch 5); framing the meeting (Ch 6); customer segmentation (Ch 7); prepping, reviewing, and note-taking (Ch 8).
• The Mom Test: talk about their life instead of your idea; ask about specifics in the past instead of generics or opinions about the future; talk less and listen more.
• Getting back on track: deflect compliments; anchor fluff; dig beneath opinions, ideas, requests, and emotions.
• Mistakes and their symptoms:
  • Fishing for compliments: “do you think it will work?”
  • Exposing your ego (The Pathos Problem): “be honest and tell me what you really think!”
  • Being pitchy: “No no, I don’t think you get it…”
  • Being too formal: “thanks for agreeing to this interview…”, “On a scale of 1 to 5…”, “Let’s set up a meeting.”
  • Being a learning bottleneck: “Because the customers told me so!”
  • Collecting compliments instead of facts and commitments: “Everybody I’ve talked to loves the idea.”
• Signs you’re going through the motions: the Ch 8 list, plus two additions: “You aren’t sure which big question you’re trying to answer” and “You aren’t sure why you’re having the meeting.”
• Signs you aren’t pushing for commitment: zombie leads; product meetings ending in compliments or with no next steps; meetings that “went well”; they haven’t given up anything of value.
• Framing (VFWPA): Vision (half a sentence on how you’re making the world better); Framing (where you’re at and what you’re looking for); Weakness (where you’re stuck); Pedestal (why they in particular can help); Ask.
• The big prep question: “What do we want to learn from these guys?”

Key Concepts

• Hack: a direct shortcut to the result that skips the “proper” process.
• Craft, not science: startup skills come from doing. The author says he learned more from launching small projects than from books or blogs.

Mental Models

• Treat mistakes as normal. The goal is to notice and fix them, not to be perfect.
• Use a process as a default, not as a requirement.

Anti-patterns

• Over-analysing validation: designing interview plans when a single call would answer the question.
• Blaming yourself or cofounders for bad conversations: review and improve together instead.

Rules of Thumb (author’s wording)

• It’s going to be okay.

Worked Example

The personal trainer and the police. At a segmentation workshop, a personal trainer said most of his time went on unpaid travel between clients. Someone suggested police officers as customers: he could spend a whole day at one station, with no commuting, more billable hours, and less price sensitivity. The group started planning how he should validate this, with ideas about relatives in the police, interview questions, and market size. He held up his phone, said he’d just call them, and stepped outside. Twenty minutes later he came back with a trial session booked.

Key Takeaways

1. A good meeting produces facts, commitment, or advancement. Anything else is noise.
2. Expect to make mistakes, and use team reviews to catch them.
3. Before designing a process to learn something, check whether one direct action would answer it.
4. Keep the cheatsheet lists as a pre- and post-meeting checklist.

Connects To

• Ch 1–8: this chapter is the index to all of them.
• Ch 8: the process and warning signs are repeated here.