Think about the last task you completed. Not the result — the journey. Where did it start? In an email, a message, your own idea? Where did it go next? How many tools did it touch between appearing and being finished? If you reconstruct that journey honestly, you’ll probably discover that your information travels through a labyrinth of applications, formats and channels far more complex than necessary. The flow map makes that labyrinth visible — and once you see it, you can simplify it.
Your Information Has A Journey
Every piece of information in your digital life follows a journey. An idea is born, captured, developed, executed, archived or discarded. A message arrives, gets processed, generates an action, that action produces a result and that result gets communicated. A file gets created, edited, shared, reviewed and stored.
In an efficient system, that journey is short, predictable and without detours. You know where information enters, you know how you process it and you know where it ends up. No surprises, no bottlenecks, no holes where things get lost.
In a system with too many tools, the journey is long, unpredictable and full of handoffs. Information jumps from one app to another, changes format with every jump, loses context with every transfer. Sometimes it never reaches where it needs to go. Sometimes it arrives duplicated. Sometimes it arrives so late it’s no longer useful.
The flow map is simply a diagram — it can be as simple as a sketch on paper — that shows the real journey your information follows. Not the ideal journey, not the one it should follow, but the one it actually follows day to day. It’s an observation exercise, not a design one. The design comes later.
How To Trace Your Map
Choose three or four flows that represent your typical work. For example:
- How you manage a project from start to finish.
- How you process your email.
- How you capture and develop an idea.
- How you collaborate with someone on a document.
For each flow, reconstruct the path step by step, noting every tool the information touches:
Example: managing a project.
- The project starts as a message in Slack → 2. I note it as a task in Todoist → 3. I create a document in Google Docs → 4. I share the link by email → 5. Comments arrive via Slack and email → 6. Revisions happen in Google Docs → 7. The final result is stored in Drive → 8. I notify delivery via Slack.
Count the tools: Slack, Todoist, Google Docs, email, Google Drive. Five tools for a single flow. And in every transition between tools there’s a risk of loss, delay or duplication.
Now do the same with your other flows and draw the connections. What you get is your flow map — a visual representation of how your information travels through your digital ecosystem.
The Most Common Bottlenecks
When you look at the map, certain problematic patterns appear again and again:
Multiple entry points. New information arrives through too many channels: email, chat, messages, app notifications. Each channel is an open tap, and if you don’t funnel them towards a single processing point, you lose things between the cracks.
Manual handoffs. Moments where you are the bridge between two tools that don’t connect to each other. You copy information from one and paste it into another. You rewrite in one what already exists in another. You send via one channel what arrived via another. Every manual handoff is an opportunity for error, delay and loss of context.
Dead ends. Places where information enters but never leaves. That “read later” folder you never review. That ideas list you never process. That bookmark manager with hundreds of links you never revisit. These aren’t useful tools — they’re information graveyards with good intentions.
Loops. Circular journeys where information passes through a point it’s already been through. You send something by email, it’s forwarded back with comments, you pass it to the document, someone comments on the document, you receive the notification by email. Information goes round without advancing.
Chokepoints. Points where everything accumulates because processing is slower than input. Your inbox is the classic example: information enters faster than you can process it, and what you don’t process sinks beneath the new.
From Diagnosis To Action
The flow map isn’t an aesthetic exercise — it’s a diagnostic tool that points to exactly where to intervene. Every bottleneck you find is a concrete point for improvement.
For multiple entry points: reduce the input channels to a minimum. Establish clear rules about which channel each type of information should arrive through. The urgent via one, the important via another, the dispensable via none.
For manual handoffs: look for ways to eliminate them. Sometimes the solution is an automatic integration. Other times, the solution is more radical: eliminate one of the two tools and do the entire flow in just one.
For dead ends: accept that if information doesn’t advance, you probably don’t need it. Eliminate the dead end or, at minimum, establish a periodic review that empties it.
For loops: identify the point where the loop breaks and force the information to advance instead of spinning. Usually, the loop breaks when someone makes a decision instead of forwarding.
For chokepoints: either reduce the input or increase the processing capacity. Reducing the input is usually more effective and more sustainable.
The ultimate goal is a simple map: few entry points, few tools, short linear journeys, no dead ends. You won’t reach that map in a day. But having it as a reference gives you a clear direction for every decision you make about your tools from now on.
The flow map converts a fuzzy problem — “I feel like my system doesn’t work” — into a visible, concrete one: “here is where it gets stuck, here is where it gets lost, here is where there’s one tool too many.” And visible, concrete problems are the ones that get solved.
