Politics, boundaries, and difficult colleagues

"I don't do politics" is a popular sentence with an unpopular consequence: decisions about your work get made by the people who do. Politics, stripped of its sneer, is just how groups decide things when the org chart runs out of answers, and opting out means delegating those outcomes to whoever stayed in the room. This chapter is the honest engineer's version: influence without manipulation, boundaries that hold without drama, and scripts for the six colleagues who make work harder.

Don't be confused: political and manipulative are not synonyms, and the difference is auditability. Political behavior survives daylight: briefing stakeholders before a decision, building support for a proposal, timing an ask well; you could narrate all of it to the people involved without shame. Manipulation requires the dark: misrepresenting positions, engineering surprises, letting people believe things you know are false. The test for any move in this chapter: would you be comfortable if everyone saw exactly what you did and why? Every script below passes; that is the design constraint.

Pre-wiring: decisions are made before meetings

Chapter 4 taught socializing a design with engineers; the org-level version is pre-wiring: briefing every stakeholder 1:1 before the decision meeting, so the meeting confirms rather than discovers.

"Before Thursday's review, I want to walk you through the proposal and hear your objections while they're cheap to fix."
The generalized no-surprise rule (Chapter 11): nobody senior should hear consequential news, or face a consequential ask, for the first time in public. Surprise converts evaluators into opponents regardless of the merits.
The mirror skill is detecting when a "discussion" was pre-wired around you: if the room agrees suspiciously fast and questions feel ceremonial, the decision predates the meeting. Do not relitigate on the spot; ask afterward, plainly: "That felt decided coming in. What did I miss, and how do I get into that loop next time?" (A genuine question; the answer is usually a standing conversation you did not know existed.)

The optics of cc, to, and forwarding

Email and chat routing is a political instrument whether you intend it or not, so use it deliberately:

To = I need action from you; cc = no action, stay informed. Moving someone from cc to to is an ask; announce it: "Moving you to To:, Dana, because this now needs your call."
Adding a manager to a thread reads as escalation. Sometimes that is exactly what you mean; then say so honestly ("+Dana, since we're past what we can settle at our level"). Doing it silently is the passive-aggressive version, and everyone on the thread reads it as the threat it is.
BCC is a trap outside of mass-mail hygiene: if the hidden recipient replies-all, you own the explosion. Forward the sent mail afterward instead: same information, no landmine.
Reply-all discipline and thread hygiene are Chapter 1 material, but the political special case is the audience add mid-argument: widening a disagreement's audience escalates it exactly like volume does in a room. Shrink to resolve, widen to decide.

Boundaries that hold

Boundaries fail from vagueness more than from pushback. The strong forms are specific, warm, and repeated identically each time:

After hours: "I'll pick this up first thing tomorrow." Said once, then actually not picking it up, teaches faster than any speech about work-life balance. (Pair with notification hygiene; a boundary your phone ignores is a wish.) The sender-side courtesy is Chapter 1's "sending now, no response expected until your morning."
Capacity: the costed yes from Chapter 11, used on your own calendar: "I can take that on if the audit work moves; which do you want?" Never a bare "I'm too busy" (reads as unwilling), never a silent yes that becomes a missed deadline.
Role: "That's outside what I can commit for my team; Priya owns that call and I'll connect you." (Chapter 21's promise firewall, aimed inward.)
Meetings: "Declining to protect the migration work; notes welcome and ping me if the storage question comes up" (Chapter 9).
The overload flag, raised early like any other risk (Chapter 8): "Flagging that I'm at capacity and trending toward red. Nothing dropped yet; if we add anything, something visible has to move. Can we look at the list together?" Burnout announced as a status update gets resourced; burnout announced as a resignation letter does not.

The difficult-colleague field guide

Six recurring characters. Every script follows the same arc: address the behavior directly and privately first (Chapter 19's SBI), add structure second, escalate transparently third (Chapter 11).

The steamroller (interrupts, overrides, fills every silence). Live: hold the floor calmly ("let me finish the thought"), use the numbered-list device (Chapter 23). Private: SBI. Structural: written comment rounds before discussion, which flatten volume advantages entirely.
The ghost (never responds, blocks by absence). Default-forward asks with deadlines (Chapter 3), then one transparent escalation: "Third try and this now blocks the release, so I'm taking it to standup." The ghost's power is ambiguity; deadlines convert silence into a decision.
The nitpicker (twenty comments, none blocking, every review). Force the triage: "Which of these are blocking?" (Chapter 7); propose the convention fix (lint rules end style debates permanently); appreciate the genuine catches so the correction targets the noise, not the person.
The credit-taker: the Chapter 31 scene, plus prevention: work in public early (design docs and threads with your name and a date beat testimony later).
The cynic ("that will never work", every time). Convert mood into testable claims: "Which part fails first, and at what load?" (Chapter 12). Either you get a real failure mode (valuable) or the objection evaporates on contact with specificity. Assign the pessimist the risk section; it is usually a superpower pointed the wrong way.
The instant escalator (cc's your manager on the first disagreement). Do not match the move. One calm correction on the thread ("happy to settle this at our level; Dana, nothing needed yet"), then the direct conversation: "When the first message goes above me, I lose the ability to just fix the thing. Come to me first and I'll do the same for you."

The meta-rule across all six: complain upward about problems, not about people, and only after the direct attempt. "I need help unblocking reviews with team X; here's what I've tried" survives daylight (Chapter 11); "X is impossible to work with" is a grenade with your name on the pin. And pick battles like a portfolio: capital spent on the nitpicker's twentieth nit is capital missing from the argument that matters (Chapter 26).

Defending others in public

The political move with the best return on investment in this whole chapter: spending your capital on someone else.

The mischaracterization, corrected flat and fast: "Small correction before we move on: the delay wasn't Sam's review, it was the freeze; Sam turned it around in a day."
The absent colleague, represented: "Ines isn't here, so I'll voice her concern; she had a real case on the replay cost."
The junior interrupted: "Hang on, I want to hear the rest of Yuki's point." (Chapter 9's invitation, used as a shield.)

People remember who defended them approximately forever, the room updates on how you treat the absent and the junior, and the cost is ten seconds of mild social friction. There is no cheaper trust in this book.

👉 That completes the skills. What remains is watching everything run at once in the situation room: a feature from first pitch to launch, an incident minute by minute, and the five hardest conversations, each transcript annotated line by line. On to Chapter 29.