<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Dovetail &#8211; iAIFeed</title>
	<atom:link href="https://www.iaifeed.com/tag/dovetail/feed" rel="self" type="application/rss+xml" />
	<link>https://www.iaifeed.com</link>
	<description>iAIFeed</description>
	<lastBuildDate>Sat, 19 Sep 2026 12:51:23 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.1</generator>

<image>
	<url>https://www.iaifeed.com/wp-content/uploads/2026/07/cropped-iaifeed1-80x80.png</url>
	<title>Dovetail &#8211; iAIFeed</title>
	<link>https://www.iaifeed.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>How to Run a Continuous Research Practice in Dovetail</title>
		<link>https://www.iaifeed.com/how-to-run-a-continuous-research-practice-in-dovetail</link>
					<comments>https://www.iaifeed.com/how-to-run-a-continuous-research-practice-in-dovetail#respond</comments>
		
		<dc:creator><![CDATA[iamltlb]]></dc:creator>
		<pubDate>Sat, 19 Sep 2026 12:51:23 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Dovetail]]></category>
		<guid isPermaLink="false">https://www.iaifeed.com/how-to-run-a-continuous-research-practice-in-dovetail</guid>

					<description><![CDATA[A research repo only earns its cost if insights stay current. This guide sets a rolling study cadence, shared tag taxonomy and a monthly digest so Dovetail feeds decisions.]]></description>
										<content:encoded><![CDATA[<p><strong>A continuous research practice means you run a small study every two weeks, tag into a shared taxonomy, and publish a monthly evidence digest instead of a one-off report.</strong> Dovetail stores the evidence; the cadence is what keeps it alive.</p>
<p>Most teams buy <a href="https://www.iaifeed.com/ai-tool/dovetail">Dovetail</a>, load one big study, and let the repo go stale within a quarter. This is how to avoid that.</p>
<h2>Why do research repositories go stale?</h2>
<p>Because the work is episodic. A study happens, a report is written, everyone moves on, and six months later the evidence is out of date but nobody removes it. Search then returns confident quotes about a product version that no longer exists.</p>
<p>The fix is a rolling cadence, not a bigger study. Four interviews every two weeks beats twenty interviews once a year, because the insights stay attached to the current product.</p>
<h2>How do you keep tags consistent across researchers?</h2>
<p>Lock the taxonomy to a small, reviewed set. Practical rules:</p>
<ul>
<li>One owner maintains the tag list and approves new tags.</li>
<li>Cap it — over about forty tags, people stop browsing and start inventing.</li>
<li>Use a fixed prefix per theme, like <code>onboard:</code> or <code>billing:</code>, so search groups cleanly.</li>
<li>Review unused tags quarterly and merge duplicates.</li>
</ul>
<p>Naming discipline sounds fussy until you search for pricing feedback and find it split across five tags.</p>
<h2>What does a monthly digest look like?</h2>
<p>One page, three sections, tied to decisions:</p>
<table>
<tr>
<th>Section</th>
<th>Content</th>
</tr>
<tr>
<td>New evidence</td>
<td>Top three insights from this month&#8217;s sessions, each with a clip link</td>
</tr>
<tr>
<td>Confirmation or conflict</td>
<td>What supports or contradicts last month&#8217;s findings</td>
</tr>
<tr>
<td>Open questions</td>
<td>What the next study should test</td>
</tr>
</table>
<p>Send it to the people who make roadmap calls, not just to the design team. A digest nobody with authority reads changes nothing.</p>
<h2>How do you connect insights to decisions?</h2>
<p>Attach every insight to a ticket or roadmap item, and record when it was last validated. An insight older than two product releases should be re-validated before anyone quotes it.</p>
<p>Keep a short &#8220;stale evidence&#8221; list and revisit it monthly. It is the cheapest way to stop the repo from quietly becoming fiction.</p>
<h2>When should you drop the cadence?</h2>
<p>During a discovery sprint you may go weekly; in a maintenance quarter, monthly is plenty. What you should not do is pause and restart — a three-month gap means re-learning context and re-reading old transcripts, which is where the cost of the tool stops paying back.</p>
<h2>Quick Summary</h2>
<ul>
<li>Run four interviews every two weeks rather than one annual mega-study.</li>
<li>Assign one tag owner and cap the taxonomy near forty tags.</li>
<li>Publish a one-page monthly digest to decision-makers.</li>
<li>Link insights to tickets and re-validate anything older than two releases.</li>
<li>Adjust cadence to the quarter, but never pause for months.</li>
</ul>
]]></content:encoded>
					
					<wfw:commentRss>https://www.iaifeed.com/how-to-run-a-continuous-research-practice-in-dovetail/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>How to Analyze User Research Interviews with Dovetail</title>
		<link>https://www.iaifeed.com/how-to-analyze-user-research-interviews-with-dovetail</link>
					<comments>https://www.iaifeed.com/how-to-analyze-user-research-interviews-with-dovetail#respond</comments>
		
		<dc:creator><![CDATA[iamltlb]]></dc:creator>
		<pubDate>Sat, 19 Sep 2026 12:51:09 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Dovetail]]></category>
		<guid isPermaLink="false">https://www.iaifeed.com/how-to-analyze-user-research-interviews-with-dovetail</guid>

					<description><![CDATA[Dovetail turns interview recordings and survey responses into tagged, searchable insights. Here is how to set up a project, tag a first transcript and where AI tagging still misses.]]></description>
										<content:encoded><![CDATA[<p><strong>Dovetail is a research repository: you upload interviews, surveys and notes, and it transcribes, tags and lets you search everything for evidence.</strong> The point is to stop losing findings in scattered docs and to quote real users in decisions.</p>
<p>It is for product and UX teams running continuous research, not for a one-off survey. If you do two interviews a year, a spreadsheet is cheaper.</p>
<h2>How do you set up a project?</h2>
<ol>
<li>Create a project and define your tags — the themes you expect, like &#8220;onboarding friction&#8221; or &#8220;pricing confusion&#8221;.</li>
<li>Upload your source material: audio, video, transcripts or raw text.</li>
<li>Let it transcribe, or paste existing transcripts.</li>
<li>Tag highlights and build an insight from the patterns.</li>
</ol>
<p>Define tags before uploading. Building the taxonomy as you go produces duplicates — &#8220;confusing onboarding&#8221; and &#8220;onboarding: confusing&#8221; as separate tags — and search then returns half your evidence.</p>
<h2>How do AI tags compare to manual ones?</h2>
<p>Dovetail&#8217;s AI will auto-suggest tags and summarize transcripts, and it is a decent first pass. It is also flat. It catches the literal topic — someone mentions &#8220;pricing&#8221; — but misses the stance, whether the user found it expensive, fair or irrelevant.</p>
<p>Careful human tagging still wins on the two things that matter: intent and contradiction. Use AI to tag the easy volume, then read the transcripts yourself for the negative signals. The most valuable finding in research is usually the one that surprises you, and that is exactly what auto-tagging smooths away.</p>
<h2>Is Dovetail free?</h2>
<p>There is a free plan for an individual or a very small team with limited storage and features, and paid tiers per seat that add more storage, advanced analysis and collaboration. Pricing scales with seats, so a ten-person product org on a paid plan is a real annual line item. Budget for the storage tier too if you keep hours of video.</p>
<h2>What does the workflow actually save?</h2>
<p>Time spent re-watching interviews. Instead of scrubbing a 45-minute recording to find the quote, you search a tag and jump to the timestamp. On a study with twenty interviews that is the difference between an afternoon and a week.</p>
<p>It also makes findings defensible. When someone argues for a feature, you can link the exact clip where a user asked for it. That is hard to do from memory.</p>
<h2>Where does it fall short?</h2>
<p>It does not do the thinking. Dovetail organizes evidence; turning evidence into a decision is still your job, and teams sometimes mistake a tidy repository for insight. A well-tagged project with no synthesis is just a nicer folder.</p>
<h2>Quick Summary</h2>
<ul>
<li>Dovetail is a research repository that transcribes, tags and searches user research.</li>
<li>Define your tag taxonomy before uploading to avoid duplicate tags.</li>
<li>AI tagging catches topics but misses user intent and contradictions.</li>
<li>Free plan for individuals; paid tiers are per-seat with more storage.</li>
<li>It organizes evidence — synthesis and decisions are still yours.</li>
</ul>
<p>Pair it with <a href="https://www.iaifeed.com/ai-tool/contextual-ai">Contextual AI</a> if you want to query the interview corpus in natural language.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.iaifeed.com/how-to-analyze-user-research-interviews-with-dovetail/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
