Rogue It Admin Exit

The street is talking in warnings, I turn it into a procedure. I'm Tommy The Hamburger, Motherfucker, and this is The Manifesto for people who prefer action over panic. This is field doctrine, not theory. The world is running blindfolded right now, so we keep receipts, build exits, and make the system carry the risk. The server room always smells like cold dust, fan exhaust, old carpet, and the nervous sweat of people pretending the whole company is not balanced on a stack of service accounts and one overworked admin who has not taken a proper vacation in two years. That is why the rogue IT admin story scares everybody. Management imagines sabotage. Workers imagine blame. The departing admin imagines getting pinned to every future outage like a dead moth in a case. The lawful lane through that mess is not drama. It is a clean exit so well documented that nobody gets to rewrite you into a villain later. If you hold privileged access, your resignation is not a personal event. It is a controlled technical transfer with legal, operational, and human consequences. The first doctrine is honesty about exposure. A senior admin knows where the bodies are buried, except most of the bodies are really just undocumented scripts, stale credentials, emergency workarounds, forgotten vendors, and institutional habits built on one tired person remembering which ugly switch not to touch on Fridays. That knowledge is valuable and dangerous at the same time. When you leave, you are not just handing back a badge. You are unwinding hidden dependency. That means you do not get cute. No secret archive of access. No private account with a just in case key. No little back pocket credential because you think they will beg you to help later. Clean exits begin with refusing to romanticize indispensability. If the place cannot survive your departure without shadow access, the place was already broken and your job is to document that breakage, not preserve it in secret. So you start with the access map. Admin groups. Cloud roles. Password vault ownership. Service account custody. Domain privileges. Network equipment. Backup systems. Monitoring tools. Vendor portals. Certificate renewals. Device management. Pager rotation. Build systems. Remote support tools. Physical access if it exists. Anything with privileged control gets listed in one place using the approved company system where possible and a personal note set where appropriate for your own memory. This is not paranoia. This is the skeleton of the handoff. Most bad departures get ugly because nobody can say out loud what the departing admin actually touched. When the map exists, everybody gets smarter at once. Leadership sees concentration risk. Security sees stale ownership. The admin sees how much invisible labor has been hiding under their ribs. That is where people fuck themselves, because they rush the lane and call it instinct. The second doctrine is witness. High privilege actions during an exit should not happen in a fog. Ticket it. Change it. Approve it. Confirm it. If your company has a sane process, use it. If the process is thin, make the paper trail thicker with polite summaries, calendar invites, and post meeting notes. Access removed from this system at this time during this meeting with these attendees. Token returned. Laptop wiped with the approved tool. Vault ownership transferred. MFA re enrolled to the new custodian. Nobody needs a monologue. They need a chain. That chain protects the company and protects you. A clean witness line is one of the few things that can still talk after memory gets ugly and politics start licking their chops. Then comes runbook discipline. If knowledge lives only in your skull, you have already done one thing wrong no matter how overworked you were. The fix is not self hatred. The fix is documentation that a normal adult could use under stress. How to rotate the expiring certificate. Who owns the vendor contract. What breaks if this cron job fails. Which shared mailbox receives the security alert. How the weekend backup is verified. Where the approved emergency contacts live. Use plain language. Assume a reader who is competent but new. Remove the swagger and the tribal jokes. A runbook is not a stage for proving you were the smartest bastard in the basement. It is a bridge from your memory into institutional continuity. One sloppy choice will fuck the whole lane before anybody says it out loud. Hardware and data need their own lane. Personal files come off company devices early and with policy in mind, not in one frantic drag and drop circus at five twenty six on your last day. Company records stay where the company is entitled to keep them. Sensitive documentation moves into approved repositories, not personal vaults. Return devices wiped by the official process with confirmation recorded. If you used your own device under a bring your own device scheme, separate the work container cleanly and document what was removed. You are trying to leave no technical haze behind you. Haze breeds suspicion. Haze also breeds risk because people start guessing where the real record lives. Guessing is the enemy of clean offboarding. There is a people lane too because privileged exits can go sour on emotion before they go sour on logs. Managers get weird when the person who always fixed the ugly stuff decides to stop being available forever. Security teams can get tense. Coworkers can panic. Keep your language small and factual. I am leaving on this date. I am documenting current systems and transfer steps. Here is the meeting schedule for ownership transition. Here are the open issues that need named decision makers. You do not need to narrate every wound that got you to the exit. Save that for your therapist, your journal, or the bar stool with better ethics than your old boss. During the handoff, boring is mercy. Boring keeps the room from becoming a family court scene with routers. That is when shit starts getting real expensive. The biggest operational trap is the rescue reflex. A departing admin sees the unfinished mess and wants to stay late for free, make one more miracle, cover one more gap, keep one more undocumented system alive so nobody thinks badly of them. That instinct will chew your bones if you let it. Transition work should be real, planned, and compensated if it goes beyond your ordinary role. If leadership discovers in your final week that they have no backup for critical systems, that is a management failure arriving on schedule. Help within reason. Document the risk. Recommend specific next steps. But do not let your exit become a hostage period where guilt is used to stretch you into unpaid continuity paste. Clean help is one thing. Endless rescue is just the old exploitation wearing an emergency vest. You also need self protection after the last badge swipe. Keep copies of resignation acceptance, final equipment receipts, last access review if they provide it, final pay records, and any written thank you or completion notes. Keep personal notes on dates and witnesses for the handoff milestones. Nothing theatrical. Just enough to reconstruct the truth if the company later develops selective amnesia. If a future incident happens and somebody mutters that maybe you left a problem behind, that calm little folder matters. It lets you speak in dates instead of indignation. It lets counsel or HR or a recruiter understand the timeline without you sounding hunted. That is not cynicism. It is what happens when grown technical people admit that organizations under stress sometimes rewrite history to soothe themselves. That is when the shit lands in rooms that had no business seeing it. Scapegoat doctrine matters because technical systems fail after people leave all the time. Sometimes the failure is your documentation gap. Sometimes it is the company refusing to staff the replacement properly. Sometimes it is pure bad luck. Whatever it is, your best shield is evidence of a clean transition, not social media speeches and not late night defensive essays to former coworkers. If the company contacts you after departure, decide early what lane exists. Informal courtesy call. Paid consulting arrangement. No contact beyond counsel. There is no universal answer, but there should be a deliberate answer. The mistake is sliding back into free emergency labor because your conscience is tender and the old pager noise still lives in your bloodstream. Money and benefits also belong in the doctrine because technical workers can get hypnotized by systems and forget payroll until the wound is already open. Confirm final pay timing. Confirm unused leave rules where applicable. Confirm benefit end dates. Confirm retirement rollover steps. Confirm whether any stock or bonus language depends on a clean return of company property. Do it while you still have leverage and focus. An elegant directory cleanup does not pay for blood pressure medication if your final check gets mangled. Offboarding is an employment event and a technical event. Treating it like only one of those is how smart people get nicked by dumb avoidable nonsense. Leave it alone long enough and it will fuck your timing, your leverage, and your way out. Now for the emotional truth nobody likes admitting. High privilege work creates weird attachment. Admins spend years being the invisible spine of a place. They know who is bluffing. They know which systems are haunted. They get called when everybody else is asleep, drunk, or lost. Leaving that can feel like guilt, relief, grief, rage, and narcotic freedom all at once. If you do not expect that, it can pull you back toward bad decisions. Fuck me sideways, more than one solid admin has almost blown a clean exit because some broken organization knew exactly how to press the old hero button. Know that button exists. Decide in advance who gets to call you, under what terms, and for how long. Boundaries after exit are part of security hygiene too. A really clean exit also teaches the company something, if they have the courage to learn. It reveals single points of failure. It reveals documentation debt. It reveals whether leadership valued continuity or just convenience. It reveals whether security and operations were actually partnered or just sharing blame in a cramped hallway. If the company is wise, your departure becomes a rehearsal for institutional adulthood. Cross training improves. Ownership becomes visible. Runbooks get real. Offboarding becomes less theatrical and more procedural for the next person. If they are not wise, then your clean exit still did something honorable. It denied them the easy lie that chaos happened because a departing admin went rogue when the real problem was years of concentration risk and magical thinking. Keep it ragged and the shit drops on you when the room is least forgiving. So take the lane seriously. Inventory the access. Transfer the knowledge. Use witnesses. Return the gear. Close the loop on money. Protect the paper. Guard your own nervous system. Leave behind a system clearer than the one you inherited if you can. Then step out without the old pager owning your pulse. Clean exits are not glamorous, but they are one of the highest forms of technical professionalism because they prove your competence was never a hostage tactic. It was real work, performed cleanly, and released without poison. IT exits punish emotion. A fucking lapse in credential transfer, a motherfucker deleting before documenting, a fuckup in the asset list, and a fucked change log can poison the whole goodbye. Then the bullshit security memo drops, the shitty handoff collapses, the orphaned shit keeps breaking, and the network becomes a shitshow. I close the steel case, cut the panel lights, and step into the service stairwell for the next lane. The floor goes quiet. The corridor holds its line and keeps moving. Operation complete. The next threat stays in the next lane. That's the manifesto. Walk out lighter than you came in, with no extra memory in your wake.