AI Note-Taking — Capture, Organize & Recall Everything

I want to start using AI transcription for my meetings. Help me set up a workflow. **My situation:** - Meeting tools I use: [e.g., Zoom / Google Meet / Microsoft Teams / In-person / Mix] - Types of meetings: [e.g., '1:1s with direct reports, weekly team standup, client calls, all-hands'] - Average meetings per week: [number] - My role in these meetings: [e.g., 'Usually facilitating' / 'Usually a participant' / 'Mix'] - What I need from meeting notes: [e.g., 'Action items and owners' / 'Key decisions with rationale' / 'Full transcript for compliance' / 'Summary to share with absent team members'] **Concerns:** - Privacy/consent: [Are all participants aware and OK with transcription? Any legal constraints?] - Confidentiality: [Are these meetings sensitive enough that I need enterprise data handling?] - Participants: [Internal team only / Includes external clients or partners] Based on this, give me: 1. A recommendation for which transcription tool to use and why 2. Step-by-step setup instructions for my main meeting platform 3. A consent script I can say at the start of meetings: 'I'm using AI transcription for note-taking...' 4. A post-meeting review checklist: the 5 things I should check in every AI transcript within 24 hours 5. A filing/organization system for where to store and how to name meeting notes Also: what are the common failure modes of AI transcription I should watch for? (Speaker misidentification, technical jargon errors, etc.)

Extract structured information from this meeting transcript. **Meeting context:** - Meeting type: [e.g., 'Weekly team standup' / 'Project kickoff' / 'Client review call' / 'Strategy session'] - Date: [Date] - Attendees: [List names/roles] - Meeting objective (what it was supposed to accomplish): [1 sentence] **Transcript:** [Paste your meeting transcript here — from Otter, Fireflies, or any transcription service] Extract and organize the following: **1. Decisions Made** List every explicit decision, including: - What was decided - Who made the decision (or who has authority) - Any conditions or caveats - Why (if rationale was stated) **2. Action Items** For every commitment made, capture: - [ ] Action: [What exactly needs to be done] - Owner: [Name] - Due date: [Stated or implied date, or 'Not specified'] - Priority: [High / Medium / Low based on context] - Dependency: [Anything blocking this action] **3. Open Questions** Things raised but not resolved — needs follow-up: - Question: [What's unresolved] - Who needs to answer: [Name or 'Unknown'] - Urgency: [High / Medium / Low] **4. Key Information Shared** Important context or data shared in the meeting that should be on record: - [1-2 sentence summary of each key piece of information] **5. Meeting Summary** A 3-5 sentence paragraph summarizing the meeting: what was discussed, what was decided, and what happens next. **6. Follow-up email draft** A brief email I can send to attendees recapping decisions and action items. Tone: [professional / casual / formal]

Help me organize and synthesize my research notes on a topic. **Topic I'm researching:** [e.g., 'Pricing strategies for SaaS products' / 'Machine learning for medical imaging' / 'Urban planning approaches to reduce car dependency'] **Why I'm researching this:** [e.g., 'Making a pricing decision for my product' / 'Writing a research paper' / 'Personal interest / professional development'] **My raw notes (paste everything — messy is fine):** [Paste your raw notes, highlights, quotes, URLs, fragments here] Do the following with these notes: 1. **Identify the main themes**: What are the 4-6 major themes or concepts that appear across these notes? 2. **Synthesize each theme**: For each theme, write a 2-3 paragraph synthesis that integrates information from multiple sources — not just a summary of each source, but a combined understanding. 3. **Identify contradictions and tensions**: Are there places where different sources disagree or tension exists? List them — these are often the most interesting and important things to think about. 4. **Identify gaps**: What important aspects of this topic are NOT covered in my notes? What should I research next? 5. **Create a topic map**: Give me a hierarchical outline showing how the concepts relate to each other. 6. **Key quotes and citations**: Pull out the 5-10 most important quotes or data points from my notes, formatted as citations. 7. **'So what?' analysis**: Based on everything in these notes, what are the 3 most important practical takeaways for [my specific purpose from above]? Organize the output as a structured document I can save as my 'master notes' on this topic.

Help me design a personal knowledge base system using AI note-taking tools. **My context:** - My role/profession: [e.g., 'Product manager at a SaaS company' / 'Freelance consultant' / 'Graduate student' / 'Entrepreneur'] - Main topics I need to track: [List 4-6 subjects you frequently research or refer back to] - Volume of notes: [e.g., '5-10 notes/week' / '20+ notes/week'] - Current pain: [e.g., 'I can never find anything' / 'I re-research the same things repeatedly' / 'My notes are scattered across 4 apps' / 'I capture but never review'] - Tools I already use: [List apps: Notion, Obsidian, Apple Notes, etc.] **Design a knowledge base system that includes:** 1. **Folder/tag structure**: A clear organization system with specific folder names and tag categories for my topics. Include a 'Inbox' for unprocessed notes and a processing workflow. 2. **Note templates**: Create 3 templates for the types of notes I most commonly take: - Meeting note template - Research/article note template - Idea/shower thought template Each template should have standard fields that make notes consistent and searchable. 3. **Weekly review process**: A 20-minute weekly ritual for processing notes from 'raw capture' to 'organized knowledge.' 4. **Linking strategy**: Rules for when to link notes to each other, how to surface related notes when writing new ones, and how to prevent the system from becoming a connection-for-connection's-sake mess. 5. **Review and retrieval**: How to surface relevant notes when starting a new project, preparing for a meeting, or researching a topic you've covered before. Give me specific, implementable instructions — not abstract principles.