Managing Up
Politics at work is information, not a character flaw
Refusing to pay attention to how influence moves is usually described as integrity, and it mostly functions as a decision to work with less information than everyone around you.
By Devika Menon3 min read

The word does two jobs and they get confused
When people say they hate office politics, they usually mean something specific and genuinely bad — credit taken dishonestly, decisions made on favouritism, information withheld to preserve an advantage. That behaviour exists and no amount of reframing makes it acceptable.
But the same word covers something else entirely: the ordinary business of understanding who cares about what, whose support a proposal needs, and why a reasonable idea keeps stalling. That is not manipulation. It is the social structure of a place where decisions are made by people rather than by a rulebook, and it exists in every organisation including the ones that describe themselves as flat.
Collapsing the two together has a cost that falls almost entirely on the person doing it. You end up declining to learn how things get decided, on the grounds that learning would be unseemly, while your colleagues carry that map and use it.
What the map actually contains
The useful version is unglamorous and largely factual. Which people get consulted before a decision is announced. Which department’s objection stops a project and which one is routinely overruled. Who has been here long enough that their agreement substitutes for a formal process. What the person approving budgets is themselves being measured on this year.
None of that is gossip, and it is not secret. Most of it can be observed from meetings and from who is copied on what. The reason it feels illicit is that nobody writes it down, so acquiring it seems like an act rather than a normal part of learning a workplace.
The single highest-value item on the list is what each senior person is judged on. Proposals succeed when they help somebody meet a target they already have, and fail when they are merely good ideas addressed to nobody in particular. That is not cynicism; it is what having a job means.
Using it without becoming the thing you disliked
There is a clean line and it holds up reasonably well. Using the map to route a good proposal to the person who can act on it, to anticipate an objection and answer it in advance, or to avoid ambushing someone who would have supported you if asked first — that is competence, and the outcomes are better for everyone including the people you did not consult.
Using it to obscure who did what, to build support for something you know to be weak, or to damage a colleague’s standing quietly — that is the other thing. The distinguishing test is not whether influence was involved but whether the account you gave would survive being repeated to everyone in it.
Most people find in practice that the second category is rarer than the reputation suggests, and that a great deal of what looked like scheming was somebody doing the basic work of talking to the relevant people before a meeting.
The pre-meeting is where most decisions happen
One concrete consequence is worth naming, because it surprises people early on. Substantial decisions are usually settled in short conversations beforehand, and the meeting confirms them. Arriving at a decision meeting with a strong argument nobody has heard before tends to produce a deferral rather than a conversion, because the people present cannot commit without checking with others.
The response is not to abandon the meeting but to do the conversations first. Ask the two people whose support matters what they think, listen properly, and adjust. If they will not support it, better to learn that in a five-minute exchange than in front of an audience where positions harden.
Where the advice runs out
Some organisations are badly run in exactly this dimension. Where decisions genuinely depend on personal loyalty, where information is hoarded as currency, and where the map is not learnable because it changes with whoever is favoured that month, the effort of reading it stops paying. Recognising that is a legitimate conclusion, and it is a reasonable reason to leave.
It is also worth being honest that people vary in appetite for this. Some find the social layer interesting; others find it draining and would rather be judged on output alone. Both are fine, and the second group can still do the minimum version — know who decides, know what they are measured on, talk to them before the meeting — without adopting a whole posture they dislike. That minimum is where nearly all of the practical benefit sits.
Common questions
Is there a version of this that does not involve socialising?
Largely, yes. Most of the map is built by paying attention in meetings, noticing who is consulted, and asking direct questions about how decisions are made. Social events help some people and are not the mechanism; plenty of well-informed colleagues never attend them.
How do I ask who really decides without sounding cynical?
Ask procedurally. “Who would need to agree to this before it can go ahead?” is a normal planning question and it usually produces an accurate answer. Asking who has power invites a defensive one.
What if I get the map wrong?
You will, repeatedly, particularly in the first year, and the errors are rarely costly if you hold your conclusions loosely. The expensive mistake is deciding early that one person is an obstacle or an ally and then interpreting everything through that, which is remarkably hard to unwind.
Staff writer, After the First Job
Devika writes the explanatory pieces on first months, managing up, money at work and reads the small print so you do not have to.





