Back to the Playbook
DiscoverResearchDI-04

Synthesise user research

Turn a batch of interviews and research inputs into defensible themes, pains and opportunities that enter the Product Brain as evidence.

Product statusAvailable now

Context in3 required inputsInterview notes and transcripts · Research objective · Participant metadata
TransformationProduct Manager + Research Agent + Product AgentLocal Files · Atlassian
OutcomeResearch synthesis with themes, evidence and implications.Artifact: Research synthesis

Why it matters

Research that lives in a slide deck is read once. Research that lives in the Product Brain is used by every later Activity: the brief, the PRD, the prioritisation.

Owner

Product Manager

Human + Agent

Participants · Agents

ResearcherResearch AgentProduct Agent

Trigger

Event-drivenA meaningful batch of new research evidence exists.

Required context

Customer evidenceInterview notes and transcriptsProduct BrainResearch objectiveFilesParticipant metadata

Optional context

Customer evidenceSupport ticketsAnalyticsAnalyticsProduct BrainPrevious research themes

Skills

Local FilesAtlassian

Methods used inside this Activity: Affinity clustering · Opportunity solution tree

Activity steps

  1. 1Extract observations per interview.
  2. 2Cluster into themes and distinguish frequency from severity.
  3. 3Identify contradictions and minority signals.
  4. 4Link evidence to existing or new opportunities.

Output

Research synthesis with themes, evidence and implications.

Artifacts

Creates: Research synthesis

Updates: Product Brain, Opportunity

What good looks like

  • Every conclusion links to evidence.
  • Minority signals are preserved.
  • No fabricated consensus.
  • Implications are stated as options, not as decisions.

Quality gate

Product or research lead reviews before conclusions enter the Product Brain.

Destination

Product BrainConfluence

Usually next

Method references: Torres, Continuous Discovery Habits

People and agents work from the same Product Brain. The owner stays accountable. Assigned agents prepare and check. A named person approves at the gate.

Show us exactly how product work happens today.

Thirty minutes with a founder. We compare your process with the Playbook and pick the first Activity to run on your Jira and your repo.