Back to the Playbook
Strategy & DiscoverySD-16
How to run effective product meetings
First decide whether live discussion is necessary; preserve preparation and resume with the actual meeting outcomes.
Product statusAssisted workflowTeklens prepares the pre-read and writes the recap from notes or a transcript; the discussion itself happens between people.
Input3 required inputsMeeting purpose and the decision needed · Relevant documents and participant perspectives · Initiative focus and approved Product Brain guidance
SkillsPrepare a decision-focused meeting · Synthesise supplied evidence · Record decisions and follow-upProduct Manager + Product Manager Agent
OutcomeMeeting brief before, decision recap after: purpose, agenda and pre-read; then confirmed decisions, owners, open questions and affected documents.Artifact: Meeting brief
Owner
Product Manager
Human-led
Participants · Agents
Head of ProductEngineerDesignerProduct Manager Agent
Trigger
A meeting is proposed for a decision or a learning the team needs.
Required context
Product BrainMeeting purpose and the decision neededConfluenceRelevant documents and participant perspectivesProduct BrainInitiative focus and approved Product Brain guidance
Optional context
Meetings · BetaMeeting notes or transcriptProduct BrainPrior decisions on the topic
Skills
Prepare a decision-focused meetingSynthesise supplied evidenceRecord decisions and follow-upPrepare task context
Suggested conversation arc
- 1Decide whether to meetState the desired outcome and choose decision, review or discovery. Use an asynchronous update instead when live discussion adds no value.Skills: Prepare task context
- 2Prepare the useful pre-readDraft an agenda, specific questions, required participants and concise context. Distinguish decision makers from people who only need the recap.Skills: Prepare a decision-focused meeting
- 3Capture the discussion outcomeHold the meeting or complete the agreed asynchronous exchange; capture explicit decisions, unresolved questions, owners and dates in notes or a transcript.
- 4Confirm decisions and document changesCheck proposed decisions against the evidence, confirm owners and identify affected canonical documents. Draft their changes separately and retain the recap without implicitly sending messages.Skills: Synthesise supplied evidence · Record decisions and follow-up
Output
Meeting brief before, decision recap after: purpose, agenda and pre-read; then confirmed decisions, owners, open questions and affected documents.
Artifacts
Creates: Meeting brief
What good looks like
- The agenda has a concrete desired outcome and appropriately scoped questions.
- Proposals and confirmed decisions are distinguishable in the recap.
- No invented attendance, owner, due date or approval.
Quality gate
The meeting owner confirms the decisions and the owners before any document changes.
Destination
Product BrainConfluence
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.
Choose the path that matches your role.
Set the Product AI direction with us, or test the shared Product Brain on real work with Jira and code.