Teklens logo
DEEN
Back to the Playbook
Product BrainFoundationPB-02

Capture product decision

Turn a decision made in a meeting, thread or document into a recorded decision with rationale, linked to the Jira items and code it affects.

Product statusBetaCapturing decisions from notes and files is available today. The Meeting bot that records meetings is in beta.

Context in4 required inputsMeeting notes or transcript (Meeting bot, Beta) · Product objectives · Related Jira items
TransformationProduct Manager + Product AgentLocal Files · Atlassian · Code Analysis
OutcomeDecision record with rationale and linked follow-ups.Artifact: Decision record

Why it matters

Decisions stay in meetings. Feedback is missing from the ticket. This Activity writes the decision, not only the ticket: the goal, the option chosen, the options rejected and why.

Owner

Product Manager

Human + Agent

Participants · Agents

EngineerHead of ProductProduct Agent

Trigger

ManualA product decision is made in a meeting, a review or a document.

Required context

Meetings · BetaMeeting notes or transcript (Meeting bot, Beta)Product BrainProduct objectivesJiraRelated Jira itemsCodeAffected code

Optional context

Customer evidenceCustomer evidenceProduct BrainPrevious decisionsConfluencePRD

Skills

Local FilesAtlassianCode Analysis

Activity steps

  1. 1Extract the decision, the options rejected and the reasons.
  2. 2Link it to objectives, Jira items and the affected code.
  3. 3Draft the decision record and the follow-up work it implies.
  4. 4Publish after approval and notify the affected Activities.

Output

Decision record with rationale and linked follow-ups.

Artifacts

Creates: Decision record

Updates: Product Brain

What good looks like

  • The decision is stated as a choice, not as a summary of the discussion.
  • Rejected options and reasons are recorded.
  • Affected tickets and code are linked.
  • Owner and date are set.

Quality gate

The decision owner confirms the record before it becomes authoritative context.

Destination

Product BrainJira

Usually next

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.

Deep dives from the AI PM Lab

Articles that explain the thinking behind this Activity.

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.

Book a demoBack to the Playbook