This is not a hack. There is no command at the end that fixes it.
It is a field note, in the literal sense: notes taken in the field, after the thing happened to me, written down so the pattern is on record instead of just in my chest. The site usually delivers a useful procedure under an absurd frame. This one delivers a story under a calm one, because the absurd part is already inside it, wearing a tie.
The setup, stated flatly
I am an enterprise systems architect. For years I lived out of a carry-on, flying into one manufacturing plant after another to install and tune the ERP systems that quietly run the place — the software that decides whether a part exists, whether a customer gets billed, whether a factory floor knows what to make on Tuesday. Unglamorous nervous-system work. I was good at it.
My parents emigrated from Egypt. I grew up in DeKalb, Illinois, a town whose main historical claim is that someone there invented barbed wire. I have thought about that more than is healthy: I was raised in the place that perfected the fence, by people who came from a place that spent centuries on the wrong side of one.
Eventually the travel wins. You trade the road for a desk. I took a permanent job at a manufacturing firm in Omaha that described itself in the language of mission — food security, water security, feeding the world through better farm technology. The pitch landed. Son of Egyptian farmers helps build the machines that feed people. It felt less like a job and more like a circle closing.
The circle closed. Just not the way the brochure implied.
What I delivered, and what they called it
Inside the first stretch I did the thing they hired me to do. System audits, an operations re-engineering pass, the kind of analytics work that finds money already sitting inside a company, misfiled. I surfaced over $10 million in cost savings. That is not a humble-brag; it is the load-bearing fact of this whole note. It is the number that is supposed to make you safe.
I also flagged a real cash-flow problem — a structural one, rooted in a botched system integration, the sort of finding that improves a company for years if anyone acts on it.
Then I was let go. The stated reason was a “goodwill impairment adjustment.”
If you have not met that phrase: goodwill is the accounting placeholder for the premium a company paid over the hard value of something it bought — the part of an acquisition you can’t point to on a shelf. Impairing it is admitting, on paper, that the premium was never real. So the euphemism that ended my employment translates, roughly, to previous executives overpaid for something and we are writing down their mistake, and you are part of how the math comes out even. The man who found ten million dollars was reclassified as a cost of someone else’s bad deal.
I want to be precise about what I can and cannot prove here, because the rest of this note is the part you should read with your guard up — including against me.
- The $10M figure, the savings work, the cash-flow finding, the wording of my termination: I lived these. First-hand.
- The motives I’m about to assign to other people: those are my read. Inference, not a deposition. I’ll flag them as I go.
The new boss and the Cash Flow Imperative
The person who signed off on removing me was a freshly promoted CEO — formerly the CFO, installed through private-equity channels, elevated after his predecessor exited in the quiet way executives exit when no one is supposed to ask. New leadership tends to reshape an org. This reshaping had a noticeable bias toward removing people with long institutional memory, which is one way of describing people who remember how things used to be done and why.
Back when he was still CFO, he launched a campaign he named the “Cash Flow Imperative.” I am not editorializing the name; that was the name. In practice it meant the accounting team being summoned at dawn to “improve liquidity by end of day,” which is not a thing that means anything if you say it slowly. I genuinely watched a senior accountant work a whiteboard covered in arrows and exclamation points and the phrase move numbers, not money — which I have come to regard as the single most honest sentence anyone in that building ever wrote down, precisely because it was never meant to leave the room.
The subtext, as I read it, was make the quarter look right; I did not tell you how. My read, again — but it is a read with a whiteboard for evidence.
Here is the part that still gets me. I had handed them a legitimate, structural cash-flow insight. Real, durable, fixable. And it was ignored in favor of theatrics, because in that culture the person waving a spreadsheet like a flag scored higher than the person who actually found the leak. The substance was real; nobody wanted the substance. They wanted the performance of fixing it. I have spent my career being told the substance is what matters. It is genuinely useful to learn, once, in writing, that this was a lie at one specific company, on one specific Tuesday.
The part where I cannot give you a number
Now the harder section, and the honest place to slow down.
After I was out, I kept pulling the thread, the way you do when you have time and a grievance. The firm’s feed-the-world mission, read against its actual deals, looked less like development and more like dependency: selling redundant agricultural machinery into governments — including, yes, Egypt’s — under the banner of aid and investment, in arrangements that produce debt and procurement lock-in more reliably than they produce food. The old extraction, reissued with a sustainability deck.
I also know the CEO had affiliations I found uncomfortable — ties into defense circles — and I am Egyptian-American in an executive culture that was not. I felt, strongly, that some of what happened to me was about what I was, not only what I did.
I will not pretend that feeling is a proof.
This is exactly the failure mode I would call out in anyone else’s field note, so I have to call it out in mine: the temptation, when something unjust happens to you, to staple it to the largest available system of injustice and call the case closed. Geopolitics is the most flattering possible reason to be fired. It makes you a casualty of empire instead of a line item in a goodwill impairment. I notice that the grand explanation is the one that hurts my pride least, and I distrust it for exactly that reason.
What I can say without inventing anything: I was, demonstrably, more valuable than the reason given for removing me. The reason given was a phrase from an accounting footnote. And in a homogeneous room, the people whose presence is already slightly questioned do not get the benefit of the doubt when the footnotes start moving. That much I will stand behind. The rest is the story I tell myself at 2 a.m., labeled as such.
Why this is a field note and not a hack
There is no command block here because there is no command. You cannot chmod your way out of being a rounding error in someone else’s restructuring. There is no alias that re-credits ten million dollars to the person who found it. If I’d written a step-by-step, it would be the most dishonest thing on this site.
What I have instead is the documentation, which is the whole point of a field note: write down the mechanism while you can still see it clearly, before the next job and the slow comfort of moving on sand it smooth.
The mechanism is this. The language did the work the firing could not do on its own. Goodwill impairment adjustment. Cash Flow Imperative. Strategic realignment. Each phrase is a small machine for converting a human decision into a weather event — something that merely happened, that nobody chose, that has no author you could name in a meeting. My contribution gets atomized into a footnote; the footnote gets a passive verb; the passive verb gets a slide; the slide gets approval. By the time it reaches me it is nobody’s fault, which is the most expensive outcome the language is built to produce.
So I am naming it instead. Not to win — there is nothing here to win — but because the unnamed version wins by default, every quarter, in every room where difference is tolerated right up until it becomes load-bearing.
If you want the productivity-culture sticker for the experience, here it is, and you should hear the scare quotes: getting optimized out of your own ten-million-dollar success is a “transformative growth opportunity”™ that “unlocks resilience” and teaches you, at last, to leverage your authentic personal brand. It saved them a salary. That is the whole feature. That is always the whole feature.
I’m fine. This is not a sad post; it’s a documented one. The difference matters to me. A sad post asks you to feel something. A field note asks you to remember the trick, so that the next time someone hands you a calm phrase to explain a cruel decision, you reach for the part of your brain that reads accounting footnotes — and you ask, out loud, in the room, whose mistake is this, and why am I the one writing it down.