Connect Dovetail Research to Decisions
Link the decision to a bounded finding, explain the tradeoff and record what remains uncertain. Research informs a product choice; it does not automatically dictate a feature or remove delivery and policy constraints.
Before you start: Have reviewed findings, an accountable decision owner and relevant product constraints. Use a Doc or linked decision record accessible to the intended audience.
Worked example: Evidence of contractor-access confusion can inform clearer permission language, a review step or a different default. The research does not inherently prescribe one of those solutions.
Step-by-step guide
State the decision
Write the choice the team must make and the owner responsible. Keep the scope specific enough to evaluate alternatives.
Link the relevant findings
Use evidence-backed claims with their audience and limits. Avoid cherry-picking one quote that supports an existing preference.
List credible alternatives
Include a smaller change or no change where realistic. Explain how each addresses the observed problem.
Add constraints
Record feasibility, policy and operational considerations separately from research evidence. Do not present stakeholder preference as a customer finding.
Write the rationale
Explain why the chosen option is proportionate to the evidence and risk. Preserve the strongest argument against it.
Set a review trigger
State what outcome or new evidence would cause reconsideration. Link implementation work back to the decision record without exposing unnecessary raw data.
Common mistakes
Quote becomes requirement
Understand the problem before choosing a solution.
Constraints disguised as findings
Keep evidence and delivery tradeoffs distinct.
Decision detached from source
Future reviewers cannot assess the rationale.
Tips
Keep alternatives in the record.
Record the decision owner explicitly.
Use a review trigger rather than a permanent certainty claim.
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.