Stress Taking its Toll on IT Workers

Lisa Hoover 0 Tallied Votes 336 Views Share

When sysadmin Terry Childs went off the rails in San Francisco a few weeks ago and deliberately locked down the majority of the city's network, no one should really have been surprised. As most IT professionals will tell you, it was bound to happen sooner or later.

took a fascinating look at the soft underbelly of the IT work world recently. Sadly, all of the author's sources refused to be identified out of concern for their jobs. I find that level of fear disturbing since serious issues rarely get better unless they are exposed to the light of day and managers are held accountable.

It's not that I don't understand the reluctance of IT workers to come forward publicly. They know they are easily replaced by the legions of tech workers churning through colleges in the U.S. and those waiting in the wings for jobs to be outsourced overseas. I'm dismayed that the climate is so hostile in the first place, and that managers and CIOs allow it to continue.

The chief long-standing complaint of tech workers is how they are expected to produce results with little or no say in how to get the job done. For instance, the president of a company may suddenly decide the entire company needs to "go green." He'll issue a directive to IT to reduce its carbon footprint without actually funneling money into the department to retire old, outdated equipment and replace it with environmentally-friendly hardware. Tensions arise when the company president tells IT to make do with what they have, and IT simply can't.

In his article, Kaneshige tells story after story of tech workers who struggle to keep their jobs, dignity, and sometimes sanity, in the face of an industrywide uptick of layoffs. "There's no question that another flare-up à la Childs is in the making, as companies turn a deaf ear to the pleas of burnt-out tech workers," he says.

There's precious little advice in the article about how to fix this severely damaged situation, likely because no one knows just what to do about it. One IT manager Kaneshige interviewed recommends choosing someone with a technical, rather than business, background to lead teams of tech workers. CTO Yau-Man Chan says he expects his corps of engineers would "be less cooperative if [he] came from a business background."

What else can be done to reduce the tension between IT managers and staff? Of course communication and respect are key, but let's dig deeper. Let's have some real-world ideas in the comments.

Dani AI

Generated

As notes, the root problem is usually structural: people are asked to deliver without authority, budget, or backup. That creates fear, single-person bottlenecks, and ultimately mistakes. The discussion so far points in the right direction, but here are concrete, practical steps teams can start using immediately.

  • Maintain a compact technical risk register: list critical systems, single-person dependencies, estimated business impact and a one-line remediation request for each item. Review it with execs quarterly so decisions aren’t made in the dark.
  • Reduce single-person control: require at least two authorized operators for any critical account or change, rotate privileged keys, and document emergency access procedures.
  • Operational hygiene: attach clear, tested runbooks to every significant alert; require pair-checks for production changes; keep rollback plans simple and rehearsed.
  • On-call fairness and recovery: cap frequency of on-call duty, pay or give compensatory time, and require a recovery window after major incidents. Track total overtime as a staffing signal.
  • People structure and advocacy: create parallel career tracks (technical lead vs people manager) and give senior tech leads a formal seat in budgeting/planning so they can advocate for refreshes and hires.
  • Culture tools: blameless postmortems, anonymous feedback channels, short pulse surveys, and manager training in active listening and workload planning.

Building empathy by putting technically literate people in leadership roles helps, as suggested, but it only works if those leaders are given authority and budget to act. Start small (one service, one risk register, one on-call rotation) and show measurable improvements — fewer incidents, lower overtime, faster restores. That creates the executive buy-in needed for bigger fixes.

ravishankarkota 0 Newbie Poster

If a techie becomes a manager , then there is less collision.If it is not possible Senior tech leads and managers should come to aid in elaborating the problems of IT developers to Managers.A manager should be empathetic to understand the real problems.
Free communication with out Egos , occasional Get Together of managers and techies will reduce the gap between techies and managers and increase the comfort levels in work Jone.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.