How corporate politics works is mostly incentive design plus storytelling under constraints. Headcount is easy to measure. Impact is fuzzy. Reorgs fix the business and also park promotions, retention, and exits. Engineers who hate this still live inside it. Get good enough to protect your team and advance without turning into a pirate.
Empire building: why people chase org charts
Empire building means optimizing for more humans more than for outcomes. It thrives because counting people is objective while comparing feature impact to infrastructure impact is a fight. Leaders then default to "42 reports beats 17."
Some companies even write thresholds: director needs roughly 80 to 90 people. That creates a literal cash bonus for accumulating headcount, even when a leadership principle says there is no bonus for more people. You then see shell games: park a team under someone for six months, check a box, move them back, or use grace periods and "find another director seat" instead of true down leveling.
Flat headcount eras make it worse. Growth used to mean new hires. Stagnation means cannibalism: eat scope next door because you cannot hire. Senior leaders cannot let rogue pirates raid inside the org. They either find a defendable path, convince patience, or remove the septic actor and redistribute.
How reorgs really get packed
Triggers are usually business change, acquisition, new bets, or a boss leaving and cascading moves. Backfills are rarer than "put Ethan under this leader to stretch them." Once a reorg ship leaves the dock, leaders ask what else can ride: retain stars, starve low performers of juicy work, set high performers up, manage someone toward exit with "other."
There is always a narrative for auditors and a quieter second list. Sometimes leaders are direct about retention. Sometimes they sell only the business story. Too many reorgs cost people, so when one finally happens, it gets overloaded.
Career asks: nice is not always a compliment
Quiet high performers often wait while managers save the squeaky valuable peer who might leave. That is not always malice. It is triage. If you never say what you want, busy leaders assume you will be fine.
Pushy has an upper bound. Too much and you become a net negative and a "no" makes you leave. The skilled middle: professionally firm, interpersonally warm. Example framing: my career is very important to me; I need to understand how important it is to the company, because if those are misaligned I need to think about that. Clear signal without cartoon extortion. Tune the sharpness to culture.
Deal making beats blank demands. High performers trade: I will deliver X if you help me reach Y. Classic five words: solve problems for your boss. Even imperfect bosses keep the people who make their life easier. Also invent: ask what they need, and propose small bets they can approve without micromanaging every percent of your org.
Scope without piracy
Instead of "give me that team," say you want what is best for the org and you are ready to step up when an opening appears, and you will stay through the shake. Reliability in a reorg often beats raw brilliance when leaders need a stable captain. Yes to hard, unglamorous scope can grow you fast if you can later narrate it as level appropriate accomplishment.
Bad managers and "mutiny"
Skips often resist lone complaints. Believing you means three problems: fix or remove the manager, backfill, and cover the work. Believing you are high maintenance is easier. Never escalate alone on a pattern of harm. Sanity check peers first. Bring multiple willing voices.
Cleaner first path: make a business case to move without attacking the manager. Or blame free: we are not compatible; I need a change; the real choice is keep me in your org in a different seat or lose me entirely, if that is true. Plan wording before the room. Delivery and timing matter as much as content.
Org vs org: stories beat raw facts
Teams belittle distant work. Respect falls with distance. Defense: make unsexy maintenance visible, delay with "reorgs cost six months of momentum," counterpropose consolidation under you only if you must, and prefer light on motives plus a strong performance story. Offense that is still ethical: a real value case for combining teams. Helping a struggling area before casually suggesting consolidation beats dumpster fire gossip.
Managers are umbrellas or funnels when pressure rains down. If yours funnels everything onto the team, change the safety balance: make it safer to push up, or unsafe to keep accepting fourth weekend duty without a plan. Soft power also comes from ideas pitched to people who can fund them, not only from recursive headcount.
Influence skill without becoming Darth Vader
Influence and politics share techniques. Motive decides whether it is service or predation. Do not treat humans as APIs. See them as people under pressure, then ask how you can help them help you. Positive back channeling: let stakeholders raise concerns privately, feel heard, and buy in emotionally before the big room. Negative backroom sabotage eventually gets smelled.
Slippery operators tell themselves they are "practical," not evil. Redirect their narrative toward cooperation when witnesses and rising stars make betrayal not worth it. Be a porcupine: not worth biting.
Promotions, firings, and the duct taped org
- What got you here will not get you there. Learn the next level's skills; stop only doing the current job harder.
- Senior promo slots are scarce. Trust and "do people want you in the room" matter when skills are close.
- Champions rarely appear by magic. Put peers on notice early for feedback, preferably with your manager's intro.
- You almost never get promoted over your manager's objection. Get them onboard or change bosses.
- Firings of ICs and managers often hide style clash under a performance label. Managers are harder to remove because work is fuzzier and they know the system.
Orgs start as clean architecture diagrams and ship as special cases and duct tape. Leaders still aim for performance and fairness, then deadlines and difficult humans punch the plan in the face.
If you hate politics
Choose leaders who reward craft. Work on hard enough problems that expertise creates leverage. Prefer high growth where opportunity is positive sum. Still learn warm firm language. Relationships control progress more than pure technical rightness. For the drain of mid senior leadership politics, see what drains leaders most.
Manager map
| Reality | Naive response | Skilled response |
|---|---|---|
| Headcount equals status | Pretend impact always wins | Push impact narratives and resist shell games |
| Reorgs carry second motives | Believe only the slide | Ask who is retained, stretched, or parked |
| Quiet loyalty is invisible | Wait forever | State career needs warmly and firmly |
| Lone complaint about a boss | Mutiny solo | Corroborate, or move on business grounds |
| Cross org friction | Rage in Slack | Story, witnesses, and make predation costly |
Bottom line
Corporate politics is not a separate sport from management. It is how humans allocate scarce status, headcount, and belief under incomplete metrics. Understand empire incentives, packed reorgs, deal making, and narrative skill so you can advocate, retain talent, and defend teams. Stay firm without needing anger as fuel. Solve real problems for your boss and your org. You do not have to love the game. You do have to see the board.
Frequently asked questions
Why does empire building exist?
Headcount is easy to count and impact is fuzzy. When promotions implicitly or explicitly require large teams, ambitious leaders chase people. Fix incentives toward defendable impact, not raw recursive reports.
Are reorgs only about the business?
They usually start with a business trigger, then leaders pack retention, promotion scope, stretch assignments, and sometimes gentle exits onto the same change. Expect a public narrative and quieter second motives.
Should engineers avoid politics?
You can minimize it by choosing growth areas and leaders who reward craft, but human incentives do not disappear. Learn warm, firm career asks and relationship skill, or others who do will set your path.
What should you do about a bad manager?
Prefer a strong business case to move teams first. If escalating, never mutiny alone. Multiple corroborating voices beat a lone complaint that a skip can dismiss as high maintenance.
Related: hardest parts of mid to senior management, what stops managers from promoting someone, should you say something to your manager.
Prefer prepared conversations over memory alone? Explore iSilta features or try the product demo.