How to Scale UX Research Without Scaling Your Research Team

One of the most common questions I get from product teams is: "How do we do more research without slowing everything down?"

The answer isn't to hire more researchers. It's to build a system that makes good research instincts repeatable across your whole team. Designers, PMs, engineers — everyone has research moments. The question is whether those moments are structured or accidental.

What enabling non-researchers actually looks like

At USAA, I built an embedded weekly research training program for designers and PMs. The goal wasn't to turn them into researchers — it was to give them enough structure that their informal observations became useful data.

We cut research turnaround time significantly. Not because we rushed things — but because more people could run the early-stage work competently, and the researchers could focus on the high-complexity synthesis.

The three things every team needs to scale research

First: a shared language. If your team can't agree on what a "finding" is versus an "observation" versus an "assumption," you'll spend half your time in definitional debates instead of making decisions.

Second: lightweight templates. Not 40-page research plans — a one-pager that forces clarity on what you're trying to learn, how you'll learn it, and what a good answer looks like.

Third: a synthesis habit. The findings don't matter if they don't get used. Building a lightweight synthesis process — even just a structured debrief within 24 hours of any research session — dramatically increases the chance that insights actually influence decisions.

If you're leading a team and want to build this kind of research culture, I'd love to talk about what that looks like for your org.