If you are the only researcher at your company, your problem is not skill — it is arithmetic. The median researcher completes about six studies every six months. At the most common staffing ratio of one researcher per five designers, that works out to roughly 2.4 studies per designer per year. No amount of craft closes a gap that size. The solo researchers who succeed in 2026 stop trying to personally run every study and instead redesign how research gets produced: triage ruthlessly, templatize the repeatable, delegate the shallow, and automate the interviews themselves.
This guide covers what the staffing data actually says, the four traps that consume a team of one, and a concrete operating model — including where AI-moderated interviews change the math.
What the staffing data actually says
The reference point most teams quote comes from Nielsen Norman Group. In a survey of 557 respondents (377 of whom answered the ratio questions), the most common researcher-to-designer ratio was one researcher per five or fewer designers, reported by 37%. Extended across the product organization, NN/g described the typical shape as 1:5:50 — one researcher, five designers, fifty developers. That ratio means researchers make up roughly 11% of all UX staff.
Two details from that study matter more than the headline. First, 54% reported at least one researcher per ten designers, and 8% reported one researcher per fifty or more designers — so the distribution has a long, painful tail. Second, and most usefully, NN/g found that a higher designer-to-developer ratio alone did not correlate with greater organizational maturity or business impact. Headcount is not the variable that determines whether research matters.
The second data point is that the team of one is becoming more common, not less. In the User Interviews State of User Research report — 485 qualified responses collected between 25 July and 9 August 2025 — the share of UX researchers working at companies with zero dedicated researchers was 19% in 2019, fell to 6% in 2022, and rose again to nearly 14% in 2025. The function contracted after the 2022–2024 correction, and a lot of research work landed on individuals.
The third data point explains what those individuals are actually up against. In Maze research covering 800+ researchers, designers and product managers, 63% named time and bandwidth as their biggest challenge, rising to 70% at enterprise technology and software firms. Not budget. Not stakeholder buy-in. Capacity.
The arithmetic nobody writes down
Put the three numbers together and the situation becomes concrete rather than emotional.
The User Interviews data reports median output over the previous six months as 2 mixed-method studies, 3 qualitative studies, and 1 quantitative study — six studies per half-year, or about one study per month for a working researcher.
| Ratio you support | Studies per year | Studies per person supported |
|---|---|---|
| 1 researcher : 5 designers | 12 | 2.4 per designer |
| 1 researcher : 10 designers | 12 | 1.2 per designer |
| 1 researcher : 5 designers : 50 engineers | 12 | 0.24 per engineer |
At the modal ratio, each designer you support receives about two and a half studies a year of your dedicated attention. Every other decision they make that year is made without research, or with research someone else ran, or with no research at all.
This is the honest framing of the team of one: you are not under-performing, and you are not going to fix a 5x demand gap by working faster. You are running a production system whose throughput is capped at roughly one study a month, against demand from an entire product organization. The fix is structural.
The four traps of the team of one
1. Becoming an order-taker. When demand exceeds capacity, the default triage rule becomes whoever asked most recently or most loudly. The result is a queue optimized for stakeholder anxiety rather than decision value.
2. Becoming the bottleneck. If every piece of customer contact must route through you, you have made yourself the rate limiter on organizational learning. Teams that cannot wait will simply proceed without evidence — and they will be right to.
3. Doing all the work at the same depth. A pricing decision worth seven figures and a copy change on a settings page both arrive as research requests. Treating them alike is the single most expensive habit in a one-person practice.
4. Never building the second-order assets. Templates, a question bank, a repository, and a decision log take time you do not have — and they are the only things that produce compounding returns. Skipping them guarantees year three feels exactly like year one.
The operating model: triage, templatize, delegate, automate
Triage on decision value, not requester
Ask two questions of every incoming request: what decision does this change? and what does being wrong cost? If the answer to the first is "none" — a surprisingly common outcome — the correct response is to decline and say why. If a request cannot name a decision, it is not a research request; it is a request for reassurance.
Publish your triage rule. A visible rule converts every individual "no" from a personality conflict into a policy outcome. This is the single highest-leverage change most solo researchers can make in a week.
Templatize the repeatable
Roughly 70% of the requests a team of one receives are variations on a handful of recurring shapes: why did this customer churn, why is this flow failing, what do people think of this concept, why do trials not convert. Each of those deserves exactly one canonical study design that you reuse.
Start from a user interview script template and a research report template rather than a blank page. Keep a running question bank so that writing a study becomes assembly rather than authorship. See the structured questions guide for how to standardize the measurable parts of every study.
Delegate the shallow, keep the deep
Democratization is not a threat to the team of one — it is the only way the team of one survives. The Maze data shows it is already happening: designers (70%) and product managers (42%) were running studies in 2025, and in the 2026 data product managers (39%), market researchers (35%) and marketers (23%) all run their own studies alongside dedicated researchers.
The question is whether that work is supported or feral. Maze found 61% of organizations provide non-researchers with access to tools and templates, 49% maintain research libraries, 46% offer structured training, 45% provide dedicated researcher support — and 13% provide no support at all. That last 13% is where bad research gets made and bad decisions follow.
Your job shifts from producing all research to setting the floor: which methods non-researchers may use unsupervised, which require your review, and which are yours alone. Our research democratization guide and the democratization playbook cover how to draw those lines.
| Work type | Who runs it | Your role |
|---|---|---|
| Concept checks, copy tests, quick reactions | PMs and designers, self-serve | Template owner, spot review |
| Churn, onboarding, win/loss interviews | AI-moderated, always-on | Design the guide, own the analysis |
| Pricing, positioning, strategy, segmentation | You | Everything |
| Compliance, accessibility, high-risk populations | You | Everything, no exceptions |
Automate the interviews, not the thinking
The step that has actually changed since 2024 is moderation. Scheduling, running and transcribing interviews is the part of the pipeline that consumes a solo researcher and produces the least differentiated value — and it is now automatable.
This is also where AI adoption has concentrated. Maze reports 69% now use AI in at least some research projects, with data analysis (76%), transcription (57%), study planning and drafting (56%), generating research questions (55%) and synthesis and reporting (47%) as the leading applications.
Automating moderation does not mean automating judgment. Deciding what to study, which trade-off matters, and what the findings mean for the roadmap remains entirely yours — and is the part of the job that justifies the headcount.
Where Koji fits for a team of one
Koji is built for exactly this constraint: a small number of people who need research output far beyond their personal hours.
- AI-moderated voice interviews run without you in the room. Launch a study on Monday, have 40 conversations completed by Wednesday. You are not scheduling, not attending, and not transcribing. See how AI research agents work and our comparison of AI versus human moderators for where each is appropriate.
- Six structured question types — open_ended, scale, single_choice, multiple_choice, ranking, and yes_no — mean one study returns both the quotes and the numbers. You stop running a qualitative study and a separate survey to answer one question. Details in the structured questions guide, scale questions and open-ended questions.
- Automatic thematic analysis turns 40 transcripts into themes with supporting quotes, removing the multi-day synthesis block that usually forces a team of one to run fewer, larger studies.
- One-click reports give stakeholders something to read without you building a deck for every request.
- No moderator bias and no interviewer fatigue. Human moderators degrade after four to six interviews in a day; the fortieth Koji interview is conducted exactly like the first.
- Customizable AI consultants let you encode your own probing style once and apply it across every study.
- No per-seat pricing. A team of one is not penalized for inviting stakeholders to read results — see per-seat versus usage-based pricing.
The practical effect on the arithmetic above: the constraint moves off your calendar. Studies stop being rationed by your available hours and start being rationed by what is actually worth knowing — which is the correct constraint.
A 90-day plan for a new team of one
| Days | Focus | Concrete output |
|---|---|---|
| 1–30 | Map demand and stop the bleeding | Written triage rule, inventory of every open request, one decision log |
| 31–60 | Build the reusable layer | Three canonical study templates, a question bank, a shared repository |
| 61–90 | Shift the ratio | Two always-on AI-moderated studies running continuously; non-researcher self-serve tier defined |
By day 90 the goal is not more studies. It is that the studies which happen are the ones that change decisions, and that routine questions no longer require your calendar.
Prove the impact before someone asks
The CMX community data makes a point that transfers directly: teams whose data was connected to a system of record were over twice as likely to rate their impact as extremely successful. The lesson is not about tooling for its own sake — it is that impact you cannot evidence is impact you will be asked to justify.
Keep a decision log from week one: the decision, the evidence, the date, and what changed. When budget season arrives, that log is the argument. Our research ROI guide covers how to frame it, and UX researcher salary and team cost benchmarks gives you the comparison figures.
Frequently Asked Questions
What is a research team of one?
A research team of one is a single dedicated researcher supporting an entire product organization, with no other research staff. It is common: User Interviews found that nearly 14% of UX researchers in 2025 worked at companies with zero dedicated research headcount besides themselves, up from 6% in 2022.
How many designers should one researcher support?
Nielsen Norman Group found the most common ratio is one researcher per five or fewer designers (37% of respondents), often described as 1:5:50 across researchers, designers and developers. However, 8% of respondents reported one researcher per fifty or more designers, so the tail is long.
How many studies can a solo researcher realistically run?
Median reported output is about six studies per six months — roughly one per month, split across mixed-method, qualitative and quantitative work. At a 1:5 ratio that is about 2.4 studies per designer per year, which is why triage and automation matter more than working faster.
Should a team of one let non-researchers run studies?
Yes, with guardrails. Democratization is already happening — 70% of designers and 42% of product managers were running studies in 2025 — so the real choice is whether it is supported or unsupervised. Define which methods are self-serve, which need your review, and which are yours alone.
Does AI moderation replace a solo researcher?
No. It replaces scheduling, moderating and transcribing — the highest-volume, lowest-differentiation parts of the job. Choosing what to study, interpreting trade-offs and influencing the roadmap still require a researcher, and those are the activities that justify the role.
How do I prove my impact as the only researcher?
Keep a decision log recording each decision, the evidence behind it, and what changed as a result. Evidence you can point to is far more persuasive than study counts, and teams that connect research data to their systems of record are measurably more confident about their impact.
Run more research than your calendar allows
If you are a team of one, the constraint is your hours — not your judgment. Koji removes the moderation and synthesis bottleneck so the studies that matter actually happen.
Start free with 10 credits — no credit card, no research expertise required. Design a study in minutes, launch AI-moderated voice interviews, and get themes and quotes back in hours rather than weeks.
