Our AI invented the numbers. We caught it.
The hosts discuss the importance of double-checking AI outputs and validating information, emphasizing that this is not a new problem but rather a longstanding practice required with any information source. They explore how AI tools can be customized to individual workflows and contexts, arguing that understanding foundational methodology matters more than specific tools.
Summary
The conversation begins with the hosts acknowledging that AI can produce false information, but frame this as an existing challenge rather than a unique AI problem. They stress the importance of verification practices that have always been necessary in academic research, journalism, and professional work. The discussion then pivots to the practical application of AI in productivity workflows, with both hosts sharing examples of how they've integrated AI into their content creation and article writing processes. Rather than using AI as a push-button solution, they emphasize the importance of iteration, customization, and building systems that align with individual expertise and cognitive styles. A significant portion of the conversation focuses on the concept of context and how AI systems become powerful when they have access to complete, well-structured personal context and information. The hosts argue against tool dependency, advocating instead for local control of data while leveraging powerful external services. They introduce the ICO methodology as a foundational, tool-agnostic framework that remains constant even as specific technologies change. The conversation emphasizes that successful AI implementation requires understanding core principles rather than chasing trending tools, and that building effective systems requires sustained focus on specific use cases rather than broad experimentation. Finally, they discuss momentum and compounding effects, noting that their membership growth from 1,000 to 7,000 people has reinforced their methodology while remaining fundamentally unchanged over five years.
Key Insights
- The problem of AI producing false information is not unique to AI—it's a longstanding issue that existed with Wikipedia, word-of-mouth information, and any unverified source, making verification a fundamental practice across domains rather than an AI-specific concern.
- The real power of AI systems comes from having complete, well-structured personal context available—something that has never been possible before in computing history, enabling tools to naturally understand and respond to user needs without extensive explicit instructions.
- Success with AI requires understanding foundational, tool-agnostic principles and methodology rather than becoming dependent on specific tools or following trends, as these core principles remain constant even when underlying technology changes.
- Building effective AI systems requires sustained focus on one specific high-value use case for extended periods (weeks to months) rather than broad experimentation, with parallel testing against existing systems to avoid abandoning proven workflows prematurely.
- The distinction between privacy and dependency is important—one can safely use cloud services without being dependent on them if data can be fully extracted and migrated, maintaining autonomy even while trusting external services.
Topics
Transcript
[0:00] All right, everyone. Welcome back to another session this week with my dear friend Paco. Welcome, Paco. Today we talk about >> well, who would have guessed AI and in the realm of productivity. The thing is I just published a video on YouTube on the main channel um talking about doing research with AI and I think that's something we should talk today about. [0:30] >> Um the video is all about double-checking what you actually get back from AI and this video it was funny enough uh the research for the video itself produced fake numbers for this video. So it is included in the video itself. >> But this is what I did from the get-…
Full transcript available for MurmurCast members
Sign Up to AccessMore from ICOR with Tom | AI Productivity
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.
Claude writes better weekly reports than I did. Here is proof.
The speaker demonstrates how AI-powered weekly reports can automatically synthesize journal entries, notes, and captured content into personalized insights without manual review. Two different implementations are shown—one dashboard-style and one essay-style—proving the same underlying system can be customized to individual preferences and consumption habits.