Dec 1, 2024 · 1h 29m · lennys-podcast
Identify your bullseye customer in one day | Michael Margolis (UX Research Partner at GV)
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In this masterclass, GV UX Research Partner Michael Margolis presents his 'five and three in one' sprint framework to help founders identify their bullseye customer and validate product concepts in a single day. Through step-by-step tactical guidance, recruitment strategies, and bias mitigation techniques, he demonstrates how to compress months of discovery into rapid, cross-functional team alignment.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Lenny holds 25.4% of the talking time here. How this is scored →
Lenny as informed peer 4.4 Guest teaching 4.5 Guest disagreement 1.1 Lenny pushing back 0.1
speaking balance: gold is Lenny, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 51:05 Rejecting standard startup ICPs as too broad
When Lenny cites famous early ICPs from Gong, Linear, and Gusto as examples of hyper-narrow targeting, Michael pushes back that for a research sprint those descriptions remain far too broad and vague.
Hardest push from Lenny ▶ 59:06 Pushing back on AI-generated functional prototypesLenny suggests product teams might soon generate functional prototypes via AI rather than static mockups, but Michael pushes back that building functional apps distracts from testing core positioning.
Biggest teaching moment ▶ 52:07 Differentiating selling mode from humble inquiryMichael educates Lenny and the audience on why founders fail in interviews by remaining in pitch mode rather than practicing vulnerable, humble inquiry.
Lenny holds their own ▶ 50:05 Lenny citing early ICP profiles of top B2B SaaS companiesLenny demonstrates deep product knowledge by reading specific historical ICP parameters used during the early days of Gong, Linear, and Gusto.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Lenny as informed peer | Guest teaching | Guest disagreement | Lenny pushing back | Why |
|---|---|---|---|---|---|---|
| Michael Margolis's 30-Year Career and Fast Research Roots | 3 | 3 | 1 | 0 | Lenny invites Michael to detail his 30-year journey across ethnographic consulting, Walmart, Google, and GV. Michael provides an expansive breakdown of how rapid UX research evolved into one-day sprints. | |
| Defining the Bullseye Customer Versus Traditional ICP | 4 | 4 | 1 | 0 | Lenny asks Michael to define the bullseye customer and clarify how it differs from traditional ICP. Michael explains that a bullseye customer is a tightly focused subset most likely to adopt immediately, which aligns product roadmaps. | |
| High-Level Architecture of the One-Day Sprint | 4 | 5 | 1 | 0 | Michael outlines the high-level sprint architecture: five customer interviews and three prototype variations tested across a single day. Lenny synthesizes the core principles and asks when teams should run the sprint. | |
| Sprint Step 1: Aligning on Critical Unresolved Questions | 5 | 5 | 1 | 0 | Lenny brings in Andy Johns' concept of making customer definitions 'comically narrow.' Michael shares a detailed case study of specialty prescription delivery to illustrate how narrowing down to refrigerated medication uncovered true customer pain. | |
| Categorizing Attributes: Inclusion, Exclusion, and Triggers | 5 | 4 | 1 | 0 | Michael breaks down criteria into inclusion, exclusion, and timing triggers like marriage or childbirth. Lenny reads directly from Michael's book checklist to review specific demographic and behavioral attributes. | |
| Sponsor Message: Enterpret Customer Feedback Intelligence | 6 | 6 | 2 | 1 | Lenny presents the early ICP definitions of Gong, Linear, and Gusto to demonstrate narrow targeting. Michael counters that research recruiting profiles need to be substantially narrower than commercial ICPs and explains Ed Schein's humble inquiry framework. | |
| Sprint Step 4: Crafting Three Distinct Prototype Recipes | 4 | 4 | 1 | 0 | Michael explains how to construct three flat prototype recipes highlighting contrasting value propositions. Lenny asks whether AI tools should be used for interactive functional prototypes, and Michael cautions against over-building. | |
| Sprint Step 5: Conducting Two-Part Discovery and Concept Interviews | 4 | 5 | 1 | 0 | Michael details the two-part interview structure combining past behavior discovery with prototype shopping. Lenny reads warm-up scripts from the text, and Michael emphasizes smiling and adopting an open listener persona. | |
| Sprint Step 6: Watch Parties, Structured Debriefs, and Predictions | 4 | 5 | 1 | 0 | Michael describes the watch party protocol, manual note-taking, and capturing team predictions beforehand to eliminate hindsight bias. Lenny affirms the recurring shock teams feel when direct customer feedback overturns internal assumptions. | |
| Common Pitfalls, Blind Spots, and the Curse of Knowledge | 5 | 4 | 1 | 0 | Lenny connects Linear's waitlist survey to screener questionnaires, and Michael emphasizes prioritizing past demonstrated behavior over hypothetical user intent. Michael closes by exploring how these sprint methodologies apply to clinical trial recruitment in biotech. |
Statements from this episode (18)
Margolis: Successful product building requires starting with a hyper-focused initial customer subset
“Every ambitious founder wants to build a product for everybody and we're investors. So at GV, we want them to be successful and to have these huge markets. But it doesn't start there. So to build successfully, usually you have to be much more focused and much …”
Margolis: Batching customer interviews in one day makes patterns obvious
“If you do them in a clump like that, then the patterns are just much more obvious. You have to, at the end of the day, it's just really clear what were the big takeaways.”
Margolis: Five qualitative customer interviews reach data saturation
“And that idea of just doing five of them
You hit what's called data saturation. And so this is the thing in qualitative research where the kind of the common version of this is everybody after four or five is like, oh, for God's sakes, please don't let me sit …”
Margolis: Testing multiple prototypes stops teams overcommitting to one idea
“The other big benefit of having multiple prototypes is it helps teams avoid getting too wed to one specific idea. And so you can get a little over committed. There's a risk that you get over committed to one idea.
You're polishing that you're working on it. Yo…”
Margolis has not written a user research report in 10 years
“I don't write a report. I haven't written a report in, I don't know, 10 years because we've at the end, when we capture those big takeaways, that's the team has captured it, right?”
Margolis: Bullseye customer definitions must be comically narrow to reduce variables
“Comically narrow is exactly what it is. And there are times that teams will just be like, Oh, for God's sakes, Margolis, like, just like, this is too much. The reason that I do that is I'm pushing them to identify a person who they all would agree. This person…”
Margolis: Early customer research must exclude industry experts and domain insiders
“Another typical exclusion Criteria is I don't want somebody who knows too much. So your core bullseye customer, I want somebody who's pretty typical. So in this case, like if I were to find out that somebody was a pharmacist or worked in healthcare, I'm like, …”
Margolis: Bullseye customer definitions require inclusion, exclusion, and trigger criteria
“The way I think about it is kind of in these three groups. So there are inclusion criteria, there are exclusion criteria, and then there are, what we found is very important are triggers.”
Margolis: Screeners must avoid telegraphing desired answers to prevent participant bias
“And so part of the trick there is to write a questionnaire in a way that I'm not telegraphing the right answers. And so that I kind of am in the control seat so I can pick out and identify the people.”
Margolis: User research requires founders adopt humble inquiry over sales pitching
“Asking questions and being vulnerable and giving the person you're asking the higher status is a difficult thing to do as a founder when you're selling. Right? Because you don't want to be vulnerable and express that you don't know or, and people are always, I…”
Margolis: Low incentives like $20 gift cards cause research no-shows
“You have to make sure they show up, make sure you're compensating them sufficiently. This is something where I'm not giving 20 dollar Starbucks cards because somebody's gonna blow you off. Like when I have those five sessions and the whole team queued up to wa…”
Margolis: Founders must test competitor products with users, not just analyze them
“If you haven't studied your competitor's product and not just gone through it, but like seeing how people respond to them, you're just missing something, right?”
Margolis: Prototype typos undermine credibility because testers fixate on errors
“People get stuck on errors and then it undermines the validity and the credibility of the prototype. So proofread it and make sure. Cause otherwise people are like, oh, that's not right.”
Margolis: Teams should take manual notes instead of using AI during research
“We have people manually taking notes and not using AI to take notes. The reason for this is what we found is we want people to lean in to this experience. We want you to focus and engage and pay a lot of attention. And if you know somebody else is taking notes…”
Margolis: Teams must record specific predictions before research to defeat hindsight bias
“We do this thing before the watch party where we get everybody to predict what they think they're going to learn. And this is really valuable for a bunch of different reasons. So it's a way to capture a snapshot before we do the interviews of like, what do you…”
Margolis: Deep expertise leads founders to overestimate customer knowledge and willingness to pay
“And when somebody has deep expertise, it's very difficult to imagine that other people don't know what you know. It's very hard to kind of put yourself in their shoes, right? And you just think, well, doesn't everybody know this? Or maybe even, you know, yeah,…”
Linear used its early launch waitlist as a customer screener survey
“With linear, something smart they did is they had a wait list.
When they first launched and the waitlist was their questionnaire.
Would you, what do you, what the, what do you call it?
The screener.
So basically the waitlist was a screener survey.
It's like, w…”