The fluorescent hum of Conference Room 308 is vibrating right at the base of my skull, a low-frequency reminder that I have been sitting in this ergonomic chair for exactly 188 minutes. On the massive screen at the front of the room, a young man named Tyler-who looks like he has never had to scrub grease off his knuckles in his life-is explaining the ‘seamless integration’ of Project Phoenix. He is currently demonstrating how to log a simple site visit. He clicks a dropdown. Then a sub-menu. Then a verification toggle. By my count, he is on click 18, and we haven’t even reached the field where you input the actual notes. I look over at Brenda, who has been our lead accountant for 38 years, and I see her eyes glazed over. Underneath her desk, her hand is resting on a weathered, mustard-yellow folder. It is her ‘Master Tracker,’ a physical spreadsheet she’s maintained since 1998, and I know for a fact she’s already updated it for this morning’s tasks while Tyler was still struggling with the two-factor authentication.

I’ve spent most of my life restoring vintage signs. There’s a specific way you have to treat a 1958 neon fixture that’s been sitting in the rain for half a century. You can’t just spray-paint over the rust and expect the hum to come back. You have to strip it down. You have to understand why the circuit broke in the first place. Was it the weather? Was it the vibration of the street? Was it a bad solder job from a guy who was rushing to get home on a Friday? Usually, it’s a combination of all three. Business processes are no different, yet we treat them like they’re abstract math problems that can be solved by adding more code. We think that if we automate the mess, the mess disappears. It doesn’t. It just becomes ‘automated mess,’ which is significantly harder to clean up because now the rot is hidden behind a slick UI and a series of mandatory fields that everyone hates.

The tool is never the transformation; it is only the witness to it.

“

I had a realization the other day while I was working on a 1948 porcelain enamel sign for a defunct diner. I’ve been using the word ‘epitome’ in my head for at least 28 years. In my mind, it was always pronounced ‘epi-tome,’ like a large book or a volume of history. I said it out loud during a meeting last week-‘This software is the epi-tome of our struggles’-and the silence that followed was so thick you could have sliced it with a putty knife. Someone eventually corrected me, gently, like you’d tell a child their fly is down. It’s ‘e-pit-o-me.’ I felt a flush of heat creep up my neck. For nearly three decades, I had built a whole internal vocabulary around a fundamental misunderstanding of a single word. It makes me wonder what else I’m mispronouncing. Not just words, but concepts. We call this ‘Digital Transformation,’ but maybe we’re mispronouncing the reality of it. Maybe it’s actually ‘Bureaucratic Fossilization.’ We take the existing dysfunctions-the fact that Bob won’t talk to Sarah, or that the sales team overpromises because they don’t understand the inventory-and we bake those dysfunctions into the software’s permissions and workflows.

Casey K.-H. told me once, while we were looking at a particularly stubborn piece of rusted channel lettering, that you can tell everything about a business by how they treat their tools. If the tools are covered in dust and the workers are using improvised hacks, the problem isn’t the tool. It’s the respect for the craft. In the office, our ‘hacks’ are the spreadsheets that live on local desktops, the Post-it notes stuck to the monitors, and the ‘quick calls’ that bypass the official ticketing system. Project Phoenix was supposed to kill the hacks. Instead, it has turned them into an underground resistance. I saw a Slack channel yesterday named ‘The Real Phoenix,’ where 88 employees are sharing tips on how to bypass the mandatory reporting fields just so they can get their actual work done. We’ve created a shadow government within our own company because the $2,000,008 tool is too heavy to lift.

The Kitchen Test: Serving the Human, Not the Machine

It’s a strange irony that we often find more clarity in our home lives than in our professional ones. When you need a tool for your kitchen or your laundry room, you look for something that simplifies the burden. You don’t buy a toaster that requires 18 clicks and a password reset to brown a slice of bread. You look for reliability and a clear path from A to B. It’s why people gravitate toward places like

Bomba.md

when they want tech that actually functions as advertised-there is an inherent expectation that the machine should serve the human, not the other way around. But in the corporate world, that logic is flipped. We are expected to serve the machine. We are told that if the data is bad, it’s because we aren’t feeding the machine correctly, never that the machine is a glutton for useless information.

I remember a project back in ’98-a small neon job for a pharmacy. The owner wanted it to flash in a specific sequence, but the controller he bought was too complex for the old wiring. We spent 58 hours trying to make the new tech talk to the old copper. In the end, we realized the problem wasn’t the controller or the wiring; it was that the owner didn’t actually know what he wanted the sign to say. He was using the flashing lights to distract from the fact that he hadn’t decided on a name for the store yet. That’s Project Phoenix in a nutshell. We are flashing $2M worth of lights to distract from the fact that we don’t know how to talk to each other without a screen acting as a mediator. We buy software to avoid the ‘people problem.’ The people problem is that we are afraid of accountability, afraid of directness, and terrified of the simplicity that comes with admitting we might be doing it wrong.

Complexity is a mask for a lack of courage.

“