Customer Development Theatre

The founder proudly displayed the spreadsheet. Fifty customer interviews. Detailed notes. Color-coded themes.

"What did you learn?" the advisor asked.

"We validated our hypothesis. Customers have the problem we thought they had and want the solution we're building."

"Did any interviews surprise you? Make you reconsider anything?"

Pause. "Not really. The interviews confirmed what we expected."

That's not customer development. That's customer development theatre—going through the motions while learning nothing.

The Performance of Validation

Customer development theatre looks productive. Meetings happen. Notes accumulate. Interview counts grow. Founders can honestly say they've talked to customers.

But the actual learning is minimal because the process is designed to confirm, not discover.

Leading questions. "Don't you think it's frustrating when X happens?" prompts agreement. The customer hasn't validated your assumption; they've been led to it. Selective hearing. The founder remembers comments that support their vision and forgets comments that challenge it. The notes emphasize confirmation and minimize contradiction. Wrong customer selection. Interviewing friendly contacts, warm referrals, and people who already like you produces artificially positive feedback. Solution pitching. Instead of exploring the problem, the founder pitches the solution and asks for reactions. Polite people give polite feedback. Confirmation framing. "We're building X because of Y. Does that resonate?" invites agreement. The customer would need unusual conviction to say "no, that doesn't resonate."

Signs You're Performing

Interviews never change your plans. If fifty interviews haven't altered your product, positioning, or priorities, you're not listening. Real customer development reveals surprises. Every interview feels positive. Real problem discovery includes negative signals. If everyone seems enthusiastic, either you've found product-market fit (unlikely this early) or you're filtering for positivity. You're talking more than listening. In genuine discovery interviews, the customer talks 80%+ of the time. If you're explaining your product more than asking questions, you're pitching, not learning. Your assumptions haven't been challenged. Real customer development surfaces unexpected information. If you finish exactly as confident as you started, you haven't tested anything. The insights match your hopes. Suspiciously convenient findings—customers want exactly what you planned to build, at the price you planned to charge—suggest bias in the process.

Why Theatre Happens

Founders don't consciously decide to perform customer development. The theatre emerges from understandable motivations.

Confirmation bias. Humans seek information that confirms existing beliefs. Founders are humans with strong beliefs about their product. The bias is natural if not counteracted. Fear of invalidation. Genuine customer development might reveal the idea is flawed. That's terrifying. Theatre avoids this terror by ensuring the right answers emerge. Pressure to validate. Investors, advisors, and accelerators want to see customer validation. Founders feel pressure to produce the expected evidence—even if artificially. Skill gaps. Good customer interviews require skills many founders lack. Without training in unbiased questioning, founders default to leading conversations. Time pressure. Real discovery is slow and uncertain. Theatre is fast and predictable. Under deadline pressure, theatre is tempting.

What Real Discovery Looks Like

Genuine customer development differs fundamentally from theatre.

Open questions dominate. "Tell me about the last time you dealt with X" reveals more than "Don't you hate dealing with X?" Open questions discover; closed questions confirm. Surprises emerge regularly. If you're truly exploring, you encounter unexpected information. The customer uses words you wouldn't use. They describe workflows you didn't anticipate. They rank priorities differently than you expected. Some interviews are discouraging. Real problems aren't universal. Some customers won't have the problem. Some will have it but not care. These interviews feel like failures but are actually valuable data. Your hypotheses evolve. After every batch of interviews, your understanding should shift. You learn nuances, identify segments, and discover edge cases. Static understanding suggests static learning. You prove yourself wrong. The most valuable interview is one that invalidates an assumption. If you never invalidate anything, you're not testing anything.

The Mom Test Standard

Rob Fitzpatrick's "Mom Test" provides a useful framework: ask questions so good that even your mom couldn't lie to you.

Bad question: "Do you think this is a good idea?" (Anyone can say yes to be nice) Good question: "When was the last time you tried to solve this problem? What did you try?" (Reveals actual behavior, not hypothetical interest) Bad question: "Would you pay $50/month for this?" (Hypothetical willingness means nothing) Good question: "How much did you spend on solutions to this problem last year?" (Reveals actual budget behavior) Bad question: "What features would you want?" (Produces wish lists, not priorities) Good question: "What's the hardest part of your current workflow?" (Reveals real pain points)

The standard is whether the question produces useful information even from someone who wants to be nice to you.

Fixing Your Process

If you recognize theatre in your customer development, you can fix it.

Record and review. Record your interviews (with permission) and listen back. You'll hear leading questions you didn't notice in the moment. Script your questions. Write questions in advance. Review them for leading language. Have someone challenge them. Seek disconfirmation. Explicitly try to prove yourself wrong. "What would make this problem not worth solving?" "Why might this solution not work for you?" Interview skeptics. Don't just interview warm leads. Find people who seem unlikely to care and see if you can learn why. Separate interviewer and interpreter. Have someone else read your notes and identify themes. Your interpretation may be biased; theirs might be clearer. Track surprises. After each interview, write down what surprised you. If nothing surprised you, the interview probably didn't teach you much.

The Courage to Learn

Real customer development requires courage because it might reveal uncomfortable truths:

• The problem isn't as painful as you thought
• Customers won't pay what you hoped
• Your solution approach is wrong
• Your target market is wrong
• Your whole idea is flawed

Theatre avoids these revelations. Real development confronts them—because it's better to learn now than to build the wrong thing.

The Honest Count

Don't count interviews. Count learnings.

Fifty interviews that produced fifty confirmations of your existing beliefs taught you nothing. Five interviews that each challenged and refined your understanding taught you enormously.

The goal isn't to accumulate interviews. The goal is to accumulate understanding—real understanding that sometimes conflicts with what you wanted to believe.

The Test

After your next batch of customer interviews, ask yourself:

• What did I learn that surprised me?
• What assumption was challenged or invalidated?
• How has my understanding of the problem changed?
• What will I do differently based on these conversations?

If you can't answer these questions, you've performed customer development theatre. You've gone through the motions without learning.

Real customer development is uncomfortable because learning is uncomfortable. It requires admitting you didn't already know everything.

But companies built on real customer understanding have a chance at product-market fit. Companies built on theatre have only luck.

Stop performing. Start learning.