Chapter 4: Keeping It Casual

Core Idea

Early learning about a customer and their problems works better as a quick, casual chat than as a formal meeting. Drop the “interview” setup, ask your most important question when the chance comes up, and reveal as little of your idea as you can.

Frameworks Introduced

• Keeping it casual:
  • Background: Steve Blank’s 4 Steps to the Epiphany recommends three separate meetings (problem, solution, sales) to avoid bias. The author found this too slow. A one-hour meeting costs about four hours once you count scheduling, travel, and review. It also asks a lot of the customer before you have anything to show.
  • The fix: keep the separation of problem, solution, and sales, but make the problem conversation a chat, not a meeting.
  • How: when you meet a likely customer, skip “let’s grab a coffee sometime” and ask your top question right away. For example, to a speaker at a conference: “How did you end up getting this gig?” You also become more memorable, which makes a later meeting easier to get.
  • Payoff: you can leave an industry meetup with a dozen useful conversations, each worth as much as a formal meeting.
• The Meeting Anti-Pattern: the tendency to put every chance for a customer conversation into a calendar block. It wastes time, makes people expect a product demo, and makes you miss chance encounters. The author’s analogy: if you meet someone you’d like to date in a café and awkwardly ask them out for coffee somewhere else, you’ve ignored that you were already on the date.
• Conversation length by stage:
  • Does the problem exist and matter? About 5 minutes at most.
  • Workflow, time use, and alternatives: usually 10–15 minutes. It can run longer if it’s useful to you and fun for them.
  • Industry details: an hour or more, usually with an expert who talks at length once pointed in the right direction.
  • Sales meetings once you have a product: about 30 minutes, roughly 5 minutes lost to lateness, 5 saying hello, 5 on goals, problems, and budget, 10 showing the product, and 5 on next steps and advancement.

Key Concepts

• Casual chat: a conversation where the other person may not realise a “meeting” happened.
• Symptoms of formality: “So, first off, thanks for agreeing to this interview. I just have a few questions for you and then I’ll let you get back to your day…”; “On a scale of 1 to 5, how much would you say you…”; “Let’s set up a meeting.”
• Founder time: the scarcest resource in a startup. Spend it where it matters most.
• Friendly first contacts: friends are fine to start with, because Mom Test questions keep friendship from biasing the data.

Mental Models

• Formality is a crutch for an awkward situation. It turns everything into a process and leaves no room for the unexpected.
• Good questions are about topics people find interesting: themselves and their daily annoyances. You may be the first person in a long time to show real interest, so these chats can be a pleasure for both sides.
• Save formal meetings for when you have something concrete to show.
• Even inside a formal meeting, small talk can carry your most important question.

Anti-patterns

• Scheduling a meeting for a 10-minute question: the scheduling overhead is bigger than the learning.
• Explaining your startup before asking anything: that can take 5–10 minutes and biases the answers.
• Survey-style scales and scripts: these make the person feel they’re doing you a favour.

Rules of Thumb (author’s wording)

• Learning about a customer and their problems works better as a quick and casual chat than a long, formal meeting.
• If it feels like they’re doing you a favour by talking to you, it’s probably too formal.
• Give as little information as possible about your idea while still nudging the discussion in a useful direction.

Worked Example

The investor dealflow tool, disproved in five minutes.

1. Assumption: investors receive hundreds of applications a month, so managing them must be a spreadsheet nightmare. The author set up meetings to learn about the industry.
2. Small talk at the first meeting: “You guys must get a ton of leads, right?” The investor laughed and agreed it was crazy.
3. Follow-up: “How do you deal with all that?” The investor pointed to about a dozen sticky notes on the wall, each with a name and phone number. Analysts reject most leads early, the partners discard more, and they phone the few serious contenders every couple of weeks. It works well.
4. Result: they don’t have the problem. The idea was disproved before the investor knew it was being discussed. There were no compliments, fluff, or ideas, only facts. (It still took a two-hour commute to reach those five minutes.)

Office managers at an industry event. The author had a product idea for office manager efficiency. He worked out the big questions over a weekend and went to an industry event on Monday. Over a beer, with questions like “X seems really annoying, how do you deal with it?”, “Is Y as bad as it seems?”, and “You did a great job with Z… where did you get that?”, he learned that their real problem was debt collection, not efficiency. Nobody realised they’d had a meeting.

Key Takeaways

1. Turn the problem conversation into a chat, and ask your top question as soon as you meet the right person.
2. Expect early chats to take 5–15 minutes. Don’t book an hour.
3. Keep your idea out of the conversation for as long as you can.
4. If they seem to be doing you a favour, you’re being too formal.
5. Keep the problem, solution, and sales separation even when you drop the formal meetings.

Connects To

• Ch 3: the list of 3 is what makes an unplanned chat useful.
• Ch 5: once you’ve chosen a solution, meetings become product meetings that need commitments.
• Ch 6: where to find these chats, and how to frame a meeting when you can’t avoid one.
• Steve Blank, Customer Development: the three-meeting structure this chapter simplifies.