The test you skip is the one that costs you the most
Product teams are fond of saying they don't have time to test. What they rarely acknowledge is how much time they lose building the wrong thing.
This is the quiet contradiction at the heart of modern product development. Sprints move fast, design decisions get made, engineers ship features—and somewhere downstream, it turns out users wanted something different. The fix is expensive. The delay is embarrassing. And it was preventable.
Research isn't a gate; it's a gear
The instinct to treat user research as a checkpoint—something that happens before launch, or after a prototype is polished—is understandable. It feels safer to test something finished. But that instinct is also what makes testing feel slow.
Megan Millians, a UX researcher who specializes in embedding research into fast-moving teams, argues that getting involved earlier is exactly what dissolves the friction. "The key to moving research left is to show people that you're going to help them achieve their goals rather than being a blocker," she said. "There's just this tendency for people to think that research is this big, long, arduous thing."
It doesn't have to be. A quick assumption test at the start of a sprint can surface misalignments before they calcify into shipping decisions.
Start with a shovel, not a backhoe
One of the most durable misconceptions about user testing is that it requires a fully realized prototype. In reality, low-fidelity concepts—rough wireframes, simple flows, basic paper sketches—often generate sharper, more honest feedback precisely because users aren't distracted by polish.
Megan offers an analogy worth keeping: "You think about a research problem as this big, monstrous thing, like a big pile of dirt, and you can use a backhoe to pick it up and move it. Or you can use a shovel. It'll get you to the same place." The shovel, she explains, lets you attack one small problem at a time, pivot quickly when something doesn't fit, and still arrive at the same destination.
This is what continuous user research looks like in practice—not a formal study every quarter, but small, well-aimed questions answered often.
Make testing a team sport
The shift from episodic to continuous testing isn't just a process change. It's a culture change.
Jessica Johnston, Senior Learning Experience Designer at UserTesting, frames it this way: collaboration among product development team members has to be built in from the start of any initiative, not bolted on before release. When designers, engineers, and researchers share learnings early, everyone rows in the same direction. Designers understand what problem they're solving. Engineers understand how best to solve it. And the researcher isn't scrambling to answer urgent questions—they're already one sprint ahead.
Jessica suggests embedding research activities directly inside product development tools like Jira. "Within every sprint, ensure that the next one to two sprints' questions are addressed," she said. The goal is to make sure product decisions never hit a research bottleneck.
For teams that feel too busy to test, the answer isn't to find more time. It's to integrate testing into the time that already exists.
ON-DEMAND WEBINAR
Designing the Insight System of Tomorrow: How UXR Leaders Can Shape the Role of Research in the Age of AI
The cost of skipping
The fastest teams aren't the ones who skip testing. They're the ones who've learned to run faster with it.
As Megan puts it: "Testing low-fidelity concepts takes less time, and putting those in front of customers, you get really good feedback."
That's the real unlock—not adding research to the sprint, but letting research be the sprint.
Resources and further reading
- WEBINAR: Continuous discovery: transform your product development—This on-demand panel webinar featuring industry professionals sharing how they've implemented continuous discovery, integrated insights into workflows, and embedded research earlier in the product development process. Directly mirrors the episode's core argument about shifting research left and making testing a team habit.
- GUIDE: Adding user tests to your agile process—This guide is for teams looking to embed user testing into sprint-based workflows. Covers low-fidelity prototype testing, research backlogs, and how to structure design sprints in parallel with development—closely aligned with Megan's advice on thinking smaller and testing early.
- PODCAST: Build products customers love with continuous discovery—In this Insights Unlocked episode with Teresa Torres, author of Continuous Discovery Habits, she explores how to shift research left, reduce the cost of rework, and build a habit of frequent, lightweight customer feedback. A strong companion to the episode's "make testing a team sport" theme.
- BLOG: How to integrate continuous user testing into your product development workflow—This blog post covers how teams can adopt continuous user testing as a standard part of their development process, validate direction quickly, and build confidence in product decisions—directly reinforcing the blog post's argument that the fastest teams test more, not less.
Related UserTesting knowledge base articles
- AI-powered test creation — step-by-step guidance on using AI to generate a complete test plan from a research goal, including methodology, tasks, and questions aligned with UX research best practices. Directly supports the script's mention of the AI-powered test creation feature.
- Choose templates for your design and development process — guidance on selecting the right test template at each stage of the design and development process, including concept validation, prototype evaluation, and feature prioritization. Ties directly to Jessica's recommendation to use templates to answer a single pressing question fast.
- Test plan best practices — a checklist of tips for writing effective test plans, including guidance on scope and sample size that reinforces the episode's "think smaller" philosophy.
