Influence & Organizational Politics

Why Technical Leaders Struggle with Influence

Engineering culture values meritocracy — the best idea should win on its technical merits. This creates a blind spot: engineers assume that if they build a compelling technical argument, the organization will adopt it. In reality, most decisions at scale involve competing interests, incomplete information, and human dynamics that pure technical arguments cannot resolve.

The uncomfortable truth: at the engineering manager level and above, your impact is bounded more by your influence than by your technical skill. You can design the perfect architecture, but if you cannot get organizational buy-in, funding, headcount, and cross-team cooperation, it dies on the whiteboard.

This is not cynicism. It is operational reality. Influence is a leadership skill, not a political game.

---

Power and Influence — The Fundamentals

French and Raven’s Bases of Power (1959)

Still the most useful taxonomy for understanding where influence comes from:

Power Base	Source	Engineering Example	Durability
Legitimate	Formal role/title	“I’m the EM, so I decide team structure”	Low — only works within direct reports, evaporates in cross-team contexts
Expert	Knowledge and competence	“She designed our distributed tracing system — listen to her on observability”	High — but domain-specific. Expert power in backend does not transfer to frontend.
Referent	Personal trust and respect	“I want to work on his team because he develops people”	Highest — portable across roles, teams, organizations. Takes years to build.
Reward	Ability to provide rewards	“She controls bonus allocation and project assignments”	Moderate — effective but creates transactional relationships
Coercive	Ability to punish	“He will PIP you if you miss targets”	Lowest — creates compliance, not commitment. Destroys trust.
Informational	Access to valuable information	“She is in the leadership meetings and shares context with the team”	Moderate — powerful in information-scarce environments

The EM’s Power Mix

For an engineering manager leading 16 engineers, your practical power mix is:

• Legitimate: Limited. Your authority covers your team, but most important decisions require cross-team alignment where you have no authority.
• Expert: Valuable but insufficient alone. You know the technical landscape, but so do other EMs and Staff Engineers.
• Referent: This is your primary asset. Build it deliberately.
• Informational: High leverage. Translate leadership context for your team. Translate team reality for leadership. Being the bridge is powerful.

The implication: invest disproportionately in referent and informational power. These are the bases that work in the cross-functional, matrixed contexts where your most important work happens.

---

Influence Without Authority — The Core Skill

Most of your highest-impact work as an EM requires influencing people who do not report to you: peer EMs, product managers, designers, platform teams, your skip-level leadership, partner teams in other business units.

The Influence Model (Cohen & Bradford, 2005)

The core insight: influence works through reciprocity and exchange, not persuasion. People give you what you need because you give them what they need — even when neither of you has formal authority over the other.

The currencies of exchange:

Currency Type	Examples	How to Use
Task-related	Resources, information, support, budget, headcount	“I can lend you two engineers for the migration sprint if your team can handle our on-call next week”
Position-related	Visibility, reputation, endorsement, political backing	“I will advocate for your proposal in the leadership meeting if you support our API standardization effort”
Relationship-related	Understanding, acceptance, personal support	“I heard about the reorg stress — let me know how I can help” (genuine, not transactional)
Personal-related	Gratitude, ownership, self-concept validation	“Your team’s observability work made our incident response 40% faster — I mentioned this to [VP]”
Inspiration-related	Meaning, purpose, contribution to something larger	“This platform work is not just infrastructure — it is what enables us to ship AI to 10M customers”

Practical Influence Tactics

1. Build the relationship before you need it.

The worst time to build a relationship with a peer EM is when you need them to prioritize your dependency. By then, you are transacting from zero trust. The best time was three months ago at a casual coffee chat where you learned about their team’s challenges and offered help with no strings attached.

Tactical: Schedule monthly 1:1s with every peer EM and key stakeholder. No agenda beyond “what is on your mind and how can I help?” This feels like overhead until the day you need something — then it is the most valuable investment you made.

2. Understand their world before asking them to understand yours.

Before requesting cross-team support, spend 30 minutes understanding the other team’s goals, constraints, and pressures. Frame your request in terms of their priorities, not yours.

Bad: “We need your team to build an API for our AI platform.” Good: “I know your team is measured on developer adoption. Our AI platform would drive 200+ developers to your API, which directly hits your Q3 adoption KR. Here is how we could structure the work to minimize your team’s investment.”

3. Create reciprocity before making asks.

Proactively share useful information, make introductions, give credit publicly, offer help. Build a positive balance in the relationship bank account before making withdrawals.

4. Use “commitment and consistency” ethically.

People tend to follow through on commitments, especially public ones. Get verbal alignment in a 1:1 before the big meeting. “Would you be supportive if I proposed X in Thursday’s architecture review?” A small yes in private makes a public yes much more likely.

5. Frame as mutual problem-solving, not as a request.

“How do we solve the latency problem that is affecting both our teams?” positions you as allies working on a shared challenge. “Can your team fix the latency issue?” positions you as a requestor and them as a resource.

---

Coalition Building

For significant organizational changes (platform adoption, architectural shifts, process changes), individual influence is insufficient. You need a coalition.

Building a Winning Coalition

Step 1: Stakeholder mapping. List every person who has influence over your initiative’s success or failure. For each, map:

• Their interest (high/low) in your initiative
• Their influence (high/low) over outcomes
• Their current position (supporter/neutral/opponent)
• What they care about (their currencies)

Step 2: Start with the easy wins. Approach natural allies first — people whose interests align with yours. Build momentum and visible support before approaching neutral parties.

Step 3: Convert neutrals. Neutrals become supporters when you show them clear benefit or remove their concerns. Most neutrals are not opposed — they are busy. Make it easy for them to say yes. Do the work of understanding their constraints and framing the benefit.

Step 4: Manage opponents strategically. Not every opponent can or should be converted. Understand why they oppose:

• Interest-based opposition: Their team loses resources/scope. Address by finding a win-win or compensating trade.
• Belief-based opposition: They genuinely think your approach is wrong. Engage technically. If they have valid concerns, incorporate them — you will build a better solution and potentially convert them.
• Political opposition: They oppose because your success threatens their position. This is the hardest. Sometimes the right move is to work around them rather than through them.

Step 5: Create a critical mass. You do not need unanimous support. You need enough supporters in the right positions that the initiative becomes inevitable. In most organizations, this is 3-5 key stakeholders who collectively control the relevant resources and decisions.

The First Follower Principle

From Derek Sivers’ famous TED talk (adapted): in organizational change, the leader who proposes an initiative is important, but the first follower is more important. The first person to publicly support your proposal transforms you from a lone voice into the beginning of a movement.

Tactically: before proposing an initiative in a large forum, secure one credible first follower. When you present, they immediately voice support. This dramatically changes the group dynamics.

---

Navigating Organizational Politics Ethically

What Is Organizational Politics, Actually?

Strip away the negative connotation. Organizational politics is the process by which groups of people with different interests and perspectives make collective decisions. This is not inherently bad — it is inherently human.

Politics become toxic when:

• Information is deliberately withheld to gain advantage
• Decisions are made to benefit individuals at the expense of the organization
• People are punished for disagreeing with those in power
• Credit is stolen and blame is shifted

Ethical Political Behavior

Ethical	Unethical
Building relationships to understand perspectives	Building relationships to manipulate
Sharing information strategically (timing, framing)	Withholding information to disadvantage others
Advocating for your team’s interests openly	Undermining other teams behind their backs
Seeking win-win solutions	Pursuing zero-sum wins
Giving credit to others publicly	Taking credit for others’ work
Framing proposals to emphasize shared benefit	Misrepresenting data to support a predetermined conclusion
Choosing which battles to fight	Avoiding all conflict to stay popular

Reading the Political Landscape

Watch for:

• Decision patterns: Who actually makes decisions? Not the org chart — the actual influence flow. In some orgs, the VP decides. In others, the Staff Engineer’s opinion is the de facto decision.
• Information flow: Who talks to whom? Who gets invited to which meetings? The meeting invite list reveals the real power structure.
• Resource allocation: Follow the money and the headcount. Stated priorities and funded priorities often diverge.
• Narrative control: Who frames the problem? The person who frames the problem usually controls the solution space.

When to Play and When to Walk Away

Not every political battle is worth fighting. A simple filter:

1. Does it materially affect my team, my mission, or my integrity? If yes, engage. If no, save your political capital.
2. Can I win? If the outcome is predetermined regardless of your effort, do not spend capital. Lose gracefully and focus on the next battle.
3. Is the cost of winning worth it? Sometimes you can win a battle but damage relationships you need for the next three years. Calculate the long-term cost.
4. Is there a creative alternative? Before fighting, look for reframes. Can you change the question so both sides get what they need?

---

Managing Up — Influencing Your Leadership

Managing up is not “making your boss happy.” It is ensuring your leadership has the context they need to make good decisions that affect your team, and that your team’s work is visible and valued.

What Your Leadership Actually Needs from You

What They Need	What Most EMs Provide Instead
Early warning of risks (with proposed mitigations)	Surprises (“the project is delayed”)
Clear, concise status (what is working, what is not)	Detailed technical updates that bury the signal
Recommendations, not just problems	“Here are three options, what should we do?”
Honesty about tradeoffs	Only presenting the option they want approved
Signal on organizational health (morale, retention risk, team dynamics)	“Everything is fine” until someone quits

The Status Update as Influence Tool

A well-structured weekly update to your skip-level or VP is an underrated influence tool. It shapes their understanding of your team’s work, signals your strategic thinking, and builds trust.

Structure that works:

## [Team Name] — Week of YYYY-MM-DD

### Highlights (what went well)
- [Result], which advances [strategic goal]

### Risks / Blockers
- [Risk] — Impact: [what happens if unresolved] — Ask: [what you need]

### Key Decisions Made
- Decided [X] because [reasoning]. Alternative was [Y].

### Next Week Focus
- [Priority 1] — why it matters

This format does several things: it connects your team’s work to strategy (demonstrating strategic thinking), surfaces risks early (building trust), shows your decision-making reasoning (demonstrating judgment), and signals priorities (ensuring alignment).

---

Anti-Patterns

Anti-Pattern	Description	Consequence
The Naive Meritocrat	“I do not do politics. The best idea wins.”	Good ideas die from lack of organizational support. The leader becomes frustrated and cynical.
The Machiavellian	Treats every interaction as a political calculation	People sense inauthenticity. Trust erodes. Short-term wins, long-term isolation.
The Credit Hoarder	Takes credit for team success, blames team for failure	Team disengages. Information flow stops (why share ideas that get stolen?).
The Passive Informant	Shares information to influence without taking responsibility for outcomes	Gets caught eventually. Reputation destroyed.
The Lone Wolf	Refuses to build coalitions because “I should not have to convince people”	Initiatives die. “Nobody supports my ideas” becomes a self-fulfilling prophecy.
The Over-Politician	Spends so much time on influence that execution suffers	Perceived as all talk, no delivery. Loses credibility.
The Yes-Sayer	Agrees with everyone to avoid conflict	Loses respect. No one knows where they actually stand. Commitments conflict.

---

References

• French, J. & Raven, B. (1959). “The Bases of Social Power.” In Studies in Social Power. — The six bases of power taxonomy.
• Cohen, A.R. & Bradford, D.L. (2005). Influence Without Authority. 2nd ed. Wiley. — The exchange model of influence; currencies of exchange.
• Cialdini, R. (2006). Influence: The Psychology of Persuasion. Revised ed. Harper Business. — Six principles of influence (reciprocity, commitment, social proof, authority, liking, scarcity).
• Pfeffer, J. (2010). Power: Why Some People Have It and Others Don’t. HarperBusiness. — Unflinching look at how power actually works in organizations.
• Kotter, J.P. (1985). Power and Influence: Beyond Formal Authority. Free Press. — Managing lateral relationships and upward influence.
• Fournier, C. (2017). The Manager’s Path. O’Reilly. — Practical sections on managing up and navigating organizational dynamics.
• Larson, W. (2019). An Elegant Puzzle. Stripe Press. — Engineering leadership in organizational context; working with the executive team.
• Patrick Lencioni (2002). The Five Dysfunctions of a Team. Jossey-Bass. — Trust, conflict, commitment, accountability, results framework.
• Grove, A.S. (1983). High Output Management. Random House. — Dual reporting, matrix management, and influence in tech organizations.
• Kim Scott (2017). Radical Candor. St. Martin’s Press. — The “ruinous empathy” quadrant as a political anti-pattern.