The Context
A VP of Product shares a proposal in a leadership meeting. It's a restructuring plan - move from siloed feature teams to a platform model. She's spent three weeks on it. The data is solid. The logic is clear. She presents it in twelve minutes. The room nods. The CEO says "interesting direction." The CTO says "let's explore this further." Everyone agrees to reconvene next week.
Two days later, she opens a strategy deck circulated by the COO's office. Page seven contains her restructuring framework - same terminology, same phasing, same logic - attributed to "cross-functional leadership alignment." Her name appears nowhere. The COO's chief of staff is listed as the author.
She learns about it not from the COO, not from the CEO, but from a director on her own team who received the deck in a separate distribution list she wasn't included on. She reads it twice. The feeling isn't anger at first - it's disorientation. Did this actually happen? Is she misreading it? Maybe the COO had similar ideas independently?
"I could confront it. But what would I say? 'That's my idea'? In a culture where everything is 'collaborative,' claiming ownership looks petty. And silence? Silence confirms that the game works."
She doesn't confront it. She doesn't say anything in the next meeting. The restructuring plan moves forward - under the COO's sponsorship. Six months later, when it produces results, the COO presents the outcomes at the board meeting. The VP watches from four seats away. She's thanked for "supporting the initiative."
This isn't an anomaly. This is a system. And if you've spent any time in organizations above a certain size - typically past the 200-person mark, though it can start earlier - you've seen some version of this play out. Not once. Repeatedly. With different actors, different stakes, but the same underlying mechanics.
The variations are endless. The engineering lead whose architecture proposal gets rejected in a review, only to resurface three months later as the CTO's "vision." The marketing director who builds a campaign that drives a 30% lift in conversions, only to watch the SVP of Growth present those numbers at the all-hands without mentioning her team. The data scientist who flags a critical flaw in the recommendation engine, gets told to "park it," and then watches the same flaw become a crisis six weeks later - at which point the person who told her to park it leads the "war room" response and earns a promotion for "decisive leadership."
Each of these scenarios shares a common architecture: value is created in one place and captured in another. The creator is separated from the credit. And the separation is maintained not through force, but through social norms - "collaboration," "team effort," "we don't do individual attribution here." These norms sound progressive. In practice, they serve whoever is best positioned to claim collective work as their own.
Corporate intrigue is what happens when political maneuvering replaces actual management. It's a system where information becomes a weapon, alliances become strategy, and results take a permanent back seat to positioning. It doesn't announce itself. It doesn't have a manifesto. It simply becomes the way things work - until the people who build things stop building and start playing, or stop showing up entirely.
The Mechanics
Corporate intrigue isn't random backstabbing. It's a structured system with identifiable components. Once you see the mechanics, you start recognizing them everywhere - in reorgs, in hiring decisions, in which projects get funded and which get starved. There are four primary mechanisms that keep the machine running.
In an intrigue-driven organization, the most valuable asset isn't competence - it's information. Who knows what, when they learned it, and who told them becomes the actual organizational currency. A director who has early access to layoff plans holds more power than one who delivers better results. A manager who lunches with the CEO's chief of staff twice a week knows the real priorities - not the ones in the quarterly OKRs, but the ones that actually drive decisions.
This creates a secondary economy. People trade information like commodities. "I'll tell you what happened in the exec offsite if you tell me what the board said about the acquisition." Access to information becomes a proxy for status, and controlling the flow of information becomes a governance tool. Leaders who master this dynamic don't need to be competent managers - they just need to be the node through which critical information passes.
Consider what happens at a company like this during a reorganization. The formal announcement comes on a Tuesday. But by the previous Friday, certain people already knew. They'd already positioned themselves. They'd already had conversations with the right stakeholders. By the time the "surprise" lands, the political map has already been redrawn. The people who didn't know? They're scrambling. They're reacting. They're already behind.
Promotions, resource allocation, project assignments, headcount - in theory, these are merit-based decisions. In practice, in an intrigue system, they follow alliance lines. The question isn't "who's the best candidate?" It's "who's aligned with whom?"
A VP pushes for her protégé to lead a high-visibility initiative. The protégé may not be the strongest candidate, but the VP has leverage - she supported the CFO's cost-reduction proposal last quarter, and now the CFO supports her staffing request in the talent review. This isn't corruption in the legal sense. No money changes hands. No rules are technically broken. But the outcome is identical: decisions are made based on networks rather than competence. The engineer who shipped the most impactful feature last year gets passed over for the one who plays golf with the SVP.
Over time, people notice. They don't need a memo to understand the real promotion criteria. They see who gets elevated and reverse-engineer the logic. The conclusion is always the same: relationships matter more than results. And once that conclusion takes hold, behavior shifts accordingly. The best engineers start spending less time coding and more time "building relationships." The most effective product managers start attending every optional leadership dinner. The system reproduces itself.
In a well-run organization, objectives are clear. Success criteria are defined. Accountability is traceable. In an intrigue system, ambiguity is a feature, not a bug. Goals are kept intentionally vague so that success can be claimed by multiple parties and failure can be attributed to external factors.
Watch how this works in practice. A CEO announces a "digital transformation initiative." What does that mean? It could mean cloud migration. It could mean customer experience redesign. It could mean hiring a Chief Digital Officer. The ambiguity is the point. Three different SVPs interpret it differently, each launching their own version. When one succeeds, the CEO claims vision. When another fails, it was "a learning experience." The SVP who failed wasn't executing the "real" vision anyway.
Strategic ambiguity also serves as a loyalty test. When the leader says something vague, the politically skilled interpret it "correctly" - meaning they guess what the leader actually wants and align accordingly. Those who take the words at face value and execute literally are seen as lacking "organizational awareness." The ability to read between lines that were intentionally left blank becomes a core competency.
Every intrigue system needs a pressure release valve. When things go wrong - a product launch fails, a major client churns, quarterly numbers miss - someone must absorb the blame. In healthy organizations, post-mortems are blameless and systemic. In intrigue organizations, blame flows downward through pre-established channels.
The politically connected are insulated. They have sponsors who protect them, allies who deflect attention, and enough informational leverage to redirect narratives. The unconnected - often the most technically capable, the ones who were too busy building to play the game - become convenient targets. "The implementation team didn't execute." "Engineering underestimated complexity." "The regional lead failed to localize the strategy."
A telling pattern: in intrigue-heavy organizations, the same senior leaders survive multiple failures while mid-level managers rotate through the blame cycle every 12-18 months. The senior leaders aren't better at their jobs. They're better at the game. They've built scapegoating infrastructure - layers of delegation designed not for efficiency but for deniability. When asked "what went wrong," they can always point to someone else's execution. Their strategy was sound. It was the implementation that failed.
"In healthy organizations, power flows from results. In intrigue organizations, power flows from positioning. The difference isn't subtle - it's just invisible to anyone who hasn't seen both."
The Symptom
Meetings before meetings. That's the single most reliable diagnostic. If the real decisions in your organization happen in hallway conversations, dinner invitations, private Slack channels, and one-on-one "alignment sessions" before the official meeting - you're living inside an intrigue system.
The official meetings become theater. Confirmation of what was already decided. Everyone presents positions they've already locked in through back-channel negotiations. The "discussion" is choreographed. The "decision" is pre-determined. The people who walk in thinking this is an actual deliberation are the ones without access to the pre-meeting.
You can spot it in the body language. Watch who looks at whom when a "new" idea is presented. Watch who nods first. Watch who stays silent. The silent ones either already agreed privately - or already know they lost. The real tell is when someone proposes something and three people immediately support it using slightly different language. That's not organic agreement. That's a coordinated bloc.
"I realized the meetings were performative when I noticed that the CEO never looked surprised. Not once. Every 'decision' was something he'd already discussed with his inner circle. The meeting was just the public ratification."
The downstream effects are corrosive. People start spending more energy on relationships than results. "Managing up" becomes a recognized skill rather than a dysfunction. When a new employee asks how to succeed, the honest answer stops being "do great work" and becomes "make sure the right people know about your work - and make sure you're aligned with the right people before you start it."
Calendar analysis tells the story. In an intrigue-heavy organization, senior leaders spend 30-40% of their time in one-on-one "syncs" that have no documented agenda and no recorded outcomes. These aren't coaching sessions. They're alliance maintenance. They're information trading posts. They're the real organizational structure - invisible on the org chart, but more powerful than any reporting line.
The best operators - the ones who actually build things - face a binary choice. Learn the game or leave. Some learn it. They compartmentalize. They do their real work in the margins and spend the rest of their time navigating the political landscape. They're effective, but they're operating at 40% capacity because 60% goes to survival. Others leave. Quietly. They don't write dramatic resignation letters. They don't make scenes. They just accept a LinkedIn recruiter's message one Tuesday afternoon and are gone within a month. The organization barely notices - until it does. Until the institutional knowledge walks out and nobody remaining can explain why the system works the way it does.
A particularly insidious symptom: watch how credit flows. In intrigue organizations, credit is a zero-sum resource. If one person gets recognized, another feels diminished. Public recognition becomes a political act - not a celebration of achievement, but a signal of alliance. "I'm publicly praising you" means "you're in my camp." Not praising someone who clearly deserves it means "you're not." People start tracking recognition patterns the way traders track market signals.
Another diagnostic: observe what happens to dissent. In healthy organizations, someone who pushes back on a proposal is seen as engaged - they care enough to challenge the idea. In intrigue organizations, dissent is interpreted through a political lens. "Why did she challenge that proposal? Is she aligned with the other faction? Is she positioning for that role?" The substance of the disagreement becomes irrelevant. Only the political implications matter. Over time, this kills intellectual honesty. People stop challenging ideas not because the ideas are good, but because challenging them carries political risk. Bad decisions go unchallenged. Projects that everyone privately knows will fail get funded anyway because nobody wants to be the person who "isn't supportive."
The final symptom is perhaps the most damaging: talent arbitrage. The best people in an intrigue-driven organization are perpetually undervalued internally and overvalued externally. The market knows their worth; the organization discounts it because they're not politically positioned. This creates a constant talent drain - not of the worst performers, but of the best ones. The organization retains the politically skilled and loses the operationally excellent. Over time, the average competence drops while the average political sophistication rises. The organization gets better at intrigue and worse at everything else.
Why It Persists
The obvious question: if intrigue is so destructive, why don't organizations fix it? The obvious answer: because the people with the power to fix it are the ones who benefit from it.
Leadership often benefits from intrigue because it creates dependency. A leader who is the central node in an information network is irreplaceable - not because of their competence, but because of their position. They know what the board discussed behind closed doors. They know which executive is on thin ice. They know the real budget numbers before finance publishes them. This information monopoly makes them essential regardless of their actual management ability.
Consider the incentive structure. A CEO who operates through transparent processes and clear accountability is, in some sense, replaceable. The system works without them. Any competent leader could step in and follow the established playbook. But a CEO who operates through personal relationships, informal alliances, and selective information sharing has made themselves the system. Remove them and the entire invisible infrastructure collapses. Nobody knows who's really aligned with whom. Nobody knows the real priorities. The organization is paralyzed - not because it lost a great leader, but because it lost the only person who understood the game.
"The intrigue isn't a bug - it's a governance model. It persists because dismantling it would mean redistributing power. And the people who hold power rarely volunteer to give it away."
There's a deeper structural reason too. Intrigue thrives in organizations where the connection between individual contribution and organizational outcome is unclear. In a ten-person startup, it's hard to play political games because everyone can see who's building and who's posturing. But in a 5,000-person enterprise with seven layers of management, the causal chain from effort to impact is so long and so complex that narrative matters more than reality. If you can control the narrative about why something succeeded or failed, you can control career trajectories - including your own.
Boards of directors often enable intrigue without realizing it. They evaluate CEOs on stock price and quarterly earnings - metrics that can be manipulated through financial engineering, accounting choices, and timing of announcements. They rarely examine organizational health, decision-making quality, or talent retention patterns at the middle-management level. A CEO can preside over an intrigue-ridden organization for years, delivering adequate financial results while the best talent quietly drains away, and the board won't notice until the pipeline of future leaders is empty.
HR departments, which theoretically exist to counter dysfunction, are frequently co-opted. In intrigue systems, HR becomes an enforcement arm for the dominant political faction. "Culture fit" assessments screen for political compatibility. Performance reviews become tools for legitimizing predetermined outcomes. The 360-degree feedback process, designed to surface honest perspectives, gets gamed - people coordinate their responses, and the HR team either doesn't notice or doesn't care. The system has captured its own immune system.
There's also a temporal dimension. Intrigue compounds over time. Each political decision creates precedent. Each alliance-based promotion sends a signal. Each unpunished act of credit theft normalizes the behavior. After two or three cycles - roughly 18 to 24 months - the intrigue culture becomes self-sustaining. New hires are socialized into it before they even understand it. They observe what gets rewarded and adjust accordingly. "That's just how things work here" becomes the universal explanation, which is really a universal surrender.
Perhaps most importantly, intrigue persists because it's never named. It operates below the level of conscious organizational awareness. There's no agenda item that says "Political Maneuvering - 30 minutes." There's no Slack channel called #office-politics. It exists in the negative space between formal processes - in the things that aren't said, the meetings that aren't recorded, the decisions that aren't documented. By the time someone names it, they're usually the one being labeled "not a cultural fit."
The Antidote
Dismantling corporate intrigue isn't about making people nicer. It's about redesigning systems so that political maneuvering becomes more expensive than actual performance. The goal isn't to eliminate human nature - people will always form alliances and manage impressions. The goal is to make the organization's formal mechanisms more powerful than its informal ones.
Structural Countermeasures
-
→
Force transparency on decisions. Every significant decision - hiring, promotion, resource allocation, project prioritization - requires a documented rationale. Not a post-hoc justification, but a real-time explanation written before the decision is implemented. Public attribution of ideas must be traced to their origin. If a proposal appears in a deck, the original author is credited. Make idea theft structurally impossible by timestamping contributions in shared systems.
-
→
Kill meetings before meetings. If pre-meeting alignment is happening, make it visible. Require that any pre-meeting discussions be summarized and shared with all meeting participants. Better yet, use asynchronous pre-reads that everyone receives simultaneously. When someone arrives at a meeting with a pre-formed position, they should be required to explain when and with whom they formed it. The discomfort this creates is the point.
-
→
Create promotion criteria that can't be gamed by proximity. Define what "high performance" means with observable, measurable evidence. Require promotion cases to include peer testimony from people outside the candidate's immediate alliance network. Use skip-level reviews. Implement blind evaluation stages where names are removed from performance data. If proximity to power is the actual promotion criterion, at least make people admit it out loud.
-
→
Reward results with evidence, not narratives. Separate storytelling from performance measurement. The person who presents the quarterly results should not be the only person evaluated on those results. Track contributions at the team level. Use data trails - commit logs, project management artifacts, customer outcomes - to verify who actually did the work. When someone claims credit for an outcome, make the verification process visible and routine.
-
→
Make the cost of politics visible. Track regrettable attrition - the people you didn't want to lose. Exit interviews are unreliable because departing employees self-censor. Instead, survey current employees anonymously about decision-making fairness, information access, and political dynamics. Publish the results. If 40% of your engineering team says that "knowing the right people matters more than doing great work," that's a data point your board should see. Intrigue survives in darkness. Measurement is sunlight.
None of this is easy. Every one of these countermeasures will be resisted - by the very people who benefit from the current system. They'll say it's "bureaucratic." They'll say it "slows things down." They'll say the organization needs "trust, not process." Listen to who says these things. Follow their incentives. Trust is what you earn when your decisions can withstand scrutiny. If someone resists scrutiny in the name of trust, they're protecting something - and it's probably not the organization's interests.
"The ultimate test: would the people who make decisions in your organization make the same decisions if their rationale were publicly visible? If the answer is no, you don't have a trust problem. You have a transparency problem wearing a trust costume."
One more thing - and this matters for the individual, not just the organization. If you're operating inside an intrigue system and you recognize it for what it is, you face a personal decision. You can learn the game and play it well. Many smart, ethical people do this. They rationalize it as "working within the system" and sometimes they're right - you can protect your team and push good outcomes by being politically savvy. But there's a cost. Playing the game consumes cognitive resources that could go toward actual work. And over time, the game changes you. You start seeing relationships as strategic assets rather than human connections. You start withholding information reflexively. You become what you originally diagnosed.
The alternative - leaving - isn't failure. It's a legitimate strategic response to an environment that can't be changed from your position. The best move isn't always to fight. Sometimes the best move is to find an organization where your energy goes toward building rather than surviving. The clearest sign that you should leave: when you catch yourself evaluating a new idea not by its merit but by its political viability. When "will this work?" gets replaced by "who will this threaten?" - you've already absorbed the system's logic. That's the moment to go, before the absorption becomes permanent.
it's a feature of systems with unclear accountability.
When the rules of the game are invisible, people invent their own.