The Pivot: System vs. Soul

I’ll admit to a specific mistake I made early in my career. I was so convinced that ‘real work’ happened in the project management software that I stopped checking my email for a week. I thought I was being a visionary. I thought I was ascending to a higher plane of productivity. By the 6th day, the CEO walked into my office. He wasn’t angry; he was confused. He had sent me a series of emails outlining a major pivot in our strategy, including 16 pages of notes from a board meeting. None of that was in the ‘system.’ It was all in his ‘sent’ folder. He told me, quite bluntly, that the system was for the people who didn’t need to know why things were changing. The email was for the people who did. That conversation changed how I view data. It made me realize that the more important a piece of information is, the more likely it is to be unstructured.

Think about the last 6 major decisions made at your company. Were they the result of a database query? Probably not. They were likely the result of an email exchange that started at 11:06 PM on a Sunday, involving 6 different stakeholders who were all using different terminology to describe the same problem. The final decision might have been recorded in a formal log, but the 86 reasons why that decision was made-the trade-offs, the fears, the compromises-are all trapped in those individual inboxes. When one of those stakeholders leaves the company, that data doesn’t just become hard to find; it essentially ceases to exist. It’s a form of corporate amnesia that we’ve just accepted as the price of doing business.

I think about that a lot. Our inboxes are archives in the truest, most tragic sense. They contain the sum total of our professional knowledge, yet they are almost entirely opaque. We are sitting on a goldmine of insights-customer sentiment, internal bottlenecks, historical context-but we are trying to mine it with a plastic spoon. We need to stop treating email as a separate, messy category of ‘non-data’ and start recognizing it as the primary source. The challenge isn’t to get people out of email; it’s to build systems that can finally understand what’s happening inside of it.

The Comfort of Chaos

There is a certain comfort in the chaos, though. I find myself clicking through old threads sometimes, like a ghost haunting my own past. I see the 46 emails I exchanged with a colleague who moved to London, and I remember not just the project we were working on, but the specific brand of frustration we shared. It’s human. And maybe that’s the real reason email persists. Databases are cold. They are unforgiving. They don’t allow for the ‘p.s.’ or the ‘hope you’re doing well.’ They don’t have room for the 156-word tangent about a bad sandwich that somehow leads to a breakthrough in a software architecture problem. Our business runs on stories because we are a storytelling species. We haven’t figured out how to put a soul into a spreadsheet yet, so until then, we’ll keep hitting ‘reply all’ and hoping for the best.

I looked at my screen again. The quote still wasn’t there. I realized I was looking for a file named ‘Final Quote,’ but 6 months ago, the vendor had actually sent it as an inline text table because his ‘Word doc was acting up.’ I changed my search to look for the dollar sign followed by the first three digits of the amount I remembered. There it was. Hidden in a thread about a completely different project, tucked under a signature block that was 6 times longer than the actual message. I found the data, but I had to navigate a labyrinth of human error and technological quirkiness to get it. We shouldn’t have to live like this, but as long as our most important truths are written in the language of conversation rather than the language of code, the inbox will remain the most powerful, and most frustrating, database on the planet.