Ship-to-Learn Research Allocation
Reserve scarce user research for high-uncertainty, high-leverage problems; ship to learn everywhere else
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 3
- Confidence
- 90%
A decision rule for when a product team should invest in user research versus just shipping and measuring. Winters argues research is a scarce resource that most teams overspend, when frequently the fastest way to learn is to ship. Research is reserved only for problems that are both highly uncertain and high-leverage.
Origin
Developed by Casey Winters while leading product at Eventbrite, in reaction to a 'zero interest rate phenomenon' pattern he saw in PMs who over-researched before acting.
Core principles
- 01User research is a scarce resource, not a default step
- 02Many times the fastest way to learn is to ship
- 03Only spend research where uncertainty is extreme AND leverage is high
- 04For low-stakes problems, copy what leading companies already validated
How to run it
- 1
Classify the problem's uncertainty and leverage
Ask two questions: is this a big problem we don't understand well enough, or a well-understood problem where we're unsure our solution will hit the mark? Only if the answer is yes to extreme uncertainty plus high leverage does research qualify.
Pro tip Winters' two research triggers: 'we have a really big problem, we don't understand it well enough' OR 'we understand it well but we're just not sure if our solution is going to hit the mark.'
- 2
For low-uncertainty problems, copy proven patterns
If you're redesigning something well-trodden like a login page, don't burn research. Look at what leading companies (FANG, top unicorns) did — they likely did a good job, and your customers already use those products so they're familiar with the pattern.
Watch out Don't just collect a list of what other companies did — analyze WHY each chose their option and which is most applicable to you.
- 3
Match approach to customer sophistication and scale
High-scale consumer products: bias to shipping, run experiments, get data easily, and only research when impact is confusing. Enterprise: talk directly to sophisticated customers and sales — the research is the sales conversation. Middle (SMB, prosumer): be nuanced and pick research spots deliberately.
Pro tip Winters focused Eventbrite's research on the B2B side 'where the problems seem big but not well defined enough or the problem's well defined but we just really don't feel like we have the right solution yet.'
In the wild
Winters told his team that redesigning the Eventbrite login page did not merit user research — 'just go see what FANG and the top unicorns did, they probably did a good job.'
→ Research resource preserved for genuinely uncertain, high-leverage B2B problems instead of well-solved UI patterns.
Winters notes the best researchers he worked with would tell him 'we don't need to research on this, we have enough information, we have other things we should be' doing.
→ Signals a healthy research culture where the scarce resource is aimed only where it changes decisions.
Common mistakes
Treating research as a mandatory first step
PMs who insist 'I can't even begin to come up with solutions until I see all the data and talk to customers' waste a scarce resource and slow the team; often the fastest way to learn is to ship.
Copying competitors without analysis
Producing a list of what other companies did with no reasoning about why they chose their options or what's applicable to your context adds no real learning.
Is it for you?
Best for
Product managers and product leaders at startups or public companies with finite research/design resources and pressure to move fast
Not ideal for
Pure enterprise products where every six-figure customer is sophisticated and research IS the direct sales conversation, or genuinely novel high-stakes bets
From the transcript
“user research is a scarce resource we have to reserve it for the areas that have extreme uncertainty and high leverage”
“many times the fastest way to learn is to ship”
“if you're redesigning the login page for Eventbrite you don't need to use that resource to learn what to do just go see what Fang…”
“where it's a high leverage area which means you have a really big problem uh we don't we don't understand it well enough or we…”
From the episode
Thinking beyond frameworks
Casey Winters (Pinterest, Eventbrite, Airbnb, Tinder, Canva,