Write Evidence-Linked Dovetail Findings
Write each finding as a bounded claim supported by traceable evidence, then separate the recommended action. Dovetail now calls the former Insights format Docs; use the current object while preserving familiar research language.
Before you start: Have reviewed source material, relevant highlights and Doc edit access. Identify the product decision the finding should inform.
Worked example: New owners misunderstand contractor access in the invite flow is narrower than onboarding is broken. Support the specific claim with source context and explain who the study did not cover.
Step-by-step guide
Write the claim
State the observed pattern, audience and context. Avoid a universal conclusion that exceeds the study.
Add supporting evidence
Link relevant highlights and explain how each supports the claim. Keep a source reference rather than copying untraceable fragments.
Include contradictory cases
Describe evidence that limits the pattern. Do not hide disagreement merely to make the narrative clean.
State the limitation
Record sampling, method and uncertainty. Separate frequency in this study from prevalence in the entire customer base.
Propose a decision
Explain the action or next research question the evidence justifies. Keep the recommendation distinct from the observation.
Review and share
Ask another researcher to check the evidence trail, then verify the Doc’s sharing permissions before sending the link.
Common mistakes
Insight headline becomes universal
Bound the audience and context.
Evidence dump without reasoning
Explain the link between source and claim.
Recommendation presented as observation
Keep them separate.
Tips
Use one main claim per finding.
Preserve the strongest counterexample.
Check source access with a recipient.
Sources and verification
Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.