Topic
Managing Up: How to Communicate So the People Above You Can Act
Managing up is the practice of communicating so the people above you can steer the work without chasing you. Done well, it reduces their uncertainty — stating the situation, the consequence, what is in hand, what is not, and what you recommend — instead of merely reporting activity. The book calls this skill executive usefulness.
1 guide in this topic
Managing up has a bad reputation it does not deserve. It is not flattery, politics, or managing your boss's mood. It is the plain skill of giving the people above you a picture they can act on — quickly, accurately, and without having to drag it out of you one question at a time.
The book calls this executive usefulness, and it draws a sharp line. Weak communication tells the reader what is happening. Useful communication changes, for the reader, what is still uncertain. Two updates can carry the same facts, the same word count and the same sincere effort, and have completely different effects on the room: one leaves the reader with more questions than they arrived with, the other with fewer.
Why this is a control skill, not a presentation skill
A manager with six areas of work cannot hold the detail of all six. What they can hold is the shape of each — which is under control, which is drifting, which has a live decision in it this week. They build that picture from updates that have already done the thinking, never from raw activity. When your updates are useful, your manager can step back without losing the thread, and trust can be handed to you at range. When they are weak, the manager hedges, asks to see more, copies themselves into threads, and quietly becomes the bottleneck the team waits on. They have not changed their mind about you; the updates have not yet earned the delegation.
"A recommendation you are half-sure about is more useful than a description you are fully sure about." — The Control Standard
That is the whole move. A manager can disagree with a recommendation and steer it. They can do nothing with a narration except ask for more.
What good looks like
The reliable structure is a six-question shape: what is happening, so what, what is in hand, what is not, what you recommend, and what you need. Front-load the answer, name the consequence, and end with a clear ask. That answer-first habit is the pyramid principle applied to an update — lead with the conclusion, then support it — and it is also how you keep stakeholder engagement deliberate rather than reactive. The guide to writing a useful status update works through that shape with worked examples you can copy on Monday morning.
Around the writing sit a handful of supporting ideas worth knowing by name: decision rights, so you escalate the right calls and make the rest yourself; stakeholder management, because work moves at the speed of alignment, not the plan; and the limits of a RAG status, which summarises a feeling but is not, on its own, evidence that work is under control.
Where to start
Begin with the status update guide — it is the most portable habit here and pays back the same week. If you would rather see where your own work is currently routing through you and going unseen, the free Drift Report scores it in about five minutes.
Related
How to Write a Status Update That's Actually Useful
A useful status update reduces uncertainty instead of describing activity. Answer six questions in order: what is happening, so what, what is in hand, what is not, what you recommend, and what you need. Lead with the bottom line, name the consequence, and bring a recommendation — not a chronological account of your week.
TermDecision Rights
Decision rights define who gets to make which decisions, and at what level, without needing sign-off from above. Setting them clearly is how a team stops routing every choice through one person: cheap, reversible decisions are pushed down with guardrails, while the rare, hard-to-reverse ones are deliberately kept for a more senior call.
TermStakeholder Management
Stakeholder management is the deliberate work of identifying everyone with a stake in a piece of work, understanding what each needs, and keeping them aligned as it proceeds. It matters because projects move at the speed of stakeholder alignment, not the speed of the plan — and "they were in the meeting" is not the same as "they are aligned".
TermRAG Status
A RAG status reports the health of a project or task with a traffic-light colour: Red, Amber or Green. It is a fast way to communicate at a glance, but on its own it is a summary of someone's judgement, not evidence of control — a green light only means as much as the owner, dated next step and fallback sitting behind it.
TermStakeholder Engagement
Stakeholder engagement is the ongoing practice of identifying the people affected by a project, understanding their interests and influence, and actively working with them throughout its life. It is a continuous two-way relationship — not a one-off mapping exercise — aimed at keeping support high and surprises low.
TermPyramid Principle
The Pyramid Principle is a structuring method for written and spoken communication, devised by Barbara Minto at McKinsey, that puts the answer or recommendation first, then groups the supporting arguments beneath it. You lead with the conclusion, then justify it — so a busy reader gets the point before the detail.