David’s index finger is hovering, trembling slightly, over the “Save & Close” button that remains a stubborn, translucent gray until the 19th required field in the CRM is satisfied. He has been on this screen for 9 minutes. The customer call itself-the actual human interaction where a person expressed a genuine need for a solution-only lasted 9 minutes. The symmetry would be poetic if it weren’t so soul-crushing. David is a top salesman, but if you looked at his screen right now, you would think he was a data entry clerk working a graveyard shift in a windowless basement. He has 9 tabs open. One is the official Salesforce instance, a labyrinth of custom objects and mandatory dropdowns that feel like they were designed by someone who hates sunlight. The other window, hidden behind a spreadsheet of 29 internal KPIs, is his personal physical notepad.

We have spent the last 29 years optimizing the way we report work, but we have somehow forgotten to optimize the work itself. We have built cathedrals of data on foundations of exhaustion.

The Reporting Paradox and the GPS Hammer

River C.M., a seed analyst I’ve worked with for what feels like 9 lifetimes, calls this the “Reporting Paradox.” River spends their days looking at the guts of startups, the kind of companies that raise $9,999,999 and immediately spend $499,999 of it on a software stack that requires a full-time priest to maintain. River has this theory that as soon as a tool becomes “Enterprise Ready,” it ceases to be useful to the person actually using it.

I’m writing this while feeling particularly raw. This morning, I cried during a commercial for a brand of orange juice-the one where the grandfather teaches the kid to peel the fruit in one long spiral. It was so simple. So tactile. It reminded me of a time before we mediated every single human interaction through 9 layers of middleware. We are losing the “one long spiral” of our workflows. Instead, we are chopping the fruit into 399 tiny pieces and logging each one in a separate database table.

The Shadow Organization

In the shadow of these massive, clunky systems, a second organization has formed. It is the Shadow Organization, and it’s where the real work happens. It lives in unsanctioned Excel sheets, in private Slack channels where people actually solve problems, and in the physical notebooks of people like David.

The official CRM says the sales cycle is 49 days long because that’s how long it takes to move the digital cards through the digital columns. In reality, the deal was closed on day 9 over a cup of coffee, but the software didn’t have a field for “human connection.” We’ve optimized the manager’s dashboard at the direct expense of the employee’s sanity. If a manager wants to know the “Probability of Close” to the 9th decimal point, the salesperson has to spend 29 minutes calculating it instead of finding the next lead. It’s a wealth transfer of time, and the exchange rate is abysmal.

We are effectively taxing our most productive people to provide data to our least productive departments.

The Collective Hallucination

River C.M. once showed me a dashboard at a Series B startup that had 59 different widgets. It was beautiful. It looked like the stickpit of a spaceship. But when I asked River where the data came from, they laughed a dry, rattling laugh. “It’s all fake,” they said. “The sales team just selects the first option in every dropdown so they can get back to their actual jobs. The data is 99 percent fiction, but the board loves the colors.”

I’ve made this mistake myself. I remember trying to track my own creative process using a complex relational database. I had 9 different tags for “Mood” and 19 different categories for “Inspiration Type.” I spent more time tagging my thoughts than having them. I was a seed analyst of my own soul, and the data was pointing toward a total bankruptcy of meaning. I eventually deleted the whole thing and went back to a plain text file. The relief was physical. It felt like taking off a pair of lead boots.

Reframing the Tool’s Purpose

We need to start asking a different set of questions when we buy or build tools. Not “What data does this give the VP of Sales?” but “Does this tool make the salesperson feel like a more capable human being?“

We should be looking for tools like

Aissist that actually focus on the operational flow, reducing the friction that eats away at our focus. We need tools that act as silent partners, not demanding taskmasters. If a tool requires me to change the way I think to accommodate the way it stores data, the tool is broken, no matter how many 9s of uptime it promises.

The irony is that we have the technology to make this better. We have the ability to automate the reporting, to let the machines do the chores of data entry so the humans can do the work of humaning. But that requires a level of trust that most organizations aren’t ready for. They would rather have 89 percent of a salesperson’s time spent on accurate-looking lies than 100 percent of their time spent on unrecorded truths.

The Anxiety of 79 Micro-Services

I think about that orange juice commercial again. The simplicity of the task. The directness of the result. There was no reporting on the peel. There was no dashboard for the juice. There was just the act and the outcome. In our drive to digitize everything, we’ve lost the ability to value anything that can’t be expressed as a bar chart.

River C.M. is currently auditing a firm that uses 79 different micro-services to manage their customer lifecycle. Each service has its own login, its own quirks, its own 9-page privacy policy. The employees are vibrating with anxiety. They spend 49 percent of their day just logging in and out of things. It’s a digital assembly line where the conveyor belt moves faster than the workers can reach the parts. It’s efficient on paper and catastrophic in practice.

I’m not saying we should go back to the Stone Age. I love a good data set. But I want the data to be a byproduct of work, not the purpose of it. I want David to be able to write “Susan needs help” and have the system understand, support, and facilitate that help without requiring him to navigate a 9-layer hell-scape of buttons.

Building for Human Capability

We have to stop building software for the person who wants to watch the work, and start building it for the person who has to do it. Until we do, we will continue to live in this strange, flickering reality where the spreadsheets are perfect and the people are exhausted.

David closes his laptop at 5:59 PM. He feels like he hasn’t accomplished anything, even though the CRM says he updated 29 records. He goes home and looks at his physical notepad. He sees the three words: “Susan needs help.” He realizes he forgot to actually call her back because he was too busy logging the fact that he intended to. This is the world we have built. It is 9 parts process and 0 parts soul. It’s time we stopped clicking and started working again.