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
Your knowledge should outlive every AI tool you use.
The speaker clarifies the distinction between the ICOR methodology (a tool-agnostic productivity framework) and its implementations like the ICOR for Life scaffold and myPKA AI team, emphasizing that users can adopt the core principles in any tool they prefer. They announce plans to restructure their membership platform by separating these components to reduce confusion and help users understand they're not locked into specific tools or systems.
Claude alone took 3 minutes. With Jev, 21 seconds.
A demonstration comparing AI slide deck creation using Claude alone versus Claude integrated with Jev, showing that the hybrid approach completed the task in 21 seconds for $8 with proper formatting, while Claude-only took 3+ minutes and cost $49 with poor formatting.
Why I stick to Claude for work (most of the time)
The creator demonstrates why Claude is their preferred AI for work by comparing it with ChatGPT across multiple tests, showing that Claude better adheres to custom instructions and agentic workflows defined in local folder structures. The key advantage lies in using organized, LLM-agnostic folder systems with agents.md files rather than relying on auto-memory features.
You are using the wrong Claude for work! (Here is proof)
A video demonstrating that Claude Code is significantly more powerful than Claude Cowork for professional knowledge workers, showing how Claude Code better understands folder context, enforces safety rules, orchestrates sub-agents with different models, and creates persistent file outputs rather than temporary artifacts.
Obsidian is the tool I teach in. Keep the one you have.
The creator addresses criticism about switching to Obsidian after previously promoting other tools, clarifying that his tool-agnostic ICOR methodology remains unchanged and that Obsidian is simply an interface layer for his folder-based system. He emphasizes that the underlying folder structure, AI automation, and productivity principles are identical regardless of which tool visualizes the content.