Product and research

When new interview data is uploaded, tag every highlight against the existing taxonomy. If 3+ highlights share a genuinely new theme, create an insight and propose a tag name. Post a summary to #research for the research lead.

Every Monday, pull every insight and high-signal highlight created in the past 7 days. Group them by theme. Create a doc titled “Research digest — [week of X]” and post a 3-bullet summary with the link to #product.

When a “feature request” insight passes 10 mentions, search Dovetail for every related highlight and look up each account in Salesforce. Sum ARR by plan tier. Create a Linear ticket with the request summary, ARR breakdown, and top 5 customer quotes.

Every two weeks at sprint kickoff, pull the sprint’s theme tags from Linear. For each ticket, search Dovetail for related highlights and attach the 3 most relevant verbatim quotes as a comment with account name and date.

When a doc is published tagged “feature launch retro,” start a daily schedule for the next 14 days. Each day, search Dovetail for new mentions related to the launch and append to a running reception doc. On day 14, post a summary to #product tagging the PM with sentiment split, top praise, top friction, and confusion called out separately.

When a highlight is escalated for the 3rd time on the same bug, search Dovetail for every mention in the past 90 days. Create a Linear ticket with affected accounts, plan tier, verbatim quotes, and severity. Ping the responsible PM in Slack.

Every quarter, pull all “feature request” insights from the last 90 days. For each, calculate frequency, ARR exposure via Salesforce, and recency-weighted urgency. Rank into Do now, Do next, Watch. Create a doc with methodology and top supporting quote per item.

When an Account is marked “Closed Lost — churned” in Salesforce, pull every Dovetail highlight linked to that account. Create a “Churn reasons — [account]” doc with a timeline, verbatim quotes, and outstanding requests. Share with the account owner and product lead.

When new data is uploaded tagged with an active A/B test name, pull qualitative feedback from the test period. Pull Hex statistical results for the same test. Create a readout doc pairing what the numbers show with why users behaved that way.

Every Monday, pull usability session highlights from Dovetail from the past 7 days. Group friction points by theme with the strongest verbatim quote per theme. Post a summary to #design with links to the underlying sessions.

When a new doc is published in the changelog folder, extract the feature or fix described. Search Dovetail for prior customer feedback requesting or reporting it. Tag those highlights with the changelog date and a “shipped” tag.

Triggered by a Slack webhook when a message matches “I think users want,” “users would love,” or “customers keep asking for.” Search Dovetail for supporting or contradicting evidence. Reply in-thread with the mention count, top quote, and link — or note that nothing exists in research yet.