Semantic Meeting Memory
Flow 3: Living documentation from every conversation
The Fragmentation Problem
Meeting notes scatter across individual systems. Critical context disappears. Decisions get forgotten. Action items fall through cracks. Team members can't access the full project narrative.
Your Semantic Solution
Instead of scattered notes, build a living knowledge base that captures, connects, and surfaces information across all your meetings.
Record & Auto-Summarize
Use Granola or similar tools to record and auto-summarize every meeting. Transcripts and summaries are generated automatically, so you can stay focused on the conversation.
Share & Query
Share Granola folders with team members and query across all meetings in a folder. Ask questions like “What did we decide about the timeline?” and get answers drawn from multiple meeting transcripts.
Build Living Documentation
Create a NotebookLM or custom GPT instance that ingests meeting transcripts and project documentation. This becomes your project's living knowledge base that anyone can query.
Bonus: Claude Projects
Create a Claude Project (team or enterprise accounts) and share it for quantitative documentation and analysis. This enables the richest querying experience with the full power of Claude's analytical capabilities.
What You Gain
Projects Have a Home
All meeting context, decisions, and documentation live in one searchable place instead of scattered across email threads, Slack channels, and personal notes.
Instant Onboarding
Team members can onboard quickly by querying the meeting history. No more spending hours catching someone up on what they missed.
Cross-Meeting Intelligence
Surface recent to-dos, understand input from a particular person, and track decisions across meetings—even if you weren't in every one.
One-Prompt Deliverables
Create wrap-up documents, status updates, and presentation materials with a single prompt drawn from your entire meeting history.
From Reactive to Strategic
Every day tasks feel like BAU—they can be relatively mindless and reactive, which can feel productive at times and draining at others. Automations can take minutes to hours out of your daily admin and KTLO work. Alternately, building a presentation and bringing stakeholders along for the ride by showing analysis, context for decision making, and paths forward can be hours to days of work that can be significantly paired down.
These flows are attainable and can be incrementally beneficial for most people working white collar jobs where email, analysis, and knowledge on a project or undertaking are important. They take little time to set up. The work is in refining them and retraining yourself to always have something running in the background working for you while you reallocate your hours to higher value work.
Homework
Choose One Flow to Try
Pick one of the three automations from this class—email triage, voice-to-deck, or meeting memory—and set it up this week.
Identify Your Pain Point
Think about one frustrating, repetitive, or sloppy task you do. In Class 2, Stuart will cover how to identify these areas and explore more targeted tools and customizations that focus on unique use cases rather than broad automations.
Key Takeaways
- ✓Meetings are data — treat transcripts as queryable knowledge, not disposable notes
- ✓Shared folders enable shared context — your team doesn't need to be in every meeting to know what happened
- ✓Living documentation beats static notes — a queryable knowledge base grows more valuable over time
- ✓The real work is refinement — setup is quick, the value compounds as you retrain habits