What a manager is actually paid to do

The model most people start with

From underneath, a manager looks like a person who assigns you work, judges it, and holds a degree of arbitrary power over your prospects. Under that model every interaction is a small audition, requests feel like tests, and anything that goes wrong feels like it will be attributed to you personally.

The model is not exactly wrong, but it leaves out almost everything that determines how your manager actually behaves. They have their own manager, their own targets, a headcount number they did not choose, and a set of obligations to people you never see. Understanding those constraints is the difference between working with a manager and working around one.

Allocation, cover, translation, record

Strip away the variation between industries and a first-line manager’s job comes down to four things. Allocating finite people to more work than they can do. Providing cover, meaning absorbing shocks from above and outside so the team can keep working. Translating in both directions, turning vague strategic language into concrete tasks and turning technical reality into something a senior audience will act on. And maintaining a record of who did what, which is what performance and pay decisions are eventually built from.

Notice how little of that is about knowing your job better than you. In many fields it is normal for a manager to be less current than the people reporting to them, and this is not a scandal. Their comparative advantage is context — they can see how six workstreams interact and which one the organisation actually cares about this quarter, which is information you structurally cannot have.

The fourth item, the record, is the one junior employees consistently underestimate. When pay or promotion is discussed, your manager is arguing from what they can remember and evidence, in a room where other managers are arguing for their own people. Work they cannot describe is work that does not count, however good it was.

They are optimising a portfolio, not your career

A manager is trying to get a set of outcomes delivered with the people available. That means their decisions about you are partly about you and partly about the shape of the whole team — who else is free, who needs development, what has to ship, who is at risk of leaving.

This explains a lot of otherwise baffling behaviour. Being given dull work is often not a judgement on your ability; it may be that you are the only person free, or that the interesting work is being used to retain someone who has one foot out of the door. Being left alone is sometimes trust and sometimes simply that you are not currently the fire. Reading every allocation as a verdict on your worth will make you miserable and will also usually be inaccurate.

What they are under pressure about

Managers are typically squeezed by three things: a budget that is set elsewhere and revised without much warning, a delivery commitment they may not have agreed to, and the risk of losing people, since replacing someone costs money, months and their own time. Almost every request you make lands somewhere against those three.

This is why the word "proactive" is useless and the underlying behaviour is not. To a manager under that pressure, a proactive person is specifically someone who reduces the number of things they have to hold in their head. That means flagging a slip while it is still cheap to fix, closing loops without being chased, bringing a recommendation rather than an open problem, and being someone who can be given an ambiguous task without it coming back untouched.

Working with rather than around

Going around a manager — routing decisions past them, taking problems to their boss, quietly doing things a different way — sometimes works in the short term and reliably costs more later. It undermines the one thing they need to function, which is a defensible account of what their team is doing, and it makes you a source of surprise. Managers hate surprise more than they hate bad news.

The productive move is to make yourself cheap to manage and then ask for things. Someone who never generates unexpected problems has real informal leverage when they want a course, a different project or a conversation about progression, because the cost of accommodating them is low and the cost of losing them is not.

And sometimes the model does not apply

All of this assumes a manager who is basically doing the job. Plenty are not. Some are overloaded to the point of absence, some were promoted for technical skill and given no training in any of the four functions above, and a few are actively harmful. In those cases the advice to understand their constraints is still true but much less useful, and the realistic question becomes how long you are willing to stay in a role where the record of your work is being kept badly or not at all.

It is worth judging that on evidence rather than on a bad month. A manager who forgets things but backs you in public is a different proposition from one who is pleasant in private and silent when it counts.