Suits ignored IT's warnings, so the tech team went for the neck
Corporate IT staff recount a case where leadership ignored clear warnings about looming network capacity issues until the tech team deliberately throttled executives’ own connections to force action. Commenters use this anecdote to explore broader themes: how poorly aligned incentives, weak technical literacy, and political dynamics in large organizations lead to underinvestment in infrastructure and security, and why engineers often resort to “making management feel the pain” rather than quietly absorbing it. Others question the ethics of such tactics, arguing for better risk communication in business terms and clearer accountability instead of covert sabotage.
Organizational dysfunction & incentives
- Many see the story as highly believable, blaming large-organization pathologies: distance between “suits,” IT, and customers; tech seen only as a cost; decisions driven by politics and budgets rather than operations.
- Executives are described as managing money and information flows, often capturing outsized rewards and acting parasitically on the firm.
- Budgeting is portrayed as a power tool: controlling spend to prevent political power centers, not just to save money.
Communicating technical risk
- Several argue IT may have failed to explain the issue in business terms (e.g., “customers will experience errors by date X,” not “50% utilization”).
- Others stress that good leaders should ask follow‑up questions and understand basic concepts like exponential growth and queueing.
- A recurring theme: effective upward communication means translating tech problems into customer impact, risk, and dollars, not jargon.
“Make them feel the pain” vs professionalism
- Many endorse “managed pain” as a necessary tactic in bureaucracies: route tickets or incidents to decision‑makers, stop heroic firefighting, let SLA breaches and customer complaints surface so problems get resourced.
- Others see the deliberate throttling in the story as unethical or “sabotage,” arguing professionals should follow management’s decisions, document risks, and let failure occur naturally.
- Counter‑argument: professionals owe more to customers and the company than to incompetent managers; blind obedience is framed as “bootlicking.”
Autonomy, budgets, and the role of management
- Multiple comments call for greater operational autonomy for IT (e.g., small upgrades without executive approval), with accountability at the service/SLAs level rather than line‑item micromanagement.
- Some suggest modeling the business as IT’s “customer,” with agreed quality levels and a fixed budget, instead of case‑by‑case pleading.
Plausibility and technical details of the story
- Some doubt the story’s technical accuracy (ISDN/QoS timing, utilization thresholds) and see it as “revenge‑of‑the‑nerds” fantasy.
- Others, especially with 90s banking experience, report similar patterns: backups or capacity ignored until catastrophic failure, after which funding appears.