
Article
Your Leadership Thinks Your Team Is Doing Fine. That's the Problem.
Published June 5, 2026·8 min read
If your leadership doesn't know what your team is building toward, they'll fill that gap with assumptions. Most of those assumptions will be wrong.
The Story Leadership Is Already Telling About Your Team
Here's something most managers figure out too late: your leadership already has a story about your team. They formed it from the data points they've collected, meeting impressions, incident reports, headcount requests, the one time something went sideways six months ago. If you haven't been deliberately shaping that narrative, someone else has, or worse, leadership built it themselves from whatever fragments floated up to their level.
The absence of a clear story about your team is not neutral. Leadership fills that vacuum with whatever narrative is most convenient for the decisions they're already trying to make.
I watched this happen to a manager I worked with years ago. His team was genuinely good. Solid output, improving quarter over quarter, real investment in the craft. But he never talked about it upward. He assumed the results would speak for themselves. They didn't. When a reorg came, his team got cut first, not because they were underperforming, but because nobody in the room could articulate what they were building toward or why it mattered. The work was invisible because the story was invisible.
That's the problem. And it's fixable.
Vision Is Not a Poster on the Wall
Before we talk about communicating your team's vision upward, we need to agree on what vision actually is, because most managers confuse it with a mission statement or a set of goals.
Vision is directional. It answers the question: where are we going and why does it matter that we get there? Goals are the milestones. Mission is the purpose. Vision is the destination and the reason it's worth the trip.
If I asked you right now to describe your team's vision in two sentences, what would you say? Not the goals, not the roadmap, not the projects in flight. The destination. Where are you taking these people and why should anyone care?
If you can't answer that clearly, you don't have a vision problem with leadership. You have a vision problem. Fix that first. Everything else in this article assumes you have something real to communicate.
Why Upward Communication Breaks Down
Most managers are genuinely good at communicating downward. They run one-on-ones, they share context, they explain decisions, they keep their teams informed. They've put thought into it.
Upward communication is a different skill, and most people treat it as optional. They show up to their one-on-one with their manager, answer questions reactively, share status updates, and call it done. That's not communication, that's reporting. Reporting is about the past. Communication is about where you're going.
The breakdown usually happens for one of three reasons.
The first is that managers assume leadership already knows. They think because they're doing the work and producing output, the picture is clear. It almost never is. Senior leaders are managing enormous cognitive load. They are not tracking the nuance of what your team is building. You have to surface it explicitly, repeatedly, and in terms that connect to what they care about.
The second is that managers don't translate. They communicate in team-level language, projects, sprints, initiatives, and leadership receives it but can't connect it to the things they're responsible for: company strategy, resource allocation, risk, opportunity. The gap is a translation problem. Your job is to bridge it.
The third is that managers wait for the formal moment. They think the quarterly business review or the annual planning cycle is the right venue for the big picture conversation. By then, decisions are already half-made. You need to be working the narrative continuously, not episodically.
The Three Things Leadership Needs to Know
When you're communicating your team's vision upward, there are three questions you need to answer. Not once, but repeatedly, in different contexts, until the story is sticky.
Where is the team going? This is the vision itself, stated plainly. Not jargon, not a strategic framework, just a clear description of the destination. "By end of year, we will be the team that can turn a customer data request around in under 48 hours at scale. Right now we're at six days. Here's the path." That's a story. That's memorable. That's something a senior leader can repeat in a budget conversation without having to reference notes.
Why does it matter for the business? Your team's vision has to connect to something leadership is responsible for. Revenue, cost, retention, risk, competitive position. If you can't draw that line, your vision is operating in a vacuum. You don't need to oversell it. You need to make the connection explicit, because leadership won't always do that work for you.
What are you asking for or what should they watch for? This is the part most managers skip. Every upward communication should end with something actionable, either a request (I need a decision on X, I need air cover for Y) or a signal (watch for Z over the next 90 days, it will tell us if we're on track). Give leadership a role to play in your team's success. It creates alignment and it creates investment.
How to Actually Do This
The format matters less than the consistency. Some managers prefer a written update. Some do it verbally in one-on-ones. Some do both. What matters is that you're creating regular moments where leadership hears the narrative, not just the status.
A few things that work in practice.
Start your one-on-one with the one-sentence vision check. Before you get into the week's updates, say something like: "We're still on track for X. The thing that could knock us off is Y, and here's how we're managing it." Thirty seconds. Every week. Over six months, that becomes a very clear picture.
Find the natural connection points. When your leadership is talking about a company priority, find the place where your team's direction intersects with it and name that intersection explicitly. "That's actually exactly what we're building toward, here's why." You're not hijacking the conversation, you're doing the translation work.
Write a short team narrative document. Not a formal strategy deck, just a one-pager that describes where the team is going, why it matters, and what the key indicators of progress are. Share it once, reference it over time. When a new stakeholder gets involved in something that touches your team, send it. It does the work of establishing context without requiring you to repeat yourself from scratch every time.
When things go sideways, which they will, frame the setback inside the larger direction. "We hit a problem this week. Here's what it is, here's what we're doing about it, and here's why I still think we're on track for what we said we were building." That kind of communication builds trust faster than any amount of good news because it shows leadership you have a frame, not just a fire.
The Compounding Effect
This is the thing that surprised me when I started being more deliberate about upward communication. The return isn't just that leadership knows more. The return is that your team gets more.
When your leadership has a clear picture of where your team is going and why it matters, they advocate for you in rooms you're not in. They protect your headcount when cuts are being discussed. They connect you with opportunities that fit your direction. They give you more autonomy because they trust the direction.
Your team feels that. They feel the difference between a manager who is fighting for them and a manager who is just running the work. And the ones who feel it are the ones who stay.
Point being: communicating your team's vision upward is not a performance for leadership. It is one of the primary ways you do right by your team. They deserve a manager who can tell their story clearly. Make sure you can.
© 2026 David Liloia. Published under ManagerForge.
Become a better manager, starting today.
ManagerForge helps you track 1:1s, spot patterns, and grow as a leader.
Start your free accountNewsletter
Get new articles in your inbox.
Subscribe to the ManagerForge newsletter. No spam, just practical management content.
Related articles
Article
How to Plan a Project from Scratch
Most projects fail before anyone writes a single line of code or sends the first email. Here's how to build a plan that actually holds up under pressure.
8 min read
Article
How to Match Your Experience to a Company's Values (And Why Most People Do It Wrong)
Most candidates treat a company's stated values like a checklist. The ones who actually get hired treat them like a diagnostic tool.
8 min read
Article
How to Make a Decision When You Don't Have Enough Information
Waiting for perfect information is its own decision, and usually the wrong one. Here's how to move forward when the picture isn't complete.
8 min read
Article
How to Listen So People Actually Feel Heard
Most managers think they're good listeners. Most of them are wrong. Here's the difference between hearing someone and making them feel heard, and why it matters more than you think.
8 min read
Article
You Don't Know the Answer. Say So.
Most presenters treat "I don't know" like a confession of incompetence. It's actually one of the most credible things you can say out loud.
7 min read
Article
How to Find the Root Cause Before You Fix the Symptom
Most managers fix the wrong thing because they stop asking questions too early. Here's how to actually get to the bottom of a problem before you spend time and money solving something that doesn't matter.
8 min read