Politics Isn't a Dirty Word

Most design leaders I know would rather talk about anything than office politics. They’ll talk about taste. They’ll talk about feedback culture. They’ll cheerfully talk about layoffs. But raise the word “politics” in a one-on-one and you can watch their shoulders pull toward their ears.

I have a theory about why. Most of us trained in a discipline that taught us the work could speak for itself. That if the artifact was right — the prototype, the deck, the doc — the room would come around. And for a window of time, in a smaller industry, that was even half-true.

It is not true now. The work cannot speak for itself, because the room is not listening to artifacts. The room is listening to the people in the room. If you are not one of those people — trusted, calibrated, fluent in what each stakeholder needs to hear — your prototype is irrelevant.

The work cannot speak for itself, because the room is not listening to artifacts. The room is listening to the people in the room.

1. Politics is not the same as politicking

Let's separate two things that get conflated. Politicking — small-p, gerund — is the bad kind. The empty alliance-forming, the back-channel sniping, the meetings where you go to be seen rather than to decide. I have no patience for it and I don't recommend it.

Politics, the noun, is something else. Politics is just the name we give to how power, attention, and resources move inside a group of people who have to make decisions together. Every team has politics, because every team has finite resources and disagreement. The question is whether you understand the politics or whether the politics understand you.

The design leaders I have watched succeed are politically intelligent in the noun sense. They know which conversations matter, which rooms are real, what each peer is optimizing for, where the actual decisions get made versus where they get rubber-stamped. They are not always likeable. They are almost always effective.

2. The artifact-first trap

When a design leader tells me “I just want to focus on the work,” I hear two things. The first is true and admirable: they want to ship good design. The second, often unsaid, is a wish: they want shipping good design to be sufficient. They want the org to reward the work without them having to translate it.

It will not. Translation is the job. Inside any company past the size of about thirty people, half of design leadership is translation — not of the design, but of why this design, in this season, matters more than the next thing the CFO wants to fund. If you cannot do that translation, you are not a design leader. You are a senior IC with a title.

3. What organizational intelligence actually looks like

When I coach senior designers stepping into their first leadership roles, I tell them to spend the first four weeks doing one thing: build a map. Not a roadmap — a map of the org. Who reports to whom on paper. Who reports to whom in practice. Who is on the way up; who is being managed out. Which executives have working trust between them and which are politely pretending. What each function thinks design is for.

The map sits in a private doc that nobody else sees. You update it weekly. You date your observations — “as of mid-Feb, ENG VP and CFO are in disagreement about Q3 hiring; that is why product investment is frozen.” Six months in, you have a real artifact: a record of how this organization actually works, the kind of artifact most design leaders never bother to build.

This isn't scheming. It's the same kind of fieldwork we tell our researchers to do, applied to the system above us instead of the one below us. You wouldn't ship a product into a market you hadn't studied. Don't lead a team in an org you haven't studied either.

4. The right kind of conflict

Politics is uncomfortable in a specific way: it requires you to disagree publicly, with people you depend on, in front of other people you depend on. Most designers I know are conflict-averse on a personal level and conflict-soaked on a craft level. They will gladly tear apart a button shadow in a critique, then go silent in a strategy meeting where the wrong roadmap is being green-lit.

The right kind of conflict is structured, public, and brief. You name the disagreement (“I think the win-conditions for this quarter are wrong”). You frame the alternative (“here’s what I would prioritize and why”). You stop. You let the room argue back. You don’t do this in every meeting. You do it in the meeting where the decision is happening.

5. What the manual says

I have a private rule I picked up somewhere and never wrote down until now: if you can name the political dynamic in a room, you are not playing politics, you are doing your job. If you cannot name it, you are being played by it.

That rule has saved me a lot of grief. It is also the difference, I think, between the leaders I respect and the ones who burn out at the next layer of altitude. The respected ones can describe the system they are operating inside. The burned-out ones describe a series of betrayals.

Politics is just the system. Learn to see it, and the work — the actual design — has a fighting chance.

— S.B.