Why ClickUp, Notion, and Asana Keep Failing You
Most project management tool implementations fail because teams pick tools first and force workflows into them, rather than mapping their work structure before implementation. The speaker presents a three-step framework: mapping output elements to tool structure, replicating process maps as workflows, and implementing single source of truth through centralized task communication.
Summary
The transcript addresses why 73% of project management implementations fail within the first year. The core problem is a mismatch between how human brains think about work (in sequential workflows) and how tools conceptualize work (in hierarchical objects like spaces, folders, lists, and tasks). Teams typically open a blank project management tool and become paralyzed by structural decisions—whether to create lists or tasks, how folders differ from spaces—and end up building confusing structures that don't match how their team actually thinks about work. This leads to adoption failure where teams continue using Slack and Google Sheets instead of the official tool.
The speaker explains that different tools use different terminology for the same concepts (ClickUp's "list" equals Asana's "project"), which compounds confusion when teams switch tools. The real issue isn't learning tool features but having a clear universal language for work structure.
The framework presented consists of three steps: First, map output elements to tool structure (goals at the top, projects/work streams/operations as folders, specific workflows as lists, and work as tasks). Second, replicate the process map as a workflow inside the tool by creating lists with statuses matching workflow steps, allowing visualization of work progression. Third, enforce single source of truth by requiring all task-related conversations to happen in task comments rather than scattered across Slack, Teams, email, and other platforms.
The speaker cites research showing teams with clear structural frameworks before implementation have 3.5 times higher adoption rates. The transcript concludes with a real example: implementing this structure in a large corporate environment allowed managing over 16,000 tasks per month in Asana without failures.
Key Insights
- 73% of project management implementations fail within the first year because teams pick tools first and force workflows into them, rather than mapping their work structure beforehand
- The fundamental disconnect is that human brains think in workflows (step-by-step, cause and effect) while tools think in objects (hierarchies of workspaces, folders, lists, tasks) with no automatic translation between the two mental models
- Teams with clear structural frameworks before tool implementation achieve 3.5 times higher adoption rates compared to teams who figure out structure as they go
- Different tools use inconsistent terminology for identical concepts—what ClickUp calls a list, Asana calls a project; what Notion calls a database, ClickUp calls a table view—causing teams to incorrectly believe switching tools will solve their problems
- The speaker implemented a structure that allowed managing over 16,000 tasks per month in Asana without failures by enforcing that all task-related communication happens in task comments rather than scattered across Slack, Teams, and email
Topics
Transcript
[0:00] Here's something most teams get backwards. They pick a tool first, then try to force their work into it. And that's why 73% of project management implementations fail within the first year. But by the end of this video, I'll show you the exact framework for translating your process maps into any project management tool. If you just mapped your workflows and you're starting at a blank tool thinking, where do I even start? This is your answer. Here's what happens after you finally map out your workflows. You're excited. [0:30] You've got this beautiful process map on paper on a whiteboarding tool like Miro. You can see exactly how work should flow. And then you open ClickUp or…
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.