New Shiny App Syndrome Ends with This Map
The video introduces the ICO framework, a Venn diagram-based map for visualizing your productivity tool stack across four quadrants: personal/business and information/action. The presenter demonstrates how to categorize tools as core applications, satellite apps, or utility apps, and how to identify redundancies and gaps in your system. The goal is to build tool-agnostic clarity about your productivity system rather than chasing new apps.
Summary
The video addresses 'shiny object syndrome' — the tendency to constantly seek new productivity tools — by arguing that the root problem is typically a lack of understanding of one's overall productivity system, not a lack of tools. The presenter introduces the ICO framework, a Venn diagram composed of four overlapping areas: Personal Knowledge Management (PKM), Personal Project Management (PPM), Business Project Management (BPM), and Business Knowledge Management (BKM). The left side of the diagram represents personal use, the right side represents business use, the top relates to information, and the bottom relates to action. 'Business' is defined broadly to include anything shared with a team, clients, or used to organize a business — even for solopreneurs.
The presenter walks through a digital implementation of this map, showing how tools like ClickUp, Gmail, Google Calendar, Todoist, and a PKM vault can be dragged and dropped into the appropriate quadrants. Placing a tool in the center of all four circles means it is used across every area of the system. Tools placed inside the circles are classified as 'core applications,' which are difficult to remove because they store critical, hard-to-migrate data. Examples include Gmail, which could contain decades of information.
The framework also introduces two additional tool classifications beyond core apps. 'Satellite apps' are tools that depend on a core application to function — like Superhuman, which requires Gmail access — and are easier to replace since data lives in the core. 'Utility apps' are standalone tools that improve workflows without storing essential data or directly integrating with core tools; examples include Raycast and Claude. Tools like Sansama are shown as potentially being either satellite or core apps depending on whether data is stored within them.
Each tool on the map can be clicked to access a detail page where users can specify their integration level (testing, needs alternative, or deeply integrated), cost, devices used, and secondary use-case categories aligned with the ICOR methodology (e.g., idea incubator, team communication, goal setting, project management). This granular categorization helps users identify gaps — for instance, if a PKM tool doesn't cover quick capture, a tool like Tana can be added specifically for that purpose. The presenter emphasizes that this map serves as a single source of truth for understanding one's tool stack and can even inform AI assistants via an MCP connector about how tools are being used.
Key Insights
- The presenter argues that shiny object syndrome stems not from a lack of tools but from a lack of understanding of one's tool-agnostic productivity system, making tool-switching often counterproductive.
- The presenter defines 'core applications' as tools placed inside the ICO circles that are very hard to remove because switching away from them risks losing significant stored data — citing Gmail as an example where decades of information could be lost by migrating to Outlook.
- The presenter distinguishes satellite apps from core apps by explaining that satellite apps — like Superhuman relative to Gmail — cannot function independently and wrap around a core, making them easy to swap out without data loss.
- The presenter classifies tools like Sansama as potentially satellite or core depending on whether data is actually stored in them, noting that if Sansama only represents data from other sources, removing it leaves all underlying data in the core apps intact.
- The presenter explains that the tool detail pages — where secondary categories like 'idea incubator,' 'team communication,' and 'quick capture' are filled in — allow users to spot gaps in their system and deliberately add tools to cover missing functions, such as adding Tana specifically for quick capture.
Topics
Full transcript available for MurmurCast members
Sign Up to Access