The Unwritten Rules of IT Office Culture Every Tech Pro Should Know
Every IT department runs on two parallel operating systems: the official one documented in the employee handbook, and the shadow OS of unwritten rules that actually governs daily life. Violate the official rules and you'll get a meeting with HR. Violate the unwritten rules and you'll find your desk relocated next to the server room, your pull requests mysteriously delayed, and your coffee mysteriously decaffeinated. This is a guide to the second operating system—written with respect for the traditions, frustrations, and occasional absurdity that make IT culture what it is.
The Sacred Laws of Shared Infrastructure
In any IT environment with shared resources, an elaborate informal governance system emerges to prevent the tragedy of the commons. The development database has a pecking order for who can run long queries during business hours. The staging environment belongs to whoever is doing the most critical demo at any given moment—but the definition of "most critical" is negotiated through a combination of seniority, volume of Slack messages, and the implicit understanding of whose director will make the most noise if things go wrong. The test server that nobody is supposed to care about but everyone is secretly running personal projects on represents a form of shadow IT so universal it might as well be official policy. These informal governance systems are often more efficient than formal alternatives precisely because they are enforced by social consequences rather than bureaucratic process.
The Ticket System Theology
Every organization's ticketing system develops its own theology—a set of beliefs about what constitutes a valid ticket, what severity ratings actually mean in practice, and the correct way to escalate without making enemies. The unwritten rules include: never assign a ticket back to someone without a comment, because silent reassignment is considered passive-aggressive. Never mark something as "resolved" before confirming with the requester, because premature closure is the ticketing equivalent of hanging up on someone mid-sentence. And above all, never submit a ticket for something you could just as easily ask in person and get resolved in 30 seconds—though understanding which category a given request falls into requires years of calibration. The ticket system is simultaneously the most important and most resented tool in IT, and navigating it gracefully is a genuine career skill.
The Unspoken Knowledge Transfer Problem
Every IT team has a person—usually modest, often underestimated—who is the actual institutional memory of the department. They know why the firewall rule for port 8443 exists, whose personal project that server in the corner is running, and which vendor to call when the official support line produces only automated responses. This person is not always the most senior, not always the most technically impressive, and almost never adequately compensated for the organizational risk they represent. The unwritten rule is: be nice to this person. Learn from them. Take notes. Because when they leave—and eventually they always leave—the team enters a period that can only be described as IT archaeology, digging through years of undocumented tribal knowledge with the urgency of an incident and the methodology of a guess.
The After-Hours Communication Compact
One of the most important unwritten rules in modern IT concerns after-hours communication. Every team develops its own implicit contract about what constitutes an emergency worth interrupting someone's personal time, who is acceptable to contact via which channels, and how long a non-response to a non-emergency message is acceptable before escalating. These norms are rarely documented and are frequently a source of tension when new team members arrive with different expectations. The healthiest IT cultures make these norms explicit—formalizing them into on-call rotations, severity definitions, and communication protocols—while the least healthy rely entirely on the informal compact and experience genuine confusion when it breaks down. Getting these norms right is, surprisingly, one of the most impactful things an IT team lead can do for team morale and retention.
Explore more IT culture and professional insights on our homepage, or get in touch with your own favorite unwritten rule story.