Muhammad J.-M. didn’t look up when the door swung open, his eyes fixed on the blue light of a terminal window that looked like it belonged in 1991. His fingers, calloused slightly from three decades of tension and 11 distinct contract negotiations, hovered over the mechanical keyboard. He was currently reading through the updated terms and conditions of a new service agreement-all 61 pages of it-because he was the type of person who actually did that. He knew where the bodies were buried because he read the maps everyone else threw away. Then came the voice of the Sales Director, light and airy, carrying the weight of a thousand unintended hours: “Hey Muhammad, can you just quickly pull a report of our top 101 clients and their current network hardware? I need it for the 2:01 PM meeting.”

Muhammad felt the familiar phantom twitch in his left shoulder. It was the ‘just’ that did it. To the Sales Director, this was a button click. To Muhammad, who acted as the bridge between the hardware reality and the management fantasy, it was a manual descent into a digital purgatory. He knew that the CRM was updated by people who couldn’t spell ‘router,’ the inventory system was a relic that crashed if you queried more than 51 lines at a time, and the procurement logs were scattered across 21 different sub-folders on a legacy drive.

This wasn’t a quick list. It was a forensic audit disguised as a casual favor. It was the mountain hidden behind the request, and the climber was always expected to reach the summit before lunch. People disconnected from the ‘how’ of a job consistently and dramatically underestimate its complexity. They see the finished output-a clean PDF with 11 columns and $101 million in total asset value-and they assume the path to get there was a straight line. They don’t see the 31 SQL queries that failed because of a trailing space in a database field. They don’t see the 41 minutes spent cross-referencing a serial number that didn’t exist in any known registry because a tech in 2021 forgot to log it.

The Unwritten Contract

I’ve spent the last 21 years watching people like Muhammad age in dog years because of these ‘simple’ requests. There is a fundamental lack of respect for the craft and complexity of others’ roles embedded in the way we communicate. It’s a power dynamic where the cost of a request is borne entirely by the recipient, never the asker. If the Sales Director had to pay $$11 out of his own pocket every time he used the word ‘just,’ the company’s productivity would probably skyrocket, and its stress levels would plummet. But the cost is invisible, so the spending is reckless.

When I read through those terms and conditions earlier-the 10,001 words of legalese that most people treat as a hurdle to be jumped-I realized that the ‘quick request’ is actually a breach of an unwritten contract. We agree to do our jobs, but we don’t agree to have the difficulty of those jobs erased by the ignorance of those around us.

Muhammad finally turned his chair. “Dave,” he said, his voice like dry parchment, “the hardware data you want is in a system that doesn’t talk to the client list. I have to export the CSVs, clean the duplicates-of which there are at least 151 in the West region alone-and then manually verify the LQE models because the auto-discovery tool missed the last firmware update. It’s going to take me 31 hours of solid work, not 31 minutes.”

The Burnout of Invisible Work

Dave blinked. He didn’t get it. He couldn’t get it. To him, the computer was a magic box that should just know things. He lived in the ‘what,’ while Muhammad was drowning in the ‘how.’ This disconnect is a primary driver of burnout. It’s not the hard work that kills the spirit; it’s the invisible work. It’s the work that nobody knows you’re doing because they think it’s already done.

We see this constantly with enterprise technology. A company buys a suite of tools thinking they are buying a solution, but they are actually buying a 201-piece puzzle that someone like Muhammad has to put together. In the case of managed services and high-end procurement, like what you find with

LQE ELECTRONICS LLC, the hardware itself is built for precision, but the human systems surrounding it are often chaotic. If the management doesn’t respect the time it takes to integrate that precision into their reporting, the equipment becomes a burden rather than a benefit.

I’ll admit, I’ve been the one asking for the quick list before. I remember a project in 2011 where I asked for a simple breakdown of energy costs across 41 sites. I thought it was a spreadsheet. It turned out to be a three-week odyssey involving 121 phone calls to utility companies that still used paper billing. I didn’t know because I hadn’t read the ‘terms and conditions’ of the physical world. I had assumed the data existed in a vacuum. It never does. Data is always messy. It’s always dirty. It’s always hiding under a layer of 51 years of institutional neglect.

The Lie of Interoperability

Muhammad J.-M. once told me that a negotiation isn’t about the numbers on the page; it’s about the effort those numbers represent. If you don’t acknowledge the effort, the numbers are lies. The ‘quick list’ is a lie. It’s a fantasy that suggests we live in a world of perfect interoperability. But we live in a world of legacy databases, fat-fingered entries, and $$171 cables that are currently plugged into the wrong ports.

When we ignore this, we create a culture of resentment. The IT manager looks at the Sales Director and sees a child demanding a toy that hasn’t been built yet. The Sales Director looks at the IT manager and sees a gatekeeper who is being difficult for the sake of it. The bridge between them is made of 11% frustration and 91% misunderstanding.

To fix this, we need a radical transparency about the ‘how.’ Every request should come with a cost-benefit analysis that the asker actually sees. If Dave knew that his 101-client report was going to cost 31 hours of senior engineering time, he might decide that he only needs the top 11 clients. Or he might realize that the current network hardware isn’t actually relevant to the meeting at 2:01 PM. But because he doesn’t see the price tag, he orders the whole menu and lets the waiter starve.

The Exhaustion of Intellectual Gaslighting

There is a specific kind of exhaustion that comes from being told your complex reality is simple. It’s a gaslighting of the intellect. Muhammad felt it every time he saw a ‘simplified’ dashboard that hid 231 known errors in the back end. He felt it when he read the terms and conditions that promised ‘seamless integration’ while he was currently duct-taping two APIs together with a script he wrote at 1:01 AM on a Sunday.

Because if we don’t, we’ll eventually find ourselves in a room where all the Muhammads have left, and the only people left are the ones who think everything is simple because they don’t know how to do anything.

I finished reading those 61 pages of terms and conditions eventually. It took me 121 minutes of focused attention. It wasn’t ‘quick.’ It wasn’t ‘just’ a read. It was a commitment to understanding the reality of the service I was signing up for. It was a small act of rebellion against the culture of the surface level. We owe that same commitment to the people we work with. Stop looking at the screen and start looking at the wires. The wires are where the truth is, and the wires are always tangled.