When a senior stakeholder asks what your team is building, answer with the destination, not the route. Name the future state your work creates before you name any tool, project, or timeline. Leading with tasks files you as an executor in their mind. Leading with the outcome marks you as someone who sets direction.
Key takeaways
- Stakeholders who ask “what are you building?” want the future state, not your project list. A list of tasks answers a question they didn’t ask.
- Defaulting to tactics is usually an identity gap, not a communication gap. You still see yourself as the person doing the work rather than the person setting the direction.
- Vague vision language gets forgotten. “Continued alignment of stakeholders” disappears. “Everyone operating from the same playbook” gets repeated.
- Vision communication carries more weight during uncertainty, not less. Restructuring, AI adoption, and budget shifts raise the stakes on naming a fixed point.
- The word “continue” undersells real change. Swap it for “building,” “creating,” or “setting up” when the work is genuinely new.
What do stakeholders mean when they ask “what are you building?”
They’re not asking for your to-do list. They want to know where you’re taking the team, what you stand for, and whether you can see past this quarter.
Most managers hear the question and reach for the work itself: the platform migration, the dashboard project, the process rollout. It feels like the honest answer because it’s what’s actually filling the calendar. But answering with tasks in that moment quietly files you as an executor, and that impression is hard to reverse once it’s set. The person across the table walks away knowing what you’re doing without knowing where you’re going.
What’s the difference between describing the route and the destination?
Every time you talk about your team’s work, you’re describing one of two things. The destination is the future state, what success looks like once you get there. The route is the projects, tools, timelines, and logistics that get you there. Stakeholders want the destination. Your team needs both. The problem is that most managers default to the route and never clearly name where they’re headed.
Here’s the same work in both versions.
Route version: “We’re updating our onboarding process, moving content into an AI workflow, and upgrading our tech stack so new engineers have access to the right platforms.”
Destination version: “We’re building toward a place where every person in our department, from their first week to their tenth year, is operating with the same playbook, the same current tools, and the same AI training. Development stops being a one-time event and becomes part of how we work.”
Same team, same work, and a completely different read on who’s running it. If your answer to “what are you building?” contains a tool name, a platform, or a project title before it contains an outcome, rewrite the update before your next stakeholder conversation.
Why do strong managers default to listing tasks?
Because they still think of themselves as the doer. When I see managers default to tactics in those conversations, it’s almost never a communication issue. It’s an identity issue. They see themselves as the person who does the work, not the person who sets the direction, and their language gives that away before they’ve finished the sentence.
This is why polishing the wording rarely fixes it on its own. A manager who privately identifies as an executor will keep gravitating to the route no matter how the question is phrased. The shift starts with deciding that naming the destination is part of your job, not a presentation skill you pull out for offsites.
Why does vague vision language hurt your credibility?
Because vague language gives people nothing to picture, and what people can’t picture, they can’t act on. Research on how leaders communicate vision found that vivid, image-based language paired with a small number of clear values produces measurable improvements in team performance. The same body of work named the trap most leaders fall into: the blurry vision bias, where leaders describe the future in abstract terms while describing their current projects with precision.
The result is a team that has total clarity on the tasks and no shared picture of where it’s headed, which means they can’t make good independent decisions. Wharton’s Andrew Carton and his collaborators showed across multiple studies that leaders who use image-based rhetoric communicate more inspiring and more usable visions than those who reach for conceptual language.
The fix isn’t to sound more inspiring. It’s to be more specific. “Everyone operating from the same playbook” is something a person can see. “Continued alignment of stakeholders” is not. If your vision statement could apply to any team at any company, it isn’t specific enough yet. Rewrite it until it describes a future state that only your team could produce.
Does vision communication matter more during uncertainty?
Yes, and the gap between leaders who do it and leaders who don’t widens exactly when things feel unstable. A 2024 study in the Journal of Business Research found that during periods of high perceived work uncertainty, a leader’s vision communication has a stronger effect on how employees respond to change, not a weaker one.
When an organization is restructuring, shifting budgets, adopting AI, or changing leadership, people need a fixed point to navigate toward. If you don’t give them one, they fill the vacuum with anxiety, assumptions, or quiet disengagement. That makes vision articulation a daily tool rather than an annual-planning ritual. If your organization is going through any kind of transition right now, treat naming the destination as a required communication skill, not an optional leadership asset.
Why is the word “continue” working against you?
Because “continue” signals maintenance. It tells people you’re keeping the lights on rather than constructing something new. When you’re building something from scratch or fundamentally changing how something works, “continue” shrinks both the perceived scope of the work and your role in it.
Words like “building,” “creating,” and “setting up” signal the opposite: that you see yourself as the person constructing something that wasn’t there before. Audit your last three stakeholder updates and replace every “continue” that’s actually describing a change or a new capability with an active construction verb. The work didn’t get smaller. The way you talked about it did.
How do you write a destination statement in three steps?
Use a simple structure you can deliver out loud in 60 seconds.
Step one: write one sentence on the future state. Describe the world your team is creating clearly enough that the listener can picture it without you explaining further.
Step two: name two supporting pillars. These are the two things that have to be true for that future to exist. They give the destination structure without turning it into a project list.
Step three: produce a 60-second spoken version that contains no tool, project, or platform names. If you can’t get through it without naming software, the route is still doing the work the destination should be doing.
Then test it against one question: if my CEO asked me right now what I’m building, could I answer in 60 seconds without mentioning a single tool, project, or platform? If the answer is no, that’s the gap to close first.
Do this this week
Write your destination statement using the three steps above. Open your next stakeholder meeting with one grounding sentence before any agenda item: “Before we get into the details, let me frame what we’re working toward.” Then deliver the destination statement, and only then move into the route.
Naming the destination clearly is the practical, daily work of making sure the people around you, above you, and reporting to you know where you’re taking them. The managers who can do it are the ones people choose to follow, and the ones who get asked to lead more.
Frequently asked questions
What if my team’s work right now really is mostly maintenance?
Then the destination is the standard you’re protecting or the reliability you’re guaranteeing for the rest of the business. Name the outcome the maintenance produces, not the upkeep itself.
How is a destination statement different from a company mission statement?
A mission is permanent and belongs to the whole company. A destination statement is yours, scoped to the next 12 to 18 months, and specific enough that only your team could produce it.
Should I lead with the destination in writing too, not just in meetings?
Yes. The same rule applies to Slack updates, status emails, and docs. Open with the outcome, then drop into the details underneath it.
What if I can’t actually name the destination?
That’s the more important problem. If you can’t say where you’re taking the team in one sentence, your team can’t see it either, and that’s worth solving before your next stakeholder conversation.
Doesn’t leading with the outcome make it sound like I’m dodging the details?
Not if the specifics come right after. The order is destination first, route second. You’re framing the work, not hiding it.
