Introduction
Nobody includes company politics in the onboarding guide. Nobody teaches it in bootcamps. Nobody writes it in the job description. But spend enough years in this industry and you will encounter it — and if you are not prepared, it will cost you something. A project you were proud of. A team you had built carefully. A promotion that went to someone who asked for it less quietly than you did. Sometimes a job. Sometimes something harder to name — the enthusiasm that used to make the work feel worthwhile.
I have watched it play out across different companies, different teams, different project contexts. I have seen technically exceptional developers fired not because they wrote bad code but because they were inconvenient to the wrong person. I have seen products that genuinely served users shut down because the internal champion lost a budget argument. I have seen teams built over years dissolved in a single restructuring announcement that was dressed up as strategic realignment. I have watched good people — people who cared deeply about their work, who showed up every day with genuine investment — become versions of themselves that were quieter, more defensive, more calculating, and less capable of the kind of trust that good work requires.
I want to write about this honestly, because I think the silence around it is part of the problem. When we do not talk about what politics actually looks like, where it comes from, and how it operates, we leave people unprotected against something that is operating on them whether they acknowledge it or not.
This is not a cynical piece. It is an honest one. And there is a difference.
What Company Politics Actually Is
The word “politics” carries enough negative connotation that it is tempting to define it entirely as bad behaviour. But the fuller definition is more useful and more honest.
Company politics is the informal system of influence, relationships, and power that operates alongside the formal organizational structure. Every organization has both. The formal structure tells you who reports to whom and what the official decision-making processes are. The informal structure tells you who actually influences decisions, whose opinion carries weight beyond their title, whose approval you need even when you do not technically need it.
Politics in this neutral sense is not inherently harmful. Relationships matter. Trust matters. The ability to communicate well with different people at different levels of an organization is a genuine skill that makes work happen more smoothly. Understanding who the real stakeholders are and what they care about is useful knowledge for anyone trying to get something done.
The harmful version — the one this article is about — is when the informal influence system is used not to get good work done but to protect positions, acquire resources, undermine rivals, or advance individual interests at the expense of the organization’s actual goals. That is the version that costs people things. And it is significantly more common than most organizations like to acknowledge.
The distinction I use: constructive politics is influence in service of the work. Destructive politics is influence in service of the individual using it. The same behaviour can be either depending on intent and context, which is part of what makes the harmful version so difficult to identify and name clearly.
How It Operates — The Patterns You Need to Recognise
Political maneuvering in organizations rarely announces itself. It operates through mechanisms that have plausible alternative interpretations, which is what gives it deniability. Understanding the patterns is the first step to seeing them clearly.
Credit migration
Work is done by one person or team. The credit for that work migrates to someone else — usually someone with more visibility, more relationships with decision-makers, or more willingness to be present in the moments when attribution happens.
This is one of the most common patterns in software organizations, and it operates at every level. The junior developer whose architectural insight gets absorbed into a senior developer’s design proposal without attribution. The team that built the feature that shipped to great reception, while the product manager who presented it to leadership becomes the hero of the story. The technical lead whose documentation and knowledge transfer made the migration successful, while the manager who announced the migration takes the credit in the performance review.
Credit migration is almost never a single dramatic incident. It accumulates in small moments — meetings where you were not present, email threads that summarized your work without naming you, presentations that used your slides without your name on them. Any one instance is deniable. The pattern is not.
Information asymmetry as power
In organizations with political cultures, information is not shared freely — it is distributed strategically. Knowing something before others know it is a form of power. Controlling who learns what when is a political tool.
You recognize this pattern when you are consistently the last to know about decisions that affect your work. When conversations happened in rooms you were not in and conclusions were reached before you were consulted. When you discover that your manager had information about the project’s direction for weeks before sharing it with the team. When you are asked to execute on a decision without understanding the context that produced it.
Information asymmetry is also used offensively — sharing information selectively to create confusion, to position a rival unfavorably before a decision is made, to appear more knowledgeable than you are in front of decision-makers. The technical developer who shares a critical architecture concern with the right senior leader just before a planning meeting, ensuring a rival’s proposal looks uninformed. The manager who tells their team one thing and their leadership another, maintaining a different version of events for each audience.
Alliance building and coalition politics
Decisions in organizations are rarely made purely on merit. They are made by people, in relationships, with histories. The ability to build coalitions — groups of people who are aligned, who will speak up for each other, who will vote or advocate in the same direction — is a core political skill.
This becomes harmful when coalitions form along personal loyalty lines rather than interest alignment, when inclusion in the coalition is used to punish people who are not loyal rather than to advance a shared goal, or when the coalition exists primarily to protect its members from accountability rather than to get something done.
The team that excludes a particular developer from important discussions not because they lack relevant expertise but because they once disagreed with the coalition’s leader. The manager who gives preferential treatment — better projects, more visibility, salary advocacy — to the developers who are personally aligned with them rather than the ones doing the best work. The senior leader whose direct reports compete destructively for their favour because that favour determines outcomes in ways that performance does not.
The performance review as political instrument
Performance reviews are supposed to be an honest assessment of a person’s contribution. In politically charged organizations, they are often something else: a mechanism for managing people toward outcomes that the reviewer wants, regardless of the actual quality of the work.
The developer who had a difficult year personally, whose output dipped temporarily, whose honest review would be “struggling but fundamentally strong” receives a review that focuses disproportionately on the dip — because their manager has already decided to replace them and needs documentation to support that decision. The developer who did not have the best year technically but who is politically valuable to their manager receives a glowing review that positions them for a promotion they did not earn.
Performance reviews in these contexts are not measurements. They are instruments of intent that have been written to look like measurements.
The Disguises — How Politics Presents Itself as Business
This is the section I want to spend the most time on, because the disguises are what make harmful politics so difficult to name and resist. When the political action is dressed in business language, the person experiencing it is left questioning their own perception.
Cost-cutting and restructuring
“We are going through a restructuring to better align with our strategic priorities.” This sentence has ended careers of talented people who had nothing to do with the strategic priorities being realigned.
Restructuring is sometimes genuine. Companies evolve, markets change, organizational structures become misaligned with work realities. But restructuring is also one of the cleanest political tools available because it provides cover for almost anything. Eliminate a team whose leader challenged the wrong executive. Remove a role that is occupied by someone inconvenient. Consolidate two departments in a way that makes one of the department heads redundant — specifically the one who lost the internal competition.
The people affected by political restructuring face a particular difficulty: the stated reason (strategic realignment, cost efficiency, organizational clarity) is not obviously false. It might even be partially true. But the selection of who is affected — which teams are eliminated, which roles are made redundant, which people are asked to apply for their own jobs — often reflects political considerations rather than purely operational ones.
The Performance Improvement Plan
The Performance Improvement Plan (PIP) is perhaps the most widely misunderstood instrument in corporate management. It is described as a development tool — a structured opportunity for an underperforming employee to improve. In practice, in most of the organizations I have observed, it is a documentation process used to create a paper trail that supports a termination decision that has already been made.
This is not speculation. The human resources professionals who design PIPs understand this. Employment lawyers understand this. The managers who assign them, in the majority of cases, understand this. The employee receiving it is frequently the only person in the process who has not been told what it actually is.
A genuine PIP — one where the manager honestly wants the employee to succeed, where the goals are achievable, where the support is real — exists. I have seen it. But it is the exception. The pattern I have observed far more frequently: a developer who questioned a decision, or who had a conflict with a politically powerful colleague, or who was simply in a role that someone with influence wanted for someone else, receives a PIP with goals that are technically achievable but practically improbable given the support available. They are managed out over the following weeks with documentation that makes the termination look like a measured response to continued underperformance.
The cruelty of this instrument — and I use the word deliberately — is that it places the burden of the political decision on the individual. They are told the problem is their performance. They carry that with them. They question themselves. They may spend years believing they were genuinely inadequate when the reality is that they were politically inconvenient.
Project dis-allocation and visibility management
In organizations where interesting work is the currency — where the projects you are assigned to determine your growth, your visibility, and ultimately your progression — the allocation of work is a political instrument.
Being moved off a high-profile project just before it ships. Being assigned to the maintenance work that nobody presents to leadership. Being kept on a project that is going nowhere while your peers are moved to the one that has executive attention. These are not random — they are managed outcomes that reflect the political standing of the people receiving them.
A developer who is politically inconvenient gets moved to the unglamorous work. Their contributions become less visible. Their performance review, which emphasises visible contributions, suffers. Their case for promotion weakens. The cycle becomes self-reinforcing without any single event that can be clearly named as unfair.
Late salaries and withheld commitments
This one is specific to certain geographies and company types, but it deserves naming. Companies that delay salary payments, that withhold committed bonuses, that fail to honor equity vesting schedules or salary review commitments, are often using financial pressure as a management tool — whether consciously or not.
The developer who is owed a salary review that keeps being deferred. The commitment to a promotion that was given verbally and has been forgotten by the organization even though the developer has not forgotten it. The bonus that was “dependent on company performance” when the company had a good year but somehow did not materialize. The equity package that was part of the offer letter but is being questioned now that the developer wants to leave.
Financial tools used this way create dependency. A developer who is owed money, or who is waiting on a committed outcome, is a developer who stays — not because they want to, but because leaving would mean leaving behind something they are owed. The leverage is financial, but the mechanism is political.
”Culture fit” as exclusion
“We need someone who is a better culture fit” is one of the most elastic phrases in organizational management. It can mean almost anything, which means it means whatever the person using it needs it to mean.
Sometimes it describes a genuine concern about a person’s ability to collaborate, to receive feedback, to work within the norms of a functioning team. But it is also frequently used to exclude people who challenge authority, who raise uncomfortable questions, who do not perform the social deference that hierarchically-minded organizations reward. The developer who asks “why are we building this?” too persistently. The engineer who raises a technical concern in a meeting with leadership and does not frame it diplomatically enough. The person who simply does not belong to the social group that defines the culture.
“Culture fit” concerns are almost never formally documented, which makes them extremely difficult to challenge. They are raised in conversations about hiring or promotion decisions, and they leave the person about whom they were raised with no specific criticism to respond to and no formal process to appeal to. They are perfect political instruments precisely because they are so vague.
What It Does to People
I have been careful so far to focus on mechanisms rather than consequences, because I think understanding the mechanisms helps. But the consequences deserve honest attention because they are the part that matters most.
The good people who leave
The developers who have options — who are genuinely capable, who have built a track record, who are marketable — leave politically toxic environments. This is the rational response and I am not criticizing it. But it means that politically healthy environments lose their best people faster than their mediocre ones, because the people with the most to offer have the most choices. The ones who stay in toxic environments longest are often the ones who feel they cannot leave — those with financial dependencies, visa constraints, caregiving responsibilities, or a confidence that has been eroded by the politics they have been surviving.
The talent drain from political toxicity is real and is almost never captured in exit interviews, because exit interviews are conducted by HR and the truthful answer (“I’m leaving because my manager takes credit for my work and the promotion process is determined by social proximity to leadership rather than contribution”) is the answer you do not give when you still need references.
The good people who stay and change
Some people who encounter destructive politics do not leave. They adapt. They become more guarded, more calculating, more defensive. They stop sharing ideas openly because open ideas become credit that migrates. They start managing up more aggressively because they have learned that being good at the work is not enough — being seen by the right people matters more. They build alliances not because they want to but because they have learned that not having alliances leaves you exposed.
This adaptation is rational. It is also a loss. The developer who arrived with genuine enthusiasm and collaborative instinct and left as a political operator — the transformation is a cost that neither the individual nor the organization will ever formally account for.
The good people who are damaged
Not everyone who experiences destructive politics adapts successfully or leaves cleanly. Some people are genuinely damaged — their confidence, their trust in institutional structures, their ability to believe that effort and quality are connected to outcomes.
A PIP that was politically motivated rather than performance-based, received by someone who had no framework for understanding what was happening to them, can produce years of self-doubt. A public undermining by a politically powerful colleague can produce social anxiety about professional environments. A layoff that felt personal — that was, in fact, personal, even if it was described as structural — can produce a wariness about investing in work that persists long after the situation that caused it.
These are not dramatic outcomes. They are quiet ones. They show up as reluctance to speak up in meetings, as a tendency to keep work visible and protected rather than sharing it generously, as a calibrated distance from institutional commitments that were once made genuinely. They are the residue of political environments on the people who lived in them.
How Products and Projects Die
The political cost is not only personal. Products and projects absorb it too.
The product that solved a real problem for real users, built by a team that genuinely understood those users, shut down because its executive champion was outmaneuvered in a budget conversation by someone whose project had less merit but more political support. The technical platform that would have provided the foundation for a decade of development, quietly defunded because the architect who proposed it had the wrong relationship with the person who controlled the budget. The project that delivered on every technical metric but was cancelled because the team lead had been politically marginalised in the preceding months and there was nobody left to advocate for continuing it.
These deaths are not random. They follow the political topography of the organization. The projects that survive are not always the ones with the most merit. They are often the ones with the best-connected sponsors, the most politically skilled teams, or simply the ones that have not yet been touched by the internal competition.
The industry’s graveyard is full of genuinely good software that was killed not by the market or by technical failure but by the internal dynamics of the organizations that built it.
Politics as Survival Skill — Engaging Without Becoming
This is where I want to be careful, because the honest conclusion of everything above is uncomfortable: you cannot opt out of company politics. Refusing to engage with the informal influence system does not remove you from it. It simply means you are in it without any of the tools to navigate it.
The developer who keeps their head down, does excellent work, and trusts that merit will be recognized is not above politics. They are simply undefended against it. And in an environment where politics is operating, being undefended is its own vulnerability.
The question is not whether to engage with the informal systems of influence and relationship. It is how to engage without becoming the thing you are trying to survive.
Build relationships because they are real
The most durable political protection is genuine relationships — with people at different levels of the organization, across different functions, built over time through actual collaboration and honest communication. This is not networking in the transactional sense. It is investing in the human reality of the people you work with.
Genuine relationships are political capital because people advocate for people they trust and respect. But the reason to build them is not that they are capital. The reason is that they are valuable in themselves — that working with people you know well, who know you well, who trust your judgment and whose judgment you trust, is a fundamentally better experience than working among strangers.
The side effect is that you are better protected when political forces move against you. That is a benefit of investing in real relationships, not the reason to do it.
Make your contributions visible — deliberately, not performatively
Invisible work does not protect you in an environment where credit migrates. This is uncomfortable for developers who find self-promotion distasteful — and I include myself in that description. The instinct is to let the work speak for itself. The work does not speak for itself in an environment where political forces are controlling the narrative.
Making contributions visible means documenting decisions and their context, sharing progress in forums where the right people see it, writing up the technical problem and its solution in a way that preserves the thinking rather than just the output. This is not self-promotion — it is making the record accessible. The record protects you because it is harder to rewrite than a verbal attribution.
Name what you see — carefully, to the right people
Political dynamics that go unnamed are harder to address than ones that are named. A pattern of credit migration that a team never talks about is a pattern that continues. A manager who consistently gives unbalanced performance assessments and whose team never discusses it collectively is a manager whose behaviour persists.
The risk of naming is real — which is why “carefully” and “to the right people” are doing significant work in that sentence. Naming political dynamics to someone who is part of them is not helpful. Naming them to a trusted colleague or a trusted manager outside the immediate political system can be. The goal is not to create conflict. It is to make the pattern legible to someone who can do something about it, or at minimum to someone who can verify that your perception is accurate.
One of the most destabilizing effects of political environments is gaslighting — the experience of having your perception of what is happening contradicted by people whose interests are served by your perception being wrong. A trusted person who can verify “yes, what you are seeing is real” provides a form of protection that technical skills cannot.
Know when to leave
This is the survival skill most people learn too late. Political environments have a cost that compounds over time. The developer who stays too long in a toxic political environment does not exit at the same capability and confidence level they entered. The environment extracts something.
Knowing when the cost has exceeded what the role is worth — financially, professionally, personally — and leaving before the damage becomes lasting is a form of self-protection that the culture around work makes difficult. We are taught to persist, to be loyal, to not give up. In genuinely toxic political environments, persistence is not strength. It is exposure.
Leave when you have determined that the environment is not going to change and that you cannot navigate it without becoming someone you do not want to be. Not reactively, not dramatically — but with clarity about what is happening and what staying will cost you over time.
What Organizations That Take This Seriously Do Differently
Not every organization is equally politically toxic. The ones that maintain lower political toxicity tend to do specific things.
They make decision-making processes explicit and public. When the criteria for promotions, project allocations, and performance assessments are visible and consistently applied, the space for political manipulation narrows. Opacity is where politics lives.
They create multiple paths for escalation. A developer who has a problem with their direct manager should have somewhere to take that problem that does not route through the manager. Skip-level conversations, HR processes that are genuinely independent, anonymous reporting mechanisms — these do not eliminate politics but they provide checks on the most harmful manifestations.
They measure and reward collaboration, not just individual performance. In environments where individual performance is the only currency, political behaviour that advances individual performance at others’ expense is rational. Measuring team outcomes, team health, and cross-functional trust changes the incentive structure.
They treat credit attribution seriously. Who is named in project retrospectives, who presents to leadership, who is referenced in success communications — these are not trivial decisions. Organizations that are intentional about attribution — that go out of their way to name the people who did the work — reduce the incentive and the opportunity for credit migration.
They pay people on time and honor their commitments. This sounds like table stakes. In practice, many organizations fail it. Consistent, reliable follow-through on financial commitments is a form of institutional respect that signals that the employment relationship is genuine rather than exploitative.
Conclusion
Company politics is not going away. It is a feature of human organizations, not a bug that can be patched. Power differentials exist. Resources are finite. People have interests that do not always align with the organization’s interests. The informal influence system will always operate alongside the formal one.
What can change is how clearly we see it, how honestly we name it, and how deliberately we engage with it. The developer who refuses to acknowledge that politics exists is not above it — they are underneath it. The developer who engages with the informal systems of influence in service of the work, who builds genuine relationships rather than transactional alliances, who makes their contributions visible without performing them, and who knows when an environment is costing more than it is providing — that developer is not immune to politics. But they are better equipped to navigate it.
The people who are most damaged by destructive politics are usually the ones who had the most genuine investment in their work and the least preparation for what political environments actually look like. The enthusiasm that makes someone a great developer — the care about quality, the investment in the team, the belief that good work produces good outcomes — is the same quality that makes them vulnerable to an environment where those things are not the actual currency.
The work matters. The people matter. The thing that politics most consistently destroys is both of those — the quality of the work and the wellbeing of the people doing it.
Seeing it clearly is the beginning of protecting both.
If you are in an environment where you are questioning whether what you are experiencing is real — the gaslighting, the credit migration, the managed performance process that feels disconnected from your actual performance — trust your perception. Find one person you trust and describe what you are seeing. If they tell you it is real, believe them. If they tell you it is not, find another person. Your instincts about the environment you are living in are more reliable than the institutional narrative that has an interest in your uncertainty.