liveBook · Manning

Organizational politics

As explained in Think Like a CTO

Office politics is organizational conflict or influence behavior driven by emotion and personal interests rather than shared factual information.

Organizational politics arises when emotion and personal interests displace shared facts in workplace decisions. It can appear within a team or across a company, even where people insist there is no politics. The aim is not to find a foolproof way to eliminate conflict, but to recognize patterns early and bring conversations back to specifics. section 2.7 section 2.7.1 section 2.7.2

Watch for two patterns:

  • Fiefdoms: one person or a loosely allied group puts its own goals first and asserts control over an area. Even friendships that seem innocent can lead others to perceive an exclusive group. section 2.7.1
  • Bullying: intimidation, rudeness, irrational behavior, or inconsistent decisions and actions. Distinguish it from assertiveness rather than treating every firm disagreement as bullying. section 2.7.1

An outburst on a conference call

A CEO entered a conference call and angrily berated the CTO without knowing who else was listening; a client could have been present. The private equity firm learned of the outburst and fired the CEO. The incident shows how intimidating behavior can reach beyond the people directly involved. section 2.7.1

When a conversation turns political, try to restore clarity without assuming a fixed script will work:

  • Check your own behavior first. Ask a trusted colleague or friend whether you show the same traits you notice in others. section 2.7.2
  • Address threatening or passive-aggressive behavior directly. Calm directness, sometimes with humor, can interrupt a hostile exchange. section 2.7.2
  • Avoid vague requests and shifting interpretations. Ask for specific examples, clarify the grievance, and confirm what you understood before conceding a point or becoming defensive. section 2.7.2

A new technology leader should listen before trying to change the landscape. One-on-ones can surface what team members would fix, but their answers are individual viewpoints, not yet a complete diagnosis. Meet peer executives, learn why existing choices were made, and be thoughtful about people who supported the previous technology roadmap. Where change is warranted, frame it as a positive enhancement rather than an attack on earlier decisions. Ask: Which concerns are supported by specific examples, and whose perspective have I not heard? section 14.7 section 2.9

How Think Like a CTO covers it

How deep it goes
Defines office politics, distinguishes common behaviors, and gives mitigation techniques without promising a foolproof process.
Examples
Uses a CEO’s conference-call outburst and new-leader one-on-ones to show both visible conflict and quieter discovery.
What it assumes
Assumes workplace experience with colleagues and executives while defining office politics and distinguishing bullying from assertiveness.
What you can do after
Practice/perform calmer responses by requesting specifics, checking your own behavior, and listening before changing an inherited roadmap.
How it connects
Links politics to fiefdoms, bullying, organizational culture, and changes to a technology roadmap.
Cover of Think Like a CTO
liveBookmanning.com
Read Think Like a CTO on liveBook Get the book at manning.com

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a CTO. The section links point to the parts of the book it draws on.