At Lightningcast, a small video advertising startup where I led the engineering team, the CEO departed, and a new one was brought in. The previous engineering leader had also left and I assumed I would step into the role. I had been acting as the manager, and I knew the team, the technology, and the product better than anyone remaining. In a startup of that size, it seemed like the logical next step.
But I never said any of this out loud.
The new CEO brought in a friend to be the VP of Engineering. This was a perfectly reasonable decision from his perspective; he was new, he needed people he trusted, and nobody had told him that someone on the existing team wanted the role and was already doing most of the work.
I didn’t tell him because I assumed it was obvious. I assumed the situation spoke for itself.
It didn’t.
When the new VP arrived, I prompted a meeting and asked where he saw the company and the team headed. He wasn’t certain, so I shared what I knew about the technical landscape, the team dynamics, and the priorities as I understood them. He listened with genuine interest.
Near the end of the conversation, he asked the standard question: “So where do you want to be in the next few years?”
I pointed at his chair.
I told him, directly and without softening it, that I had expected to be leading this team. It was one of my more direct moments, and I don’t necessarily recommend the delivery, but what it accomplished was immediate and important: from that moment forward, he knew I was ambitious. He knew I wasn’t content to simply execute, and that the quiet, steady person who had been holding the team together had aspirations that extended beyond what my demeanor communicated.
The irony is that I then spent the next several months trying to make him successful. I gave him everything I knew about the team and the right approach going forward. He listened and he tried, but his interests pulled him toward building rather than leading. Within weeks, he had dived into a technical problem, writing an entire Perl library to pull reporting data and present it to the CEO, while I continued managing the people on the team by default. He was a good person, probably a quiet leader himself, but he fell into the trap of doing far more building than leading.
He left in less than a year.
The lesson I carried from that experience was not about the outcome. It was about the silence that preceded it. I had ambition, capability, and a legitimate case for the role, but by the time I made them visible, the decision had already been made.
This pattern has repeated throughout my career in different forms, and I suspect it has repeated throughout yours.
Quiet leaders deliver. We stabilize teams. We solve problems without creating new ones. We are the people that managers never have to worry about, which, as I’ve written before, means we are also the people that managers never think about.
And because we don’t broadcast our ambitions, organizations fill in the blank with an assumption: “this person must be satisfied with where they are.”
It is a reasonable assumption. If someone never signals that they want a different role and never makes their aspirations known in the conversations where career decisions are shaped, the default conclusion is that they don’t have aspirations. Or that their aspirations are modest. Or that they’re content to keep doing what they’re doing.
There’s that phrase again. “Keep doing what you’re doing.” The organizational equivalent of “we’ve stopped wondering what you want.”
I want to name why this happens, because understanding the mechanism matters more than resenting the outcome.
Organizations track ambition through signals. Explicit signals, like saying:
“I want to be considered for that role.”
“I’d like to lead that initiative.”
“Where do I stand for the next promotion cycle?”
These are the signals that loud leaders send naturally. They advocate for themselves the same way they advocate for their ideas: directly, vocally, and early enough to influence the outcome.
Quiet leaders often don’t send these direct signals. They often believe they are sending signals, even though the organization is not receiving any.
They think they are sending signals when they take on additional responsibility without being asked. They believe they are signaling ambition, but the organization just sees reliability.
Or they think they are signaling readiness for leadership by mentoring others and building team capabilities, but the organization just sees a strong team player.
More than anything, the quiet leader thinks they are sending signals about their ambition when they deliver consistently quarter after quarter. They believe they are signaling readiness for more, but the organization sees someone who is well-suited to their current role.
In each case, the quiet leader’s behavior is genuinely admirable, but ultimately unhelpful to driving their career. Behavior does not communicate ambition; behavior communicates competence. Ambition requires words.
The gap between actions and explicitly stated intentions is one that quiet leaders often leave open because it feels like self-promotion. For people whose entire leadership identity is built on substance over performance, self-promotion feels like a betrayal of their values.
I’ve felt this resistance myself. At Amazon, I spent years building teams, shipping products, earning patents, and delivering results that I believed would speak for themselves. And they did speak. They said: “David is reliable, technically excellent, and runs a strong organization.”
They did not say: “David wants to lead a larger organization.” Or: “David has ideas about where this part of the business should go.” Or: “David should be in the conversation when we discuss who leads the next major initiative.”
And I didn’t say those things clearly enough.
The feedback I received more than once across my career was some version of “we need to see more leadership presence” or “you need to be more visible in cross-functional settings.” What those phrases actually meant, decoded from corporate language into plain English, was: “We don’t know what you want because you haven’t told us, and we’ve stopped trying to guess.”
This feedback was completely accurate.
At Warner Bros. Discovery, I watched this dynamic play out with leaders I coached. Talented, thoughtful people who were doing exceptional work and receiving average reviews. People whose managers genuinely liked them and genuinely had no idea they were frustrated, ambitious, or considering leaving.
The conversations I had with these leaders often followed a predictable pattern:
“Does your manager know you want that role/project/responsibility?”
“They should. I’ve been performing at that level for over a year.”
“But have you told them?”
Silence.
Over and over again, their performance was visible and their ambition was invisible. And in every case, the manager had just filled the gap with the most convenient assumption: this person is satisfied.
Not maliciously or carelessly, just humanly. Managers have limited attention, and they spend most of it on the people who are creating problems or making demands. The quiet leader who creates no problems and makes no demands becomes the person whose career gets the least deliberate investment. And then they suffer the consequence: stagnation.
There is a deeper cost to this pattern that goes beyond missed promotions and modest raises.
When an organization consistently fails to ask what you want, and you consistently fail to tell them, something shifts in how you see yourself. You start to wonder whether your ambitions are legitimate. You start to question whether wanting more is compatible with leading quietly. You internalize the assumption that was made about you and begin to believe it might be true: maybe you are satisfied. Maybe this is enough. Maybe the fact that you aren’t fighting for more means you don’t want it badly enough.
That internal narrative is corrosive. It takes a legitimate structural problem, the organization’s failure to see your ambition, and converts it into a personal doubt: “Maybe I’m not ambitious enough.”
You are. You just haven’t made it visible.
And I want to be direct about this: making your ambition visible is not self-promotion. The same way you would advocate for a team member whose contributions were being overlooked, you need to advocate for yourself. Not loudly or performatively, but clearly, specifically, and in settings where the information can actually influence decisions. This is good career stewardship.
The practice is not complicated. It is uncomfortable, which is different. Here is how you can break it down step by step.
Tell your manager what you want. Not in vague terms like “I’d like to grow”, but in specific ones (”I want to be considered for a director role within the next year. What would need to be true for that to happen?”). Ask for criteria, not affirmation.
Tell them early. Don’t wait for the performance review cycle. By the time formal reviews happen, the decisions about promotion slates and role assignments have already been influenced by months of informal conversations. If your name wasn’t in those conversations because nobody knew you were interested, the review is too late.
Tell more than one person. Your manager is the most obvious audience, but they are not the only one who needs to know about your goals. Peers, skip-level leaders, mentors, and the partners you trust all play a role in how the organization perceives your trajectory. When multiple people know what you want, the information travels through the informal channels where career decisions actually get shaped.
For the managers reading this: ask. Don’t assume that your steady, reliable, high-performing, quiet leader is satisfied. They may be the most ambitious person on your team and the least likely to tell you about their goals. The question “what do you want next?” costs you nothing and might be the most important question you ask all year.
I think about the Lightningcast moment often. Not because of the outcome, but because of how long I waited to say something that should have been said immediately.
When the previous leader left and I was already doing the job, one clear conversation with the incoming CEO could have changed everything.
“I’ve been leading this team. I want to continue leading it. Here’s what I’ve built and here’s where I think we should go.”
Three sentences. Thirty seconds. Instead, I waited, assumed, and watched the opportunity go to someone who was simply more visible to the decision-maker.
The new VP wasn’t more capable than me, and he wasn’t more ambitious. He was just more known to the CEO. He was the more obvious choice. And in organizations, being known is often more important than being qualified.
Organizations aren’t perfect systems; they are human systems. In a human system, the people making decisions can only consider the information they have. If your ambition is information they don’t have, it cannot factor into their decisions.
The question I’d leave with you:
Does the person who most influences your career trajectory know what you actually want?
Not what you’re willing to accept or what you’d be fine with—what you want.
If the answer is no, that is not their failure. It is an action you haven’t taken yet.
Only you can make your ambition visible.
