That was after he spilled his smoothie into the breakroom power strip and took down half a floor’s Wi-Fi. He thought it was funny. I thought it was a preview. I’m in my mid-40s, two kids in college, two cats with IBS, and one ex-husband who still texts me every April like I’m his personal tax fairy.
I’ve spent twenty years in IT, and for the last eight, I was the one who kept the whole damn place running. Not the flashy work, not the slide decks, the real work. The servers, the security licenses, the vendor contracts, the backups that nobody ever thought about until something crashed. We weren’t Amazon, but we were big enough that if our production went down, money started bleeding out of arteries nobody even knew were there.
I made sure that never happened. And hey, since 90% of y’all listen to these stories without subscribing, maybe toss a like and hit that follow button. Then Brent showed up. New VP of Operations.
Fitted suits, buzzwords that sounded good in meetings and meant nothing on the floor. I watched him from behind my second monitor, half listening while he rattled off terms like streamline redundancy and optimize cost centers. He had no idea what any of it actually meant. He just knew how to say it.
He also knew how to cut people. His second move, weekly all hands meetings where he talked about synergy and accountability while the real work piled up like corpses in a war no one declared. He especially loved finding ways to eliminate redundancy, which in plain English meant pushing out anyone who wasn’t shiny enough to look good on a slide deck. The old guard, the people who actually knew the systems, gone one by one.
I knew I was on the list. Not because anyone told me, but because I saw the spreadsheet. Like when the cat hides under the bed 2 hours before the sirens start wailing. So I did what I always did.
I kept the system humming. I documented everything. Every login, every license, every vendor touchpoint, all of it traced, backed up, verified. I didn’t say a word.
I just prepared. The day came on a Thursday. Brent called me into a conference room with Legal on the line. He did the whole sad-face routine, said it wasn’t personal, said it was about streamlining for the future.
He talked for ten minutes. I nodded. I signed. No bridge burned because they assumed I wouldn’t bring matches.
He walked me to my desk and watched me pack a small box. He said they’d handle the transition, no need to worry. I said I’d leave everything documented and accessible. He smiled like I was doing him a favor.
My badge deactivated at exactly 5:05. No party, no speech, no cupcake in the breakroom, just an autogenerated farewell message sent from HR’s system with my name misspelled. They brought in Hannah the next Monday. Young, sharp, dressed like she’d been born in that boardroom.
She walked around asking basic questions, taking notes, nodding like she understood. Brent introduced her as the future. She didn’t ask me anything. Why would she?
I was already gone. But I wasn’t gone. Not really. I had left them a gift, and they didn’t even realize it.
You see, the entire security infrastructure ran on one credential. Mine. It was a legacy setup, not because nobody else wanted to fix it, but because nobody else knew how. Every vendor license, every API key, every authentication token tied to my identity.
I’d flagged it twice in yearly reviews. I’d written recommendations, suggested migration paths, offered to train backup personnel. Every single one filed and ignored. Brent had signed off on keeping it that way.
Too expensive to change, too disruptive, too complicated. He called it a low priority. I called it a ticking clock. So when I left, I didn’t take anything.
I didn’t delete a single file. I just let the system do what it was designed to do. On Monday at 4:55 p. m.
, I opened my terminal one last time, logged into the vendor portal, verified that my credentials were still tied to the active license, still binding, still irreplaceable without formal process. Then I logged out. At 5:01 p. m.
, the deactivation timer kicked in, automatically scheduled to begin after 48 hours of inactivity. I shut my laptop and slid it into the return bin outside IT. The license didn’t revoke access immediately. It slid into pending deactivation, giving the vendor system 48 hours to wait for reauthentication, renewal, or reassignment.
If someone had logged in before the timer expired, everything would have been fine. If someone had even opened the documentation I left, they would have seen the warning. The vendor had sent automated flags for months, easy to miss if you weren’t looking, but impossible to ignore if you were. Brent never bothered to read any of it.
By Wednesday morning, the first flags started firing. Audit log sync error, expected response timeout. The system sent alerts to the distribution list I used to manage. Nobody responded.
The alerts escalated. Still silence. I knew that because I was the one who used to check it. By Thursday, the vendor portal locked.
No response, no heartbeat. The system did exactly what it was told to do. One by one, the services went dark. The security dashboard went blank.
The authentication layer started rejecting every request. The vendor logs showed attempts, thousands of them, all failing. Without proper token validation, they couldn’t authenticate anything. By 4:13 a.
m. , the overseas logistics platform reported its first outage. At 5:45, the first major client filed a priority 1 incident. At 6:30, the internal ticketing system stopped accepting requests.
By 9 a. m. , every critical system that depended on that credential was frozen. No one could log in, and even if they could, they had no clearance to change a thing.
I got a text. From an old coworker. Three words: theyre losing it. Across town, execs were pacing their glass offices barefoot, suit jackets abandoned, shouting into muted Zoom calls while interns fetched Red Bulls and tried not to cry.
Hannah, by most accounts, had a full breakdown by 7:15. She was last seen wheeling her desk chair into the hallway, muttering something about legacy traps and why didn’t anyone tell me? Because they did tell you. I told you.
It was in the documentation. By 10 a. m. , they’d traced the issue to the license expiration.
by 10:30, they’d confirmed the credential was tied to my name. By 11, they were calling me. I let it ring. Same number, same ringtone, same desperation.
Then voicemail after voicemail, one from Brent, one from Legal, one from Hannah, her voice cracking like she’d just run a marathon inside a haunted house. Then a text. Short. Direct.
What do you need? I didn’t reply. The system spoke for me. They tried everything.
They tried calling the vendor, but the vendor required a formal release from the original credential holder. They tried activating a backup license, but the inventory file was encrypted. They tried reaching out to the vendor’s emergency line, but the security protocol required a manager of record. That was me.
They tried to escalate. The vendor asked for a signed release form. They didn’t have one. Hannah sent a DM from her personal phone around 9:12 a.
m. Her message was short. Please. They had her.
She didn’t know what she was signing, so she signed it and sent it back. Then I gave them what they needed. I logged in, verified the release, and submitted it. One by one, the system came back to life like it had been holding its breath for three days.
Access restored. Licenses renewed. Services blinking awake again. I was still at my kitchen table.
I wasn’t celebrating. I wasn’t angry. I was just still. The chaos faded.
The clients calmed down, mostly. Brent and Hannah and Legal had to explain themselves to the board. Everyone on the executive floor started carrying around printouts of my final email, the one they’d ignored, the one that explained exactly what would happen if the credential was centralized without a succession plan. But they didn’t learn.
That same week, Brent sent a company-wide announcement. New security protocols. Centralized credential management. No individual points of failure.
He’d learned the words, but not the lesson. A few weeks later, I got another text. It was Brent. He said, out of nowhere, that they were reconsidering their security vendor, that they wanted me to consult.
I didn’t respond. Not because I was bitter, but because I’d already moved on. Some people only learn after the fire, and even then, they just build the house the same way and hope it doesn’t burn twice. I still check the logs sometimes, out of habit.
Everything looks quiet. But quiet, I’ve learned, is just the sound before the system decides to speak.
