Home → Leadership
Managing Up: Setting Expectations, Not Filing Reports
"We'll probably make it." The day you say that sentence, you have also booked the bad meeting you will have three weeks later. Managing up is not flattery; it is telling the truth while the other side still has options.
- Bad news loses value over time. Early it is a decision; late it is a surprise.
- Shielding is not hiding. The test: who am I keeping this from, and for whom?
- A short weekly written update beats a long monthly meeting.
- Bring options with the problem. But if the call is above your level, ask for the call too.
From the field: news delivered three days out
In one integration the other side's API turned out different from what we expected. By week two we knew the date was at risk. But we said "maybe we can pull it back" and tried for two more weeks. I delivered the news three days before the deadline.
The meeting went badly, and rightly so. By then there were no options left: the customer had been told, the marketing calendar was set, nobody could be added, scope could not be cut. My attempt to keep the news good had taken away someone else's right to decide.
Said in week two, the same problem had three answers: split the scope, write a temporary shim for the other side's API, or move the date by a week. All three were possible. Delaying the news delayed the solutions.
Shielding versus hiding
Part of a manager's job really is shielding the team: noise, urgency theatre and panic from above should not be forwarded downward as-is. True. But the same reflex slides easily in the other direction: hiding reality from above.
- Not turning "there is panic upstairs" into a late night for the team
- Filtering urgency and passing on the real priority
- Not personalising a failure outside the team
- Not raising a risk because "it is not certain yet"
- Presenting the situation as better than it is
- Trying to fix it alone without telling anyone — twice as costly if you fail
One question separates them: who am I keeping this from, and for whom? If the answer is "so the team is not demoralised", it may be shielding. If it is "so I do not look bad", it is hiding.
The three things your manager actually needs
The worst day for a senior manager is hearing something about your area from someone else first. The rule: they should never learn anything about you from another person.
Not detail — the decision point. "The queue is backing up" is a technical sentence; "unless we act this week, order confirmations start lagging on Friday, and there are two options" is a decision sentence.
Trust does not go to the person with good news; it goes to the person whose words come true. Saying "two weeks" and taking three is worse than saying "three weeks" and taking three.
The weekly written update: five lines
Instead of long monthly status meetings, a short weekly note works far better. It never exceeds five lines, in this shape:
- Shipped: what went live or closed this week.
- Next: what is coming next week.
- Risk: which possibility threatens the date, and how likely it is.
- Waiting on you: what you need from them, and by when.
- Quiet win: valuable work nobody sees (infrastructure, tech debt paid down).
The last item looks minor but does a lot of work: if invisible work is never described, "what do these people actually do?" eventually gets asked. Writing it down has a second benefit too: six months later you have a record that says "you flagged that risk" — not to defend yourself, but to remember how decisions were made.
Bringing a problem
"Don't bring me problems, bring me solutions" is half right. Arriving with no options is wrong — but so is deciding everything alone, because some calls genuinely sit above your level.
A good version sounds like this: "Here is the risk. I see three options: (a) split the scope, gaining two weeks; (b) move the date by a week; (c) write a shim, which returns as tech debt in two months. I recommend (a). Is this your call or mine?"
That last sentence is the most useful part. Clarifying where the decision sits removes the entire "why didn't you ask me?" conversation later.
Padding estimates to stay safe. It works once or twice, and then the other side learns your multiplier and mentally shortens everything you say. From that point on, communicating a real risk becomes impossible — the upward-facing side of commitment versus estimate.
Checklist
- Is there anything my manager does not know but should hear from me?
- Which of this week's risks threatens a date? Did I say so?
- Am I holding anything back? For whose benefit?
- Did my last date hold? If not, did I share why?
- Did I ask for the pending decision clearly, with a deadline?
- Did I describe one piece of the team's invisible work this month?
- Am I raising a delay for the first time in the final three days?
Conclusion
Managing up is not about pleasing the person above you; it is about making the relationship predictable. A predictable manager gains trust even when delivering bad news, because the other side can plan around what they say.
The simplest measure: how many times in the last six months has leadership been surprised by something in your area? If the answer is zero, you are doing this well — and that absence of surprises is exactly what buys your team room to work.