The blue light of the 46th open browser tab is doing something rhythmic to my left eyelid, a sort of desperate SOS pulse that matches the way I’m currently digging through the digital remains of a project that was supposed to ship 16 days ago. I am looking for a ghost. Specifically, the ghost of a decision made by a stakeholder who is currently on a plane somewhere over the Atlantic. Everyone remembers the decision. Sarah says it was in the Slack channel for the 2006 rebrand. Mark swears it was an Outlook invite attachment from the 6th of last month. I am currently staring at a WhatsApp thread that contains 66 messages about lunch orders, but not a single word about the architectural shift we are supposedly implementing. This is the moment where the friction of modern work turns into a physical weight. It’s that familiar, stinging sensation of knowing the answer exists-it was typed, it was seen, it was acknowledged with a ‘thumbs up’ emoji-but it has been swallowed by the platform residue.

I recently stood in the middle of my kitchen, staring at the toaster, wondering why I had walked in there. I had a specific purpose 16 seconds prior, but the transition from the hallway to the tile floor wiped the cache. This is exactly what we are doing to our organizations. Every time we move a conversation from a shared document to a quick ‘DM’ or a frantic huddle in a different app, we are walking through a doorway that wipes the collective memory. We think we are being agile. We think we are moving at the speed of light. In reality, we are just scattering the puzzle pieces across 106 different rooms and then wondering why the picture looks incomplete. My friend David N. knows this better than anyone. David is a fire cause investigator, a man who spends his days looking at the blackened skeletons of buildings to find the one 6-inch stretch of wire that failed. He told me once that the hardest fires to investigate aren’t the ones where everything is leveled. The hardest ones are ‘fragmented burns’-where the fire jumped, leaving patches of unburnt material in between the destruction. It creates a false narrative of what happened first.

Communication in a fragmented institution is a fragmented burn. We have these ‘islands of clarity’ trapped inside private channels and siloed apps, surrounded by the charred remains of context. You see a message that says ‘Approved,’ but the 26 messages of context that led to that approval are locked in a thread you weren’t invited to. So you proceed based on a half-truth. In David N.’s world, a false lead can mean the difference between an insurance payout and a criminal charge. In our world, it just means 56 hours of wasted development time because we built the wrong feature based on a ‘yes’ that actually meant ‘yes, but only if we ignore the previous 16 constraints.’ We are obsessed with the ‘channel’ as a solution, but the channel is often the catalyst for the chaos. We add a new one because the old one feels ‘cluttered,’ not realizing that clutter is just the natural byproduct of humans trying to coordinate without a central gravity.

When you multiply the avenues of input, you don’t increase the flow of information; you decrease the probability of retrieval. It is a mathematical certainty that remains ignored by every manager who thinks ‘let’s just start a Slack group for this’ is a valid project management strategy. David N. showed me a photo from a 2016 investigation of a warehouse fire. To the untrained eye, it was just ash. To him, the way the steel beams had warped at exactly 1006 degrees told a story about where the oxygen was coming from. Our digital ‘oxygen’ is the context. When the context is split across Teams, Notion, and a stray email thread from 26 days ago, the project begins to warp. You can’t see the warping in real-time. You only see it when the product launches and the users ask why the ‘Submit’ button is 6 shades of the wrong blue and the API doesn’t talk to the database. At that point, the post-mortem becomes a frantic search for the original sin, the moment where the ‘truth’ was decided and then immediately hidden.

We have reached a point where the average knowledge worker spends 36% of their week just looking for the information they need to do the remaining 64% of their work. That is not a productivity hurdle; it is a systemic collapse. We are operating in a state of perpetual reconstruction. Every morning, we wake up and try to piece together what happened yesterday by scrolling through a ‘Timeline’ of notifications that are sorted by ‘recency’ rather than ‘relevance.’ The algorithm of our work lives is biased toward the loudest, most recent ping, not the most important structural decision. This is where the exhaustion comes from. It isn’t the work itself; it’s the mental tax of maintaining a 3D map of where every piece of the project is currently hiding.

I asked David N. how he keeps track of his findings when he’s on a site. He didn’t say he used a ‘suite of cutting-edge investigative apps.’ He told me he uses a single physical ledger and a camera. He creates one stream of reality. If it isn’t in the ledger, it didn’t happen. There is something profoundly liberating about that level of constraint. In our digital environments, we have the opposite: infinite space and zero friction. Because it’s so easy to start a new channel, we do it for every 6-person meeting. This is the point where most people realize that the ‘best of breed’ app strategy is actually just a slow-motion car crash, a realization that usually leads back to the necessity of a unified platform like ems89 where the architecture doesn’t fight the user. When the environment is centralized, the ‘archaeology’ of a decision doesn’t require a shovel and a brush. It just requires a look at the ledger.

The resistance to centralization usually comes from a desire for ‘autonomy.’ Teams want to use the tools they like. But autonomy without legibility is just a fancy word for isolation. If your team is moving fast in a black box, the rest of the company is just guessing at your trajectory. I’ve made this mistake myself. I once ran a project where I let every sub-team pick their own ‘vibe’ for communication. One team used Discord, another used Trello, and I tried to bridge the gap with a series of 16-page weekly reports. By week 6, I realized that I wasn’t a manager; I was a translator. I was spending my entire life translating the ‘vibes’ of three different platforms into a single language that the executives could understand. I was the single point of failure because I was the only one who had the ‘map’ of where all the truth was buried. When I got sick for 6 days, the project ground to a halt. Not because the people weren’t working, but because they couldn’t find the ‘latest version’ of anything.

The Cost of Fragmentation

David N. calls this ‘total consumption.’ It’s when a fire becomes so hot that it consumes the very evidence of its origin. In a corporate sense, total consumption happens when the volume of communication becomes so high that nobody can find the original ‘why’ behind any task. We are just reacting to the heat. We are answering the pings because they are there, not because they move the needle. We have replaced progress with ‘presence.’ If I am active in 46 channels, I must be doing something important, right? Wrong. You are likely just a human router, passing fragments of half-baked ideas from one silo to the next. The real work is the thing that requires 6 hours of uninterrupted focus, the thing that is impossible to achieve when you are terrified of missing the one decision that might be made in a random thread while you are focused.

If we want to stop this, we have to stop treating communication as an ‘add-on’ and start treating it as the core infrastructure of the work itself. This means making the hard choice to kill the channels that don’t serve the truth. It means deciding that ‘if it isn’t in the project doc, it doesn’t exist.’ It sounds rigid. It sounds like it might slow things down. But as David N. would tell you, a controlled burn is always better than a wildfire. You might move 6% slower in the beginning, but you won’t spend 206% more time later trying to find out who authorized the change that broke the system. We need to value the ‘searchability’ of our decisions more than the ‘convenience’ of our conversations.

I eventually remembered why I went into the kitchen. I needed a glass of water. But by the time I remembered, I had already opened the fridge, moved a jar of pickles, and checked the time on the oven (it was 2:06 PM). I had created a whole series of unnecessary actions just because I lost the initial thread of intent. Our companies are doing this on a global scale. We are opening the digital fridge 46 times a day, moving the ‘pickle jars’ of irrelevant data, and forgetting that we just needed a simple sip of clarity. The solution isn’t a better fridge. It’s a clearer memory. And in the digital world, memory is only as good as the place where you choose to store it. We have to choose one place. We have to make it the reality. Anything else is just smoke, as David N. puts it, looking at the ash and hoping for a miracle.