How to Communicate With Senior Leadership as a Manager
Managers and senior leaders often see different parts of the same organization. Learn how to communicate results instead of tasks, report up more effectively, and translate what leadership needs to know without losing sight of what your team can see.
The view changes depending on where you sit. Learning to lead means learning what information needs to travel up, down, and across the organization.
When I was a manager, I was sure senior leadership had no idea what it was like to run the operation. Then I became the COO, and I found out the managers had been right about some of it. Leadership couldn't see everything they could see.
The managers couldn't see everything leadership could see, either. As COO I was weighing financial exposure, risk to the company, commitments made in other parts of the business, competing priorities, and consequences that might not reach an operation for months.
Sometimes the decision that best protected the company made a manager's job harder. From the operation, that could look ridiculous. From my desk, it could be the least-bad option on the table.
Both views were right about something, and both were missing something.
Part of becoming a manager is learning to see past your own work
This is one of the harder parts of moving into management, because most people get promoted for being good at the work in front of them. You know the customer, the operation, and what your team can handle. You can see exactly why the new policy won't work the way someone at corporate thinks it will.
That knowledge still matters. As you move up, a second kind starts to matter too:
What is leadership trying to protect?
What's happening somewhere you can't see?
What tradeoff is being made?
What happens if this decision doesn't get made?
What does the person above you need to know that you only know because you're closer to the work?
You can ask all of these and still disagree with the decision. Good senior leaders should be asking the same things about you.
You are often standing between two incomplete views
This gets harder when leadership makes a decision you don't agree with. Your team sees the operational consequences right away, and you probably do too. But now you're their manager, and you have to say something.
The two easy lines are:
"I think this is a great decision."
"I know. I think it's stupid too, but corporate says we have to do it."
The first one asks you to pretend. The second tells your team the people above you don't know what they're doing.
A third line takes more work:
"Here's what I understand about why this decision was made. Here's what it means for us. Here's what we can control. And here's what I'm going to keep communicating upward as we see how it works."
With that line, you're translating between two groups of people who can't fully see each other's terrain.
I didn't know how to do this either
At one point in my career, leadership asked me for a weekly report on my work. I hated it. It felt like micromanagement. I already had plenty to do, and now I was supposed to spend time every week writing down everything I did so someone above me could check on it.
So that's what I gave them: tasks. What I worked on, which meetings I had, which projects were moving. It felt like a complete waste of time, and leadership never read the reports.
I understand now that I didn't know how to tell them what they needed to know. Nobody had taught me. They also didn't know how to develop me.
What senior leaders need from your report
They need to understand what's happening because of the work. Compare these two updates:
Met with Operations and IT about the inventory problem. Continued working on the new process. Training scheduled for next week.
Inventory discrepancies are down since Operations and IT changed the handoff last week. Two failure points remain. We're testing the larger one this week, and I expect to know by Friday whether we can eliminate it without additional labor.
The second one tells me what changed, what still matters, what you're doing about it, and what I should be watching. Someone farther from the work needs exactly that.
Information has to move both ways
As your responsibility grows, part of the job is moving information around the organization.
Look up: what can leadership see that I can't?
Look down: what can my team see that leadership can't?
Look across: who else is affected by what we're doing?
Then translate. Give leadership enough to understand what's happening without making them live inside your task list. Give your team enough context to understand a decision without pretending you know everything that went into it.
When the two views don't match, find out what each side can see before deciding one of them is wrong. Sometimes the thing that looks unreasonable from where you're standing makes more sense once you can see the rest of the map. And sometimes, once leadership can see what you're seeing, the decision needs to change.
One question for your next update
The next time you update your boss, start here: what does my boss understand now because I told them?
That question would have saved me a lot of useless weekly reports.
Need a better way to report up?
The Weekly Status Report is built around four things leadership needs from you: what changed, what matters now, what needs attention, and what's coming next.
Field Notes
Read your own terrain, every Sunday
One leadership signal a week, read through the map, so you know where you're standing and what to do next.
Get the weekly Field NoteOne email a week. Unsubscribe anytime.
They’ve already solved the problem
They’ve made the calls, checked the alternatives, and come to you with a specific request. Before you start solving the problem, listen for the part they actually need you to decide.
Someone asks if they can leave an hour early for the next two weeks. Their childcare arrangement has fallen through.
You look at the schedule. It might take a little rearranging, but you think you can make it work.
"What happened?"
They explain. Someone who usually helps isn't available anymore.
"Could someone else pick them up?"
They've tried that.
"What about the after-school program?"
There's a waiting list.
You're working through the problem together. At least, that's how it feels to you. People bring you problems all day, and helping them find a way forward is part of what you do.
But this person came with a specific request. They've already made the calls, checked the alternatives, and worked out an arrangement that would get them through the next two weeks.
They need your answer about the hour.
Now they're walking you through everything they tried before they came to you.
Somewhere in the conversation, the task changed. You're trying to solve their childcare problem. They're trying to find out whether they can leave at three.
Listen for what they're asking
"I don't know how I'm going to manage pickup. Can you help me think through it?" opens a conversation about possibilities.
"Can I leave an hour early for the next two weeks?" asks you to consider a particular arrangement.
Both involve a problem. Your part in each is different.
In the first conversation, exploring options together may be exactly what the person needs. In the second, they may have done considerable work before approaching you. The question that reaches your desk is the part they cannot decide for themselves.
When you start suggesting alternatives, you can accidentally send them back through work they've already done. Each suggestion requires an explanation. Each explanation brings more of their private life into the conversation.
You may pick up useful context. For them, it can feel like having to prove the request is reasonable in the first place.
Your questions carry the decision
A manager's question has weight because the manager controls what happens next.
"Could your partner do it?" might feel like an ordinary suggestion. To the person waiting for your approval, it can sound like a condition: before I agree, show me why your partner can't.
Now they have to decide how much to say about their relationship, someone else's job, or an arrangement they would rather keep private. They may answer because they trust you. They may answer because they need a yes.
You cannot always tell which.
This is slippery precisely because you're trying to help. You're paying attention, making time, and drawing on experience. Those are things you want to bring to management. But they can carry you beyond the help someone actually requested.
You can leave the conversation feeling that someone opened up to you. They can leave relieved about the schedule and wishing they hadn't needed to explain so much.
Work on the part you're responsible for
A specific request still needs consideration. There may be coverage to arrange, work to hand over, or a limit on what you can approve.
Those questions belong in the conversation.
Which days do they need? What happens during that last hour? Can the team cover it? When will you check whether the arrangement is still needed?
You can be thorough about those things without taking responsibility for reorganizing someone's family.
If the request cannot work as proposed, explain the actual constraint. That gives you something concrete to work through together. If you need more information, be clear about what you need and why.
And when you're unsure which conversation someone wants, you can ask: "Are you looking for help thinking through options, or do you need me to consider this arrangement?"
That small check can save both of you a much longer conversation.
Give the answer first
Sometimes you know early that you can approve the request. Then concern takes over, and you keep asking questions before saying so.
The person across from you is still waiting.
"Yes, we can make that work. Let's sort out the coverage."
Once they have the answer, they can choose whether to tell you more. You can still care about what they're going through, and they can still welcome it.
But they no longer have to wonder whether the next detail is the one that will get their request approved.
One thing to carry
The next time someone brings you a problem, listen for the work they've already done.
They may need your ideas. They may need you to make a decision. They may have reached the one part of the solution that requires your authority.
Before you ask another question, consider:
What have they actually asked me to help with?
Field Notes
Read your own terrain, every Sunday
One leadership signal a week, read through the map, so you know where you're standing and what to do next.
Get the weekly Field NoteOne email a week. Unsubscribe anytime.

