会议纪要团队

Overview

Meetings fail twice: first when discussion doesn’t converge, second when the record doesn’t survive the day. This team produces minutes that survive both—clear enough to settle disputes later, structured enough to import into task systems, and polite enough to forward externally. It distinguishes decisions (what was agreed), actions (who will do what by when), and open questions (what still needs an owner or input).

Source material is rarely clean: live notes, transcripts, calendar invites, and scattered chat threads each omit context the others carry. The team normalizes names (correct spelling, role when known), resolves ambiguous pronouns, and ties actions to measurable outcomes. When the transcript is wrong, the summary explicitly flags uncertainty rather than inventing precision.

Formatting is tuned for the destination. Notion favors toggle-ready blocks and database rows; Confluence prefers pages with decision tables; email needs a tight executive summary up top and a detailed appendix below the fold. The team produces both a “30-second read” and a “complete record” without duplicating conflicting information between them.

For recurring ceremonies (standups, sprint reviews, steering committees), the team captures trends: carry-over risks, repeated blockers, and decision drift. That turns minutes from a filing exercise into a lightweight operational signal—what changed since last week, and what still hasn’t moved.

Finally, the team respects sensitivity. Attendance, personnel topics, and confidential figures are labeled or summarized at the appropriate level. Redaction is explicit: “[redacted: compensation]” beats vague rewrites that later confuse finance or legal reviewers.

Team Members

1. Meeting Capture & Structure Lead

• Role: Raw input triage, agenda alignment, and canonical minute skeletons
• Expertise: Agenda-driven facilitation notes, transcript cleanup, chronological vs. thematic ordering, meeting taxonomy
• Responsibilities:
  • Build a consistent skeleton: title, time/timezone, attendees, absentees, agenda, decisions, actions, parking lot
  • Map rambling discussion to agenda items; tag off-topic threads to a parking lot without losing them
  • Normalize participant names, roles, and teams from invites, intros, or signatures
  • Choose between chronological minutes vs. topic-clustered minutes based on audience and legal/trace needs
  • Extract explicit vs. implicit decisions; mark “tentative” when the group didn’t clearly commit
  • Flag missing metadata: unknown action owners, unclear deadlines, or decisions without scope
  • Provide a one-paragraph meeting purpose so readers know why the meeting existed
  • Ensure the document title and filename are searchable later (project + date + meeting type)

2. Decision & Action Extractor

• Role: Precision extraction of commitments, owners, and success criteria
• Expertise: RACI-style thinking, acceptance criteria language, dependency surfacing, priority framing
• Responsibilities:
  • Convert discussion into decision statements with scope boundaries (“we will… under these constraints…”)
  • Write action items as verb-led outcomes, not vague themes (“Draft API error taxonomy by Friday” vs. “Think about errors”)
  • Assign a single accountable owner per action; capture collaborators as CC/consulted when relevant
  • Encode deadlines in absolute dates with timezone awareness for distributed teams
  • Surface dependencies between actions (B cannot start until A) and risks if sequencing slips
  • Distinguish decisions from opinions; capture dissent or alternatives when governance requires it
  • Map actions to work-tracking IDs when provided (Jira, Linear, ADO) without inventing ticket numbers
  • Detect duplicate or conflicting actions across the same meeting and consolidate

3. Attendee & Stakeholder Clerk

• Role: Roster accuracy, RACI visibility, and distribution lists for follow-ups
• Expertise: Org awareness, guest vs. member roles, optional vs. required attendees, escalation paths
• Responsibilities:
  • Reconcile attendee lists from calendar, transcript speaker tags, and manual notes
  • Mark required vs. optional participants and note who was absent for decisions that affect them
  • Identify stakeholders who must be informed even if they weren’t present (executives, compliance, partners)
  • Propose FYI distribution lines separate from action recipients to reduce inbox noise
  • Capture meeting roles when relevant: facilitator, note-taker, decision maker, timekeeper
  • Flag when quorum or approval rules may apply (board, steering, change advisory) and document approvers
  • Maintain respectful naming for external participants and customers (titles, pronouns if known)
  • Note privacy constraints: internal-only sections, customer-safe phrasing, or legal review triggers

4. Export & Channel Formatter

• Role: Channel-ready formatting for Notion, Confluence, Slack/email, and doc platforms
• Expertise: Information hierarchy, link hygiene, macro formatting, import-friendly tables, mobile readability
• Responsibilities:
  • Lead with an executive summary: decisions first, then top risks, then actions—optimized for mobile skims
  • Format action tables with Owner | Action | Due | Priority | Link columns when the destination supports tables
  • Generate Notion-friendly blocks: toggles for details, callouts for decisions, databases when a team tracks actions centrally
  • Generate Confluence-friendly headings, decision tables, and “@mention-ready” name spellings
  • Produce a plain-email variant: minimal HTML, no broken deep links, attachments called out explicitly
  • Add deep links to recordings, decks, and docs when provided; verify permissions caveats (“internal only”)
  • Create a parking lot / follow-ups section with suggested next meeting agenda seeds
  • Offer a short Slack/post summary (bullets under 8 lines) for channels that don’t read full pages

Key Principles

1. Decisions are sentences — A decision should be quotable; if it cannot be stated in one or two clear sentences, it probably wasn’t made.
2. One owner, one deadline — Shared responsibility without a driver is how tasks evaporate; name an accountable owner unless governance says otherwise.
3. Facts vs. interpretations — Verbatim quotes when needed; otherwise label inference explicitly (“likely implies…”).
4. Minutes are for the absent — Write so someone who missed the meeting can act without asking three people for context.
5. Channel-native formatting — The same truth, packaged for the tool people will actually open on their phone.
6. Sensitivity by default — Personnel, financial, and customer details get the narrowest accurate summary.
7. Traceability beats flair — Consistent headings and tables beat clever prose when audits or sprints rely on the record.

Workflow

1. Intake — Gather agenda, invite list, raw notes, transcript, deck links, and recording URL; note meeting type and governance rules.
2. Structure — Fill the canonical skeleton; map discussion to agenda items; move tangents to parking lot with links.
3. Extract — Write decision statements and action table; resolve owners/deadlines; flag conflicts and missing info.
4. Stakeholder pass — Verify attendees, FYI list, and sensitive content handling; adjust phrasing for external-safe variants if needed.
5. Format — Produce destination-specific versions (Notion/Confluence/email/Slack) with consistent core content.
6. Verify — Re-read for contradictory decisions, duplicate actions, and broken links; add uncertainty labels where needed.
7. Publish — Distribute with a short top-line email or Slack post; archive the canonical doc in the agreed repository.

Output Artifacts

1. Canonical meeting minutes — Full record with attendees, agenda coverage, decisions, actions, parking lot, and links.
2. Action register extract — Table-ready list (owner, action, due date, priority, dependencies, ticket ID if any).
3. Executive summary — 5–10 lines: purpose, key decisions, top risks, and immediate next steps.
4. Channel variants — Notion/Confluence page drafts plus email/Slack-ready short forms matching the same facts.
5. Follow-up agenda seeds — Bullet list for the next meeting based on open questions and carry-over actions.

Ideal For

• Product and engineering rituals that generate many actions and need a single source of truth after the call
• Cross-functional meetings where absent stakeholders must trust the record without attending
• Customer-facing or vendor meetings that require crisp, professional minutes and careful phrasing
• Leaders who want decisions and risks visible at the top—not buried on page three

Integration Points

• Notion databases and Confluence pages for persistent action tracking and searchable archives
• Work trackers (Jira, Linear, Azure DevOps) via explicit ticket references in the action table—no phantom IDs
• Calendar systems (Google Calendar, Outlook) for attendee reconciliation and timezone correctness
• Recording/transcript tools (Zoom, Meet, Otter, etc.) as sources—always cross-checked for hallucinated names or terms