Build a lab meeting facilitation guide: agenda archetypes, artifact capture, decision…
- User
Build a lab meeting facilitation guide: agenda archetypes, artifact capture, decision logs, and action tracking.
- Assistant
Lab Meeting Facilitation Guide
Built by Sherlock, Trailblazer Labs
Empower your team to turn chaotic discussions into high-impact outcomes. This guide provides reusable templates and processes for efficient lab meetings in research, engineering, or innovation environments.1. Purpose & Core Principles
Lab meetings drive alignment, capture knowledge, and accelerate progress. Key Principles:
- Time-box everything: Keep meetings to 30-60 minutes.
- Facilitator role: Neutral guide; rotate weekly.
- Pre-meeting prep: Share agenda 24h in advance; attendees submit updates.
- Post-meeting ritual: Publish notes within 1h (artifact capture + logs).
- Tools: Notion/Google Docs (notes), Miro/Figma (visuals), Slack/Teams (async updates), Airtable/Excel (tracking).
2. Agenda Archetypes
Use these plug-and-play templates. Customize based on team size (5-15 ideal). Each includes time allocations and outputs.
Archetype 1: Weekly Sync (30 min)
Purpose: Alignment on progress/blockers.
1. Quick Wins (5 min): 1 highlight per person. 2. Blocker Busting (10 min): Share & triage blockers. 3. Priorities for Next Week (10 min): Top 3 per project. 4. Actions/Decisions (5 min): Capture live.Output: Updated action tracker.
Archetype 2: Project Kickoff (45 min)
Purpose: Launch with clarity.
1. Context & Goals (10 min): Problem, objectives, success metrics. 2. Roles & Timeline (10 min): RACI matrix, milestones. 3. Risks & Dependencies (10 min): Brainstorm & mitigate. 4. Q&A/Commit (15 min): Buy-in round-robin.Output: Kickoff doc + initial action log.
Archetype 3: Research/Experiment Review (60 min)
Purpose: Deep-dive feedback.
1. Hypothesis Recap (5 min). 2. Results Presentation (20 min): Data viz, key findings. 3. Feedback Rounds (20 min): +/Δ/ideas (structured). 4. Next Experiments (10 min): Prioritize. 5. Decisions/Actions (5 min).Output: Review artifact + decision log.
Archetype 4: Brainstorming/IDEation (45 min)
Purpose: Generate ideas silently first.
1. Problem Framing (5 min). 2. Silent Ideation (10 min): Post-its/digital. 3. Clustering & Voting (15 min): Group & dot-vote top 3. 4. Refine & Assign (15 min).Output: Miro board + action items.
Archetype 5: Retrospective (30 min)
Purpose: Continuous improvement.
1. What Went Well (10 min). 2. What to Improve (10 min). 3. Actionable Experiments (10 min).Output: Retro notes + process actions.
Pro Tip: Start with "Parking Lot" for off-topic items (capture in shared doc).
3. Artifact Capture
Goal: Immutable record of discussions for async review. Always create a "Meeting Hub" page (e.g., Notion database).
Process
- Pre-Meet: Create page with agenda + attendee input fields.
- Live Capture:
- Screenshots of slides/shared screens.
- Transcripts (Otter.ai/Zoom auto).
- Visuals: Export Miro/Figma frames.
- Post-Meet: Facilitator summarizes in <1h; tag @team.
Template: Meeting Hub Page Structure
# [Date] Lab Meeting: [Archetype/Topic] ## Agenda - [Bullet points] ## Key Artifacts - [Slides: Link] - [Visuals: Embed Miro/Figma] - [Transcript: Link] ## Attendee Updates | Name | Update | Blocker | |------|--------|---------| | ... | ... | ... | ## Raw Notes - [Timestamped bullets]4. Decision Logs
Goal: Track "what we agreed" to avoid rehashing. Use a centralized Decision Log Database (Notion/Airtable).
Best Practices
- State decisions positively (e.g., "We will use X").
- Capture DRII: Decision, Rationale, Impact, Initiator.
- Review last 3 decisions at start of every meeting.
Template: Decision Log Entry
Date Decision ID Decision Rationale Impacted Status YYYY-MM-DD D001 Switch to PyTorch for ML pipeline. Better GPU support; 20% faster training. All ML team. Approved ... ... ... ... ... ... Live Capture Prompt: "Who supports? Objections? Recorded as D###."
5. Action Tracking
Goal: Convert talk to motion. Use a shared Action Tracker (Airtable/Notion table). Review at every meeting start/end.
Process
- Assignment: "Who? By when? What does 'done' look like?"
- Follow-Up: @owner in Slack weekly; escalate if overdue.
- Status: New → In Progress → Blocked → Done.
Template: Action Tracker
Action ID Description Owner Due Date Status Notes/Outcome Completed Date A001 Prototype v1 UI. @Alice 2023-10-15 In Progress Awaiting design feedback. A002 ... @Bob 2023-10-10 Blocked Depends on vendor API. ... ... ... ... ... ... ... Review Cadence:
- Start: "Actions from last time?"
- End: "New actions? Confirm owners/dues."
6. Facilitation Toolkit & Tips
- Timer: Use shared countdown (e.g., Google Timer).
- Icebreaker: 1-min "One word to describe your week."
- Inclusivity: Round-robin for input; call on quiet voices.
- Escalation: Flag high-impact items for 1:1 follow-up.
- Metrics for Success: 80% actions completed on time; NPS >8/10 post-meeting.
- Scale for Remote: Use reactions (👍/🚀/🔥) for quick polls.
7. Quick-Start Templates
- Notion Duplicate: Full Meeting Hub (Link placeholder; build your own)
- Google Sheet: Action + Decision Tracker
- Export this guide to your team's wiki.
Iterate this guide in your next retro. Questions? Ping Sherlock. 🚀
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.