The 1:5:50 Problem
It's everywhere
A lot of my friends from my Ph.D. days who didn’t go the professor route, ended up as UX researchers and research managers. Whenever I catch up with them and ask them how things are going at work, I usually hear some variation of “we’re a bottleneck and we hate that.”
There’s a ratio that quietly shapes every product decision in every tech company, and most people have never thought about it.
1:5:50.
One researcher. Five designers. Fifty developers. That’s the typical ratio in product organizations, according to Kate Kaplan at Nielsen Norman Group.
One person is responsible for understanding the humans you’re building for. Fifty people are responsible for turning that understanding into software.
The Math Doesn’t Work
Let’s think about what this means in practice.
Your researcher has maybe 40 hours a week. But 25% of that — roughly 10 hours — goes to support work: answering ad-hoc questions, running quick studies for teams that need data, democratizing research access across the org (Source: User Interviews, State of Research Strategy 2025).
That leaves 30 hours of actual research capacity. For 50 developers working on multiple features, across multiple sprints, shipping continuously.
It’s not physically possible for one person to generate the user understanding that 50 builders need. The math doesn’t work. It never has.
The Invisible Cost
When research can’t keep up with development — which is structurally guaranteed by this ratio — teams make decisions without it. Features ship based on assumptions. Product strategy gets informed by stakeholder opinions instead of user behavior.
This isn’t a process failure. It’s a design failure. The organizational structure itself creates the gap.
And the cost is enormous. When 42% of startups fail due to lack of product-market fit (Source: WithIntent), the research bottleneck isn’t an HR problem — it’s an existential risk.
Why Hiring Doesn’t Fix It
The obvious response is “hire more researchers.” But that rarely happens at the rate needed. Research headcount has been flat or declining in many organizations, while development teams continue to grow.
Even in the best case, going from 1:50 to 2:50 doesn’t solve the structural problem. You’ve gone from impossible to merely unrealistic.
What Actually Fixes It
The solution isn’t (just) more people. It’s different infrastructure.
Research needs to scale the way engineering scaled — through tooling and systems that multiply the output of each person, not through linear headcount growth.
That’s the core thesis behind Seena. AI-powered research infrastructure that lets one researcher have the impact of five. That connects real user signals to product decisions automatically. That makes the 1:50 ratio survivable.
Because the ratio isn’t changing. But what one researcher can accomplish with the right tools — that can change everything.
Join the waitlist at SeenaLabs.io
—Ax