In that time I’ve been exposed to countless research teams and approaches. One key challenge that recurs again and again is how to pace research for maximum impact.
Finding the right research pace is a balancing act. Go too fast and you risk producing shallow, unactionable insights. Go too slow and by the time your research is ready, the team has moved on. So how do you find the sweet spot?
When research is rushed, it often starts with a vague, last-minute request, something scribbled on the back of a napkin. There is no time to ask clarifying questions, so you default to the quickest possible method, such as virtual interviews or unmoderated usability tests. A rough discussion guide is thrown together, recruitment is fast and loose, and analysis consists of a quick scan of notes and a few Post-its on Miro.
When it is time to present insights, the findings feel unclear. Nothing groundbreaking emerges, the story lacks focus, and recommendations are too vague to drive action. The team nods along but does not act on anything. Before long, another napkin request lands on your desk and the cycle repeats.
From my experience working as a researcher in this environment is a recipe for burn out. The unrelenting pace and lack of tangible impact of your work quickly takes its toll. I’ve also seen it lead to the exec teams losing faith in the value of research altogether, and no doubt if they’re ploughing all of this money and resource into something that is not driving decision making or innovation.
On the other hand, when research is too slow, it becomes an over-engineered process. A product manager submits a research request, which is discussed in multiple meetings before being assigned. A workshop is held to refine objectives, and a robust mixed-methods study is designed. A three-week diary study, in-depth interviews, and a survey seem like the best approach. Recruitment takes forever due to ultra-specific criteria.
Months later, after thorough analysis involving full transcripts, detailed tagging, and thematic workshops, a polished 100-page report is finally shared. By then, the product team has moved on. The findings feel outdated, enthusiasm has waned, and the impact is lost.
From my experience, this approach ultimately leads to hefty reports gathering dust in shared drives and companies viewing research as a blocker instead of an essential stage in their pacey iterative design process. Plus it can be incredibly demotivating to see months of your hard work have such little engagement or impact.
The ideal research pace varies depending on the context, but these key principles help strike the right balance:
{{research-plan-template="/about/components"}}
Balancing research speed and depth is an art. Move too fast and your insights lack impact. Move too slow and they lose relevance. The key is finding the Goldilocks zone, just the right pace to deliver meaningful insights when they are needed most.