## Overview Effective meetings depend on structured **note-taking** to capture key outcomes and ensure follow-through. Without proper documentation, meetings become repetitive and unproductive. Four established note-taking frameworks help teams capture, organise, and act on meeting outcomes within a recommended **30-minute** meeting window. --- ## Key Concepts - **Meeting Efficiency** – Meetings should be time-bound (ideally ≤30 minutes); inability to reach outcomes within that window signals inefficiency - **Note-Taking as a Productivity Tool** – Structured notes transform discussions into actionable outcomes - **Framework Selection** – Different meeting types require different note-taking methods; no single method fits all scenarios - **Note Ownership** – Assigning a dedicated note-taker ensures nothing is missed during active discussion --- ## Detailed Notes ### Why Note-Taking Matters - Captures **key outcomes** during and after a meeting - Enables teams to **implement decisions** rather than revisit the same discussions - Prevents the cycle of conducting repeated meetings without reaching conclusions - Creates a **shared reference** that aligns all participants on action items ### The Three Guiding Questions 1. **What?** – What impact will structured notes have on meeting outcomes? 2. **Why?** – Why is disciplined note-taking critical for execution? 3. **How?** – How should the note-taking framework be applied in practice? --- ### Framework 1: The Cornell Method - Divides a page into **three sections**: - **Cues** – Key points recorded *after* the meeting; act as triggers for recall - **Notes** – Detailed points recorded *during* the meeting; typically 3–4 notes per cue - **Summary** – A concise list of **action points** distilled from cues and notes - Best suited for meetings where **recall and review** are priorities --- ### Framework 2: The Mapping Method - Built around the **agenda structure** of a meeting - Process: 1. Write the **main agenda** at the centre or top 2. Branch into **sub-agendas** (e.g., technology, user experience, feedback) 3. Add **details** under each sub-agenda explaining expected outcomes 4. Record **discussion points** linked to each agenda item - Helps the brain organise information hierarchically - Sub-agendas should be written in **clear, easy-to-understand language** - Notes should be legible and actionable enough for any team member to execute without confusion - Commonly used in **product management** contexts --- ### Framework 3: The Charting Method - Structures notes in a **tabular or columnar** format - Process: 1. State the **single main agenda** at the top 2. Break it into **sub-topics** (unlike mapping, this focuses on one agenda per meeting) 3. Record **point-wise details** under each sub-topic - Differs from Mapping: focuses on **one deep agenda** rather than multiple broad agendas - Best suited for **theoretical, HR, and marketing meetings** – less ideal for finance or sales - Helps junior team members understand the meeting structure clearly --- ### Framework 4: The Outlining Method - Originally designed for academic note-taking; adaptable to business meetings - Process: 1. List **main agendas** at the top (can be single or multiple) 2. Nest **sub-agendas** below each main agenda 3. Record **actionable sub-points** under each sub-agenda - All sub-points must be **executable/actionable** (e.g., features to implement, timelines, ownership) - Example structure: - Main Agenda → Sub-Agenda → Key features, timeline, ownership assignment --- ### Implementation Guidelines - **Choose the right method** – Match the note-taking framework to the meeting type and team workflow - **Share notes centrally** – Upload handwritten or digital notes to a shared cloud location so all team members can access them - **Assign a dedicated note-taker** – Designate one person (not the meeting leader) to focus solely on capturing notes - **Distribute and act** – Share notes immediately after the meeting to enable prompt execution --- ## Tables ### Comparison of Note-Taking Frameworks | Framework | Structure | Best For | Key Feature | |-----------|-----------|----------|-------------| | **Cornell** | Cues + Notes + Summary | Review-focused meetings | Post-meeting cue generation | | **Mapping** | Main agenda → Sub-agendas → Details → Points | Product management, multi-agenda meetings | Hierarchical brain-friendly layout | | **Charting** | Single agenda → Sub-topics → Point-wise details | Theoretical, HR, marketing meetings | Deep single-agenda focus | | **Outlining** | Main agendas → Sub-agendas → Actionable sub-points | General business meetings | Actionable and executable outputs | ### When to Use Each Framework | Meeting Type | Recommended Framework | |---|---| | Strategy review / brainstorming | Cornell | | Product planning / multi-topic | Mapping | | HR policy / marketing campaign discussion | Charting | | General operational / cross-functional | Outlining | --- ## Diagrams ### Meeting Note-Taking Decision Flow ```mermaid flowchart TD A[Meeting Scheduled] --> B{How many agendas?} B -->|Multiple agendas| C{Need hierarchical detail?} B -->|Single deep agenda| D[Charting Method] C -->|Yes - Product/project focus| E[Mapping Method] C -->|Yes - General actionable items| F[Outlining Method] C -->|No - Focus on recall| G[Cornell Method] D --> H[Assign Note-Taker] E --> H F --> H G --> H H --> I[Conduct Meeting ≤30 min] I --> J[Share Notes via Cloud] J --> K[Team Implements Action Items] ``` ### Cornell Method Structure ```mermaid graph TD A[Cornell Method Page Layout] --> B[Cues Section] A --> C[Notes Section] A --> D[Summary Section] B --> B1[Key points recorded AFTER meeting] C --> C1[Detailed points recorded DURING meeting] C --> C2[3-4 notes per cue] D --> D1[Action points distilled from notes] ``` ### Mapping Method Structure ```mermaid graph TD A[Main Agenda] --> B[Sub-Agenda 1] A --> C[Sub-Agenda 2] A --> D[Sub-Agenda 3] B --> B1[Details & Expected Outcomes] B1 --> B2[Discussion Points] C --> C1[Details & Expected Outcomes] C1 --> C2[Discussion Points] D --> D1[Details & Expected Outcomes] D1 --> D2[Discussion Points] ``` --- ## Key Terms - **Cue** – A key point or trigger recorded after a meeting to aid recall and review - **Sub-Agenda** – A specific topic that falls under the main meeting agenda - **Note Ownership** – The practice of assigning a dedicated individual to capture meeting notes - **Actionable Sub-Point** – A specific, executable task derived from a meeting discussion (includes what, when, and who) - **Charting** – A note-taking method focused on deep exploration of a single agenda through sub-topics and point-wise details - **Mapping** – A hierarchical note-taking method that branches a main agenda into sub-agendas with layered details - **Cornell Method** – A three-section note-taking system (cues, notes, summary) designed for structured recall - **Outlining** – A nested list-based note-taking method emphasising actionable outputs under layered agenda items --- ## Quick Revision 1. Meetings should be **≤30 minutes**; longer meetings signal inefficiency 2. **Structured note-taking** is the most critical factor in making meetings productive 3. The **Cornell Method** uses cues (post-meeting), notes (during meeting), and a summary of action points 4. The **Mapping Method** organises notes hierarchically around a main agenda and sub-agendas – ideal for product and project meetings 5. The **Charting Method** focuses on **one deep agenda** with sub-topics and point-wise details – suited for theoretical and HR meetings 6. The **Outlining Method** lists main agendas with nested sub-agendas and **actionable sub-points** – versatile for general business use 7. **No single framework fits all meetings** – choose based on meeting type, number of agendas, and desired output 8. Always **assign a dedicated note-taker** so the meeting leader can focus on discussion 9. Notes must be **shared centrally** (cloud storage) immediately after the meeting 10. Effective implementation requires **choosing the right method, sharing notes, and acting on them promptly**