Map tool stack as a graph

When This Fires

• When auditing your tool stack for optimization opportunities
• When onboarding a new tool and deciding where it fits in your existing stack
• When data feels scattered across too many locations
• Complements When two tools hold the same data, designate one canonical… (canonical designation), Automate the single highest-frequency manual data transfer… (automation priority), and One tool as hub for thinking/synthesis, others as spokes… (hub-and-spoke) with the diagnostic that identifies where to apply each

Common Failure Mode

Tool-list thinking: maintaining a list of "my tools" without understanding the data flows between them. The list tells you what you have; the graph tells you how it works. Optimization requires understanding flows, not inventory.

The Protocol

(1) Draw each tool in your stack as a node (box or circle). (2) For every data transfer between tools, draw an edge (arrow) labeled with: Type (manual or automated), Frequency (daily, weekly, monthly), Data (what's being transferred: tasks, notes, events, files). (3) Identify optimization targets: High-frequency manual edges → automation candidates (Automate the single highest-frequency manual data transfer…). Multiple edges between the same nodes → potential consolidation. Nodes with the same function → single-source-of-truth candidates (When two tools hold the same data, designate one canonical…). The most-connected node → your natural hub (One tool as hub for thinking/synthesis, others as spokes…). (4) Use the map to prioritize: automate the thickest manual edge first, resolve the most critical redundancy second. (5) Update the map when adding or removing tools. The map is a living architecture document, not a one-time exercise.