The Process Maps That Took Me From Solo to Team (Step by Step)
Process mapping—not tools and automation—is the foundation of scalable systems. By visualizing workflows with clear responsibilities, constraints, and time allocations, teams can identify inefficiencies, make informed automation/delegation decisions, and eliminate bottlenecks that prevent growth.
Summary
The speaker shares 8 years of experience building systems in corporate environments and coaching thousands of professionals, arguing that most productivity stalls because people focus on tool stacking rather than foundational clarity. Real systems are built on three elements: clarity, constraints, and repeatable workflows that align teams.
The core methodology involves creating simplified workstreams—visual maps of sequential process steps with time estimates—then adding workflow responsibilities showing who does what. This reveals hidden complexity: for example, a simple "client sales call" actually comprises offer free call, call preparation (30 min), booking, taking notes during call (15 min), and follow-up (30 min). When scaled to 10 calls per week, this becomes 20+ hours of work, exposing why solopreneurs hit scaling ceilings.
Once workflows are visualized, informed decisions about automation versus delegation become possible. A back-and-forth email scheduling process can be automated with Calendly; meeting notes can be auto-transcribed and summarized with AI; follow-ups can be delegated to assistants or automated. The speaker emphasizes optimization (rethinking the workflow itself) over just automating existing steps.
Two real-world examples demonstrate impact: First, in the Paperless Movement, the speaker mapped out interview workflows involving multiple employees, delegating editing, social media posts, and blog creation while reserving only the interview itself for the founder—eliminating hours of preparation and follow-up work. Second, in a 300,000-person corporation, the speaker inherited a 5-person IT team scattered across 150 projects, all overworked. By mapping the medicine packaging line project workflow across multiple departments, the speaker discovered that 15 years of accumulated work had been incorrectly assigned to a single person who became a bottleneck. After reassigning responsibilities to appropriate departments based on the process map, the team's workload dropped 100% (for work not actually theirs), cross-department performance increased 40%, project communication moved into a single source of truth (Asana), anxiety dropped due to clarity, meetings reduced by 50%, and the system eventually scaled to handle 16,000 tasks monthly across 1,000+ people.
Key Insights
- Real systems are not tool-dependent; they are built on clarity, constraints, and repeatable workflows that get everyone on the same page, not on stacking tools and automations.
- When a solopreneur adds time estimates to individual workflow steps (call prep 30 min, call 15 min, follow-up 30 min), scaling to 10 calls per week reveals the true cost of the process is 20+ hours, exposing why they hit a scaling ceiling.
- A five-person IT team working across 150 global projects in parallel became massively overworked because they were scattered; mapping the actual workflow revealed which work belonged to which departments, allowing reassignment and 40% performance improvement.
- One person after 15 years became a bottleneck by voluntarily taking on work that belonged to other departments; when responsibilities were clarified through the process map and work was reassigned, the team's workload dropped 100% for work not actually theirs.
- Moving all project communication into a single source of truth (Asana) with clear process maps eliminated fingerpointing because responsibilities were crystal clear and reduced meetings by 50% because context was always available in task discussions.
Topics
Transcript
[0:00] how we boosted cross department performance by over 40% in a system handling 16,000 tasks a month together with a thousand people. Most people think system building means stacking tools and automations. But that's exactly why their productivity and their team's productivity keeps stalling. After 8 years building systems in corporate and coaching thousands of professionals over the years, I have learned that real systems aren't tool dependent. They are built on clarity, constraints, and repeatable workflows [0:30] that get everyone on the same page. In this video, I'll show you the simplest way to design a high impact process map, and then walk you through two real world examples that prove how scalable this is. First, I show…
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.