“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about research that gets done, presented, and forgotten — the insight graveyard problem in two weeks. dovetail had absorbed it. The tool had graduated from experiment to infrastructure without them noticing.”
When I'm a pm is about to spec a feature, I want to make past research findable so it's used rather than repeated, so I can turn raw interview data into structured insights that survive beyond the project that produced them.
A UX researcher or research ops manager at a company with a growing research practice. They've conducted enough studies that the insights are now a problem: they exist in documents, recordings, sticky notes, and people's memories. Dovetail is where they're consolidating that. They tag, they theme, they surface insights in a way that teams can find without having to ask a researcher. They believe the research repository is the infrastructure of a research-driven company. They're building it while also running new studies. It is a lot.
To reach the point where make past research findable so it's used rather than repeated happens through dovetail as a matter of routine — not heroic effort. Their deeper aim: turn raw interview data into structured insights that survive beyond the project that produced them.
dovetail becomes invisible infrastructure. Make past research findable so it's used rather than repeated works without intervention. The old problem — research that gets done, presented, and forgotten — the insight graveyard problem — is a memory, not a daily fight. AI-assisted tagging that suggests themes from transcript content reduces the.
A PM is about to spec a feature. The researcher knows there's relevant user feedback from a study six months ago — something about this exact pain point from a different angle. They're in Dovetail searching for it. They find it in three minutes. They share the insight link in the PM's Slack thread with a note. The PM incorporates it into the spec. This is the moment the repository was built for. It happens about twice a week. The researcher is still not sure if that's enough to justify what it took to build.
Conducts 2–6 research studies per month — interviews, usability tests, surveys. Uses Dovetail for analysis, tagging, and insight storage. Imports recordings from Zoom or directly records in Dovetail. Tags data collaboratively with a research team of 1–3 people. Has a tagging taxonomy they've revised once after the original one didn't reflect how PMs searched. Shares insights via Dovetail's published view with product and design teams. Has a Slack integration that surfaces new insights to a #research channel. Tracks "insights reused" as an informal metric to justify the repository investment.
The proof is behavioral: make past research findable so it's used rather than repeated happens without reminders. They've customized dovetail beyond the defaults — templates, views, integrations — and their usage is deepening, not plateauing. When new team members join, they hand them their setup as the starting point.
The trigger is specific: tagging taxonomies that make sense to researchers and make no sense to the product teams, combined with a high-stakes deadline. dovetail fails them at exactly the wrong moment. That evening, they're reading comparison posts. What makes it irreversible: they fundamentally believe a research finding that can't be found might as well not exist, and dovetail just proved it doesn't share that belief.
Pairs with `ux-researcher` interviewer persona for the full qualitative research lifecycle from interview to repository. Contrast with `pendo-primary-user` for the qualitative vs. quantitative product insights workflow. Use with `figma-primary-user` for the research-to-design handoff and evidence-based design decision workflow.