You know that feeling. The knock on your office door—or the ping of yet another Slack message—that isn't about a server outage or a security threat. It's about Excel. Again. Or about why someone's personal Gmail isn't syncing to their work phone. You're an IT Director, a Systems Architect, a Cloud Engineer... and you're being asked to perform digital janitorial work while strategic projects gather dust. Welcome to the bullshit world of IT in 2026, where the promise of being a strategic partner has been replaced by the reality of being an organizational dumping ground.
This isn't just complaining. It's a systemic failure. The original Reddit rant that inspired this article struck a nerve because it was painfully, universally true. The poster, a supposed IT Director, was being treated as the be-all, end-all person for everything from basic software tutorials to being blamed for user errors completely outside their control. The 673 upvotes and 459 comments weren't just agreement—they were a collective scream into the void from professionals who are tired, burned out, and wondering where it all went wrong.
In this article, we're going to dissect exactly what happened. We'll look at how IT became the corporate catch-all, why the "blame IT first" mentality persists, and most importantly, what you can actually do about it. This is part diagnosis, part therapy session, and part survival guide. Because if you don't change the game, the game will break you.
From Strategic Partner to Glorified Doormat: How We Got Here
Let's rewind a bit. The early 2000s vision of IT was one of transformation. We were going to enable business strategy, drive innovation, and become essential partners at the leadership table. Fast forward to 2026, and for many, that vision has curdled. Instead of strategizing about AI implementation or zero-trust architecture, you're explaining for the tenth time how to attach a file to an email. What happened?
The problem is twofold: success and abstraction. IT succeeded too well. We made technology so ubiquitous and (mostly) user-friendly that it became invisible until it broke. The average employee in 2026 has zero understanding of the complex systems that deliver their daily tools—they just expect them to work like magic. This creates a massive expectation gap. When the magic fails (or when they simply don't understand it), they turn to the nearest "wizard"—you.
Meanwhile, the abstraction of technology has created a knowledge vacuum. People don't know how their computer works, how the network functions, or where data actually lives. They see a screen and buttons. This lack of fundamental digital literacy, even among otherwise intelligent professionals, turns IT into a mystical priesthood. And when you're the priest, you get prayed to for every minor spiritual inconvenience, from a forgotten password to a confusing dropdown menu in Salesforce.
The Blame Game: Why IT is the Default Scapegoat
"Why are all our emails not coming in?!" The classic cry. The user hasn't checked the sender's address, hasn't looked in their spam folder, and hasn't considered that they might have typed the address wrong. But the first instinct? Blame IT. This reflexive scapegoating isn't just annoying—it's corrosive to your authority and mental health.
This phenomenon stems from a fundamental human tendency: to attribute internal problems to external causes. Psychologists call it self-serving bias. When a salesperson misses a lead because they didn't check the CRM properly, it's easier to blame "the system being down" or "a sync error" than to admit a personal oversight. IT systems are complex, opaque, and poorly understood by most. That makes them the perfect shadowy entity upon which to project failure.
In 2026, this is compounded by the proliferation of SaaS tools. When everything is a cloud service, the line of responsibility blurs. Is the email problem with Microsoft 365, the local network firewall, the user's device, or a misconfigured rule? The user doesn't know, and often doesn't care. They just know "email is broken" and that's an IT problem. You become the human API for every digital service the company uses, expected to diagnose and fix issues across a stack you might not even fully control.
The Cognitive Tax: Your Brain Isn't a Free Help Desk
The original rant highlighted a key injustice: "They use my brain for everything." This is the hidden cost that never appears on a balance sheet—the cognitive tax. Every interruption to explain pivot tables, every walk-through of printing double-sided, every minute spent on a problem that is fundamentally a training issue, not a technical one, is a minute stolen from your actual job.
This tax has a compounding effect. Context switching is a known productivity killer. Studies suggest it can take over 20 minutes to fully regain deep focus after an interruption. If you're getting five "quick questions" a day, you've potentially lost nearly two hours of productive, strategic work. Over a week, that's a full day. Over a year, it's months. You're not just answering questions—you're mortgaging your capacity for meaningful work to fund the company's lack of digital training.
And let's be honest: this work is rarely valued. Solving a critical server migration gets a nod. Preventing a data breach gets applause. Walking the CFO through formatting a spreadsheet for the third time? That's just "part of the job." It's the IT equivalent of emotional labor—essential, draining, and utterly invisible in performance reviews.
The Automation Imperative: Your Only Way Out
So, how do you stop being a doormat and start being a director again? The answer isn't just saying "no" (though that's part of it). The answer is systematic, ruthless automation and process redesign. You must build walls of code and policy between your valuable time and the endless tide of trivial requests.
Start with the low-hanging fruit: self-service. Any question that gets asked more than twice needs a permanent, searchable answer. Build a robust internal knowledge base (a wiki, a SharePoint site, even a well-organized Google Doc). Populate it with clear, screenshot-filled guides for the Top 50 user requests: how to connect to the VPN, how to reset your password via the portal, how to format cells in Excel. Then, enforce its use. When someone asks, your first response is a link: "Here's our guide on that! Let me know if the steps don't work for you." This simple act forces ownership back onto the user.
Next, automate ticket triage and response. Use your service desk software's capabilities to the max. Create canned responses for common issues. Implement chatbots that can answer basic FAQs before a ticket is even created. Set up automated workflows that, for example, reset passwords or grant application access after manager approval, without you ever touching it. The goal is to make the simple stuff happen automatically and the common stuff happen with minimal intervention.
For more complex data-gathering tasks that users often dump on you—like pulling reports from various web systems or consolidating information—consider tools that can handle the heavy lifting. While not a fit for every problem, platforms like Apify can be useful for building automated scrapers and data extractors. Imagine a salesperson needs daily data from a public competitor site. Instead of you doing it manually, you could (with proper governance) help them set up a simple, scheduled actor to collect that data into a spreadsheet automatically. You move from being the person who does the task to the person who enables the task.
Redefining Your Role: The Art of Strategic Refusal
Automation handles the tactical stuff. But you also need a strategic shift in how you position yourself and your department. This is about managing expectations and professionally, firmly, redefining the scope of your role.
First, get your leadership on board. Frame it not as you refusing work, but as you optimizing the company's investment in IT. Prepare a brief document or presentation. Show them the data: "40% of our ticket volume is for basic how-to questions and personal device support. My team spends X hours per week on this, which delays Project Y by Z weeks. Here's a plan to create self-help resources and redefine our scope to focus on business-critical infrastructure." Speak their language: ROI, risk mitigation, strategic alignment.
Second, create and publish a clear scope of support. What do you support? Company-issued laptops, core business applications, the network. What don't you support? Personal phones, personal email accounts, how-to training on Microsoft Office for non-core functions, troubleshooting home WiFi. Post this everywhere. Link to it in your email signature. This isn't about being unhelpful; it's about creating clear boundaries so you can excel within them.
When a request comes in that's out of scope, have a graceful redirect ready. "I can't directly help with your personal phone setup due to our security policy, but here's a great guide on smartphone basics and the vendor's support number." Or, "Excel training is handled by the department manager for professional development. I'd be happy to consult on a specific, complex formula if it's blocking a business report, but general training isn't in our wheelhouse."
Investing in User Education: The Long-Term Fix
You can't automate or refuse everything. Some user education is necessary. But it shouldn't be one-on-one, ad-hoc tutoring. It needs to be scalable and proactive. Advocate for—or simply start creating—a digital literacy program within your organization.
This doesn't need to be a formal, expensive training suite. It can start small. Record short (under 5-minute) Loom videos answering the most common questions. Create a monthly "Tech Tip" email that goes to all staff, covering one useful skill, like keyboard shortcuts or managing inbox rules. Run optional "Lunch and Learn" sessions on topics like data security basics or getting the most out of the CRM.
The goal is to shift the culture from learned helplessness to empowered capability. When users feel more confident in their basic digital skills, they bother you less with trivialities. They also make fewer catastrophic errors. This is a win-win. It makes their jobs easier and frees you up. If internal resources are stretched too thin to create this content, remember that quality training material can also be sourced externally. You could hire a technical writer or instructional designer on Fiverr to help script and produce a polished series of core training videos, which is far more cost-effective than your hourly rate spent repeating yourself.
FAQs: Navigating the Daily Grind
Q: My boss says "customer service" is part of my job and I should just help everyone with everything. How do I push back?
A: Reframe the argument. Explain that true customer service for the business means ensuring its critical systems are secure, reliable, and evolving. You can't provide that high-level service if you're buried in basic help desk tasks. Propose a pilot: for one month, you'll track all requests and categorize them. Then, show the data to demonstrate how redirecting basic queries can free up time for projects that directly impact the bottom line.
Q: What if I'm a team of one? I can't build fancy automation.
A: Start even smaller. Your first automation is your email signature with links to the three most common FAQs. Your second is a single Google Doc with screenshots on how to do something. Your third is a simple rule in your email client to auto-respond to emails with "password reset" in the subject with a link to the self-service portal. Automation isn't all about Python scripts; it's about creating systems that work without you.
Q: Won't this make me seem lazy or uncooperative?
A> It might, to the people who have grown accustomed to using you as a crutch. But it will make you seem strategic and professional to leadership. Focus on communicating the value of what you're doing instead. "I've automated password resets so I can now focus on implementing the new security audit system, which will reduce our cyber insurance premiums." That's a narrative of initiative and impact, not laziness.
Reclaiming Your Sanity and Your Career
The bullshit world of IT in 2026 doesn't have to be your world. The feeling of being a glorified doormat, a cognitive spare tire for the entire organization, is a symptom of broken processes and unclear boundaries—not an inevitable part of the job. You became an IT professional to solve interesting problems, build resilient systems, and enable technology to do amazing things. Somewhere along the line, you got drafted into being a concierge for digital incompetence.
Reclaiming your role starts with a mindset shift: you are a force multiplier and a strategic asset, not a cost center or a help desk. It continues with tactical action: automate the repetitive, document the common, and refuse the irrelevant—with professionalism and data to back you up. It culminates in a cultural shift, where you champion digital literacy not as a favor to users, but as a critical business investment.
The knock on the door will always come. The Slack ping will always chime. But in 2026, you have more tools than ever to ensure that when you answer, it's for something worthy of your expertise, your time, and your hard-won brainpower. Stop being the doormat. Start building the door.
