Stop Losing Your Best Ideas: How to Take Notes You'll Actually Use
Most people's notes are never reviewed or used because they're scattered across disconnected tools and folders. The solution is a personal knowledge management framework that categorizes information into four types (PKM, BKM, PPM, BPM) and links every note directly to projects, goals, or tasks for automatic retrieval and actionable value.
Summary
The speaker identifies a critical problem: while people take notes frequently, 80% of those notes are never reviewed again, creating an illusion of productivity without actual value. The traditional approach of capturing ideas in whatever app is convenient and saving them in isolated folders leads to lost insights and inaccessible information. When needed weeks later, these scattered notes become impossible to find despite existing somewhere in digital storage.
The core issue is that notes exist in isolation from the work they're meant to support. The solution is a framework called 'Capturing Beast' built on four categories of information: PKM (personal knowledge management for personal insights), BKM (business knowledge management for team information), PPM (personal project management for personal tasks), and BPM (business project management for team tasks). When capturing any note, the user should ask two questions: Is this personal or team? Is this information or action?
The framework comprises four key practices: First, understand the four information types and categorize accordingly. Second, use a fast intermediate capture tool (phone notes, voice memos) but process these captures daily into a single source of truth. Third, link every note to a specific project, goal, or task—never save standalone floating notes. This creates automatic context so relevant notes appear when working on related projects months later. Fourth, capture only actionable insights that change decision-making or thinking, not exhaustive documentation.
The speaker claims this system transforms knowledge management from scattered collection to compounded knowledge, where each insight builds on previous ones and remains accessible within the context of actual work.
Key Insights
- 80% of notes taken are never reviewed again, meaning most note-taking creates an illusion of productivity while providing zero actual value
- When notes are linked directly to work projects and goals, retrieval becomes automatic rather than requiring users to search through folders and apps
- The speaker's implementation of this framework at both their own organization and the Paperless Movement resulted in members stopping idea loss and starting knowledge compounding
- Asking two questions when capturing notes—'Is this personal or team?' and 'Is this information or action?'—eliminates paralysis about where to save information
- The rule for what to capture is that if information doesn't change what someone does or how they think, it shouldn't be saved, as the goal is building an actionable knowledge base rather than a library
Topics
Transcript
[0:00] I used to have brilliant insights while working on projects, then forget them 20 minutes later. Or I'd save random notes everywhere and never find them again when I actually needed them. And here's what's crazy. I wasn't lazy about taking notes. I was taking the wrong notes in the wrong places. By the end of this video, I'll show you the exact note takingaking framework we use at the Papless Movement and thousands of other professionals worldwide. How to capture only what matters, where to save it, so you'll actually find it, and how to turn [0:30] notes into actions instead of digital clutter. If you take notes, but never use them, this changes everything. So, here's what…
Full transcript available for MurmurCast members
Sign Up to AccessMore from ICOR with Tom | AI Productivity
Claude sucks. And here is why.
This video explores why Claude and other AI models produce inconsistent results, examining how model selection (Haiku vs Sonnet vs Opus vs Claude 3.5 Fable), effort levels, prompt clarity, and system context dramatically affect output quality. The speaker demonstrates these differences through a Venn diagram creation task and advocates for using organized folder systems with documented SOPs and code-based solutions to ensure consistent AI performance.
Claude can now prompt its own SESSIONS. I built the boss.
Claude now has the ability to interact with multiple sessions, allowing a streamlined orchestration of tasks through an agent called Larry. This integration can simplify task management and enhance productivity by enabling a single main session to oversee various sub-sessions or tasks.
I switched off Claude's memory. My folder does it better.
Tom explains why he disabled Claude's native memory feature and instead built a local folder-based system (myPKM) to maintain persistent context with AI agents. He shares an audit revealing systemic issues like contradictory documentation, forgotten rules, and parallel session conflicts, then outlines how to systematically fix these problems using the ICOR productivity methodology.
I do not download invoices anymore. My folder and Claude do it.
The speaker demonstrates how he uses AI (Claude) integrated with his local folder system to automate invoice collection for his accountant, downloading 36 invoices in 5 minutes with minimal manual intervention. He explains his AI team methodology, work streams, and how persistent local knowledge bases enable AI to handle recurring tasks independently without constant re-explanation.
Claude finished the work. Then I lost it in the chat.
A creator demonstrates a comprehensive local-folder-based system for managing AI-generated deliverables asynchronously, featuring an interactive browser interface that tracks decisions, changes, and conversations without relying on external databases or web applications. The system enables collaborative editing, visual annotations, and automatic context preservation across multiple parallel AI projects.