How to take notes like a project manager 🔗 **Source:** [How to take notes like a project manager](https://www.youtube.com/watch?v=-ekTXhN4ZHo) > [!note]+ Document Notes > tags: [project_management, meeting_notes, note_taking] > author: James Mitchell > source: YouTube > reference: https://www.youtube.com/watch?v=-ekTXhN4ZHo > date created: 2024-12-19 14:30 > > # 🏷️ Title: How to take notes like a project manager > <!-- deep-read:sections start --> ## 🧰 Action Inbox - [H1] Only note down relevant meeting information — avoid transcribing everything #meeting_management - [H2] Always record who said what for accountability — essential for follow-ups #action_tracking - [H3] Date all notes and track deadlines — enables progress tracking #documentation ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - [Original Video](https://www.youtube.com/watch?v=-ekTXhN4ZHo) - [Project Management Best Practices](https://example.com) ## 📝 Summary - A project manager shares practical techniques for taking effective meeting notes based on field experience - Emphasizes selective note-taking focused on actionable items rather than verbatim transcription - Key stakeholders are project managers, team leads, and professionals who run meetings regularly - Risk of information loss if notes aren't comprehensive enough, tradeoff between speed and completeness - Bottom line: Strategic note-taking improves project outcomes and accountability ## 📖 Main Content The video presents three core principles for effective meeting notes from a project management perspective. The speaker, drawing from construction and client meeting experience, argues that selective documentation is more valuable than comprehensive transcription. The first principle involves filtering content to capture only relevant information like dates, actions, and key decisions. The second principle applies David Allen's "brain for having ideas, not holding them" concept to meeting documentation. The third principle covers practical mechanics including attribution, dating, and deadline tracking. The approach balances efficiency with accountability needs. ## 🗒️ Notes #### ⏱️ [00:00](https://www.youtube.com/watch?v=-ekTXhN4ZHo&t=0) — [H1] Introduction to project management note-taking - Key idea: Taking effective meeting notes is an underrated but crucial workplace skill - Evidence: "Making notes i mean good notes i think is underrated it's something that i wish i'd learnt better at university" #### ⏱️ [00:45](https://www.youtube.com/watch?v=-ekTXhN4ZHo&t=45) — [H2] University gap in practical note-taking skills - Key idea: Academic institutions don't adequately teach meeting documentation skills - Evidence: "It's actually something that i think university could do a bit better job at teaching because it's actually really key once you get into the workplace" #### ⏱️ [01:05](https://www.youtube.com/watch?v=-ekTXhN4ZHo&t=65) — [H1] Range of meeting contexts for project managers - Key idea: Note-taking skills must adapt from informal to formal meeting settings - Evidence: "I've led you know quick 15-minute morning meetings with my pen and my pad in a construction site all the way to leading sort of big client meetings" #### ⏱️ [01:25](https://www.youtube.com/watch?v=-ekTXhN4ZHo&t=85) — [H1] First principle: Only note relevant information - Key idea: Selective documentation is more effective than comprehensive transcription - Evidence: "Only note down what is actually relevant to the meeting do not write everything that everything everyone says" #### ⏱️ [01:35](https://www.youtube.com/watch?v=-ekTXhN4ZHo&t=95) — [H2] Historical example of forced selective note-taking - Key idea: Manual distribution constraints historically taught precise documentation - Evidence: "He had to print out the key meeting minutes from a meeting and then individually put them in pigeonholes... it taught him very quickly to learn exactly what he actually needed to make notes about" #### ⏱️ [02:25](https://www.youtube.com/watch?v=-ekTXhN4ZHo&t=145) — [H3] Categories of relevant information to document - Key idea: Focus on dates, actions, outstanding information, and key statements - Evidence: "Confirmation of dates like deliveries or start and end dates of activities key actions that are needed to progress a project outstanding information" #### ⏱️ [02:50](https://www.youtube.com/watch?v=-ekTXhN4ZHo&t=170) — [H1] Second principle: External memory systems prevent forgetting - Key idea: Human memory is unreliable for retaining multiple action items - Evidence: "Your brain is for having ideas not for holding them... there are 36 items that you need to remember in your mind and as soon as that meeting's over you've forgotten everything" #### ⏱️ [03:25](https://www.youtube.com/watch?v=-ekTXhN4ZHo&t=205) — [H2] Consequences of inadequate documentation - Key idea: Forgetting action items can delay projects and affect team productivity - Evidence: "If you don't write it down it will be forgotten... worst case it can cause a delay to the project and actually affect other people's activities" #### ⏱️ [03:50](https://www.youtube.com/watch?v=-ekTXhN4ZHo&t=230) — [H1] Third principle: Attribution and tracking mechanics - Key idea: Recording who made commitments enables effective follow-up - Evidence: "Always note down who said what... if someone is promising to provide something at a particular time and you don't know down who that was you can't know who to go back to" #### ⏱️ [04:25](https://www.youtube.com/watch?v=-ekTXhN4ZHo&t=265) — [H2] Project management requires systematic follow-up - Key idea: Chasing deliverables requires clear ownership attribution - Evidence: "So much of being a project manager at least is chasing people to get certain things done and you need to know who has promised that certain activity" #### ⏱️ [04:40](https://www.youtube.com/watch?v=-ekTXhN4ZHo&t=280) — [H3] Efficiency tip for regular attendees - Key idea: Maintain a reference sheet with names and initials for quick notation - Evidence: "If you've got a group of people that always in your meeting it's helpful to sort of have a separate tab... with all of their names defined and then all of their initials" #### ⏱️ [05:00](https://www.youtube.com/watch?v=-ekTXhN4ZHo&t=300) — [H2] Date everything for progress tracking - Key idea: Timestamps enable tracking of how activities evolve over time - Evidence: "Dates dates dates always date your notes... it's really helpful to know the progression of an activity and how it changes" #### ⏱️ [05:30](https://www.youtube.com/watch?v=-ekTXhN4ZHo&t=330) — [H3] Include deadlines and attendance records - Key idea: Deadlines and attendee lists provide context for accountability - Evidence: "We also like to add on deadlines... keep an eye on who attended your meeting... it's surprising how quickly you can forget who is actually at a certain meeting" ## 📚 References - [Original YouTube Video](https://www.youtube.com/watch?v=-ekTXhN4ZHo) - David Allen's "Getting Things Done" methodology (referenced concept) - OneNote (mentioned as tool) ## 🗣️ Paraphrase - Effective meeting documentation requires strategic filtering rather than comprehensive recording of all discussion points - Human memory limitations make external recording systems essential for tracking multiple commitments and deadlines across projects - Systematic attribution and dating create accountability structures that enable project managers to effectively follow up on deliverables and track progress over time ## 📰 Newsletter **Level Up Your Meeting Notes: Project Management Techniques for Better Documentation** Whether you're running WordPress community meetups, client calls, or team standups, taking strategic notes can transform your follow-through. This week's insight comes from a project manager who's learned that selective documentation beats verbatim transcription every time. **Key takeaway**: Focus on capturing dates, actions, and ownership rather than every spoken word. Your future self (and your team) will thank you when it's time to track deliverables and follow up on commitments. **Try this**: Create a simple template with attendee initials, action items with owners, and deadlines. Date everything and watch your project coordination improve dramatically. Resources: [Learn WordPress](https://learn.wordpress.org/), [Developer Docs](https://developer.wordpress.org/), [WP-CLI](https://wp-cli.org/) ## ✅ Action Items #### DevRel - Developer advocacy: Create note-taking templates for community meetups and developer calls with clear action tracking - Education: Develop workshop curriculum on effective meeting documentation for community leaders - Community management: Implement systematic meeting minutes for contributor meetings with owner attribution #### WordPress - Community: Provide meetup organizers with note-taking templates that capture action items and deadlines effectively - Training: Add meeting facilitation and documentation modules to community leadership learning paths - Meta: Standardize meeting minutes format across WordPress project teams with consistent attribution and dating ## 🧪 Hypotheses - Systematic attribution in meeting notes reduces follow-up time by 40% compared to unattributed documentation - Teams using structured note-taking templates complete action items 25% faster than those using freeform notes - Meeting attendees are 60% more likely to complete commitments when ownership is explicitly documented - Projects with dated progress notes experience fewer delays due to improved tracking visibility ### 📊 Methodology - A/B test structured vs. freeform note-taking templates across project teams measuring completion rates and timeline adherence - Time-tracking study comparing follow-up efficiency with and without systematic owner attribution - Survey analysis of meeting satisfaction and accountability perceptions based on documentation quality ### ❓ Questions - How do digital note-taking tools compare to analog methods for retention and action item completion in project settings? - What note-taking adaptations are needed for remote vs. in-person meetings to maintain the same accountability levels? - How can automated transcription tools be integrated while preserving the strategic filtering benefits of manual note-taking? ### 🔮 Future Research - Investigation of AI-assisted meeting summarization tools that maintain strategic filtering while reducing manual effort - Cross-industry comparison of note-taking methodologies beyond construction and project management contexts - Development of collaborative note-taking systems that maintain individual accountability while enabling team visibility ### 💡 Implications - Practice: Teams adopting systematic note-taking see improved project delivery and reduced miscommunication - Policy: Organizations should establish meeting documentation standards that balance efficiency with accountability needs - Education: Professional development programs should include practical meeting facilitation and documentation skills - Funding: Investment in note-taking systems and training provides measurable returns through improved project outcomes ### 🧠 Learning Styles Assessment Reading level estimate: 8th grade (clear, practical language with concrete examples) #### 👀 Visual learners - Present: Clear structure with numbered principles and bullet points - Improve: Add flowcharts showing note-taking decision trees, sample meeting minutes templates #### 🔊 Aural learners - Present: Video format with conversational narration style - Improve: Podcast version focusing on audio-only consumption, verbal examples #### 🗣️ Verbal learners - Present: Storytelling approach with supervisor anecdotes, clear definitions - Improve: More analogies comparing note-taking to other familiar processes #### 🧩 Kinesthetic learners - Present: Practical tips that can be immediately implemented - Improve: Interactive templates, hands-on exercises for practicing techniques #### 🧠 Logical learners - Present: Structured three-principle framework, cause-and-effect relationships - Improve: Decision matrices for what to document, ROI calculations for time invested #### 🧑‍🤝‍🧑 Social learners - Present: Team context and collaborative meeting scenarios - Improve: Group exercises, peer review systems for meeting minutes quality #### 🧘‍♀️ Solitary learners - Present: Individual responsibility focus, personal skill development - Improve: Self-assessment checklists, reflection prompts for note-taking improvement #### 🌿 Naturalistic learners - Present: Construction site examples connecting to physical environments - Improve: More industry-specific examples, environmental context for different settings ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Clear heading structure, logical content flow - Improve: Add ARIA labels for video chapters, descriptive alt text for visual elements #### Keyboard navigation - Present: Video player supports keyboard controls - Improve: Chapter navigation shortcuts, focus indicators for interactive elements #### Contrast and readability - Present: High contrast video interface, clear audio - Improve: Closed captions with proper contrast ratios, transcript formatting #### Text resizing and reflow - Present: YouTube interface scales appropriately - Improve: Companion materials that reflow at 200% zoom without horizontal scrolling #### Media and captions - Present: Video content with clear audio - Improve: Professional captions, downloadable transcript, chapter markers #### Forms and interactions - Present: Standard video controls with proper labeling - Improve: Interactive note-taking templates with accessible form design ### 🌍 DEIB Assessment #### Cultural breadth - Present: Construction industry perspective with universal application - Improve: Examples from diverse industries and cultural contexts beyond Western business practices #### Inclusive language - Present: Gender-neutral pronouns, accessible vocabulary - Improve: Avoid industry jargon without definition, provide terminology glossary #### Neurodiversity support - Present: Clear structure with consistent formatting - Improve: Multiple content formats (visual, audio, text), processing time accommodations #### Representation - Present: Single perspective from construction/project management - Improve: Include voices from different industries, cultures, and professional backgrounds #### Psychological safety - Present: Non-judgmental tone about learning and skill development - Improve: Acknowledge different learning paces, validate various note-taking preferences ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Strong - follows logical structure from principles to specific applications - Inductive strength: Moderate - generalizes from construction experience to broader contexts - Causal reasoning: Good - clearly links poor documentation to project delays - Analogical strength: Effective - supervisor story illustrates filtering principles well #### Fallacies - Hasty generalization: Limited industry experience generalized to all contexts - could include more diverse examples - Appeal to authority: Relies heavily on supervisor's experience without additional validation - add research backing #### Tone of voice - Overall tone: Conversational and practical with self-deprecating humor ("making a video about making notes") that maintains accessibility while demonstrating expertise ### 🛡️ DARVO Analysis - Deny: No concerning patterns of denial or minimization present - Attack: No attacks on critics or alternative approaches - Reverse victim/offender: No victim/offender dynamics in content - Emotional cues and rhetoric: Positive, encouraging tone focused on skill development rather than blame ## 🎯 Conclusion - Strategic note-taking focusing on relevant information, attribution, and systematic tracking significantly improves project outcomes and team accountability - Practical next steps include creating templates with attendee tracking, implementing consistent dating systems, and establishing clear ownership attribution for all action items - This approach connects to broader workplace effectiveness trends emphasizing external memory systems and systematic follow-through processes ## 🧱 Refactor Appendix ### 📚 Literature Split Pad Purpose: Stage CEE units that become Literature notes. Split level: H3 ### [H1] Selective documentation outperforms comprehensive transcription > [!quote] [How to take notes like a project manager](https://www.youtube.com/watch?v=-ekTXhN4ZHo) by [[James Mitchell]] via [[YouTube]]. Published 2024. Accessed 2024-12-19. > "Only note down what is <!-- deep-read:sections end -->