Promoted to Burn: So I Said Yes

This essay is Part 2 of the "Promoted to Burn" series. It looks at how missing support gets mistaken for growth, and how that pressure shifts to the person who says yes.

TL;DR: Not all promotions are embraced. Some are endured. This essay explores what it feels like to accept a leadership role you don't feel ready for, not because you want power, but because you can't find a language to say no. It follows the internal journey of someone pulled forward by visibility, loyalty, and pressure, but left without support.

In the first essay, Promoted to Burn: Congratulations (and Good Luck), I focused on the organisational forces that lead to these premature promotions: urgency, pressure, the appearance of trust. That piece spoke to those making the decision: the ones handing over the title, redistributing leadership to buy time.

Which, in hindsight, may not be a coincidence. Much of my own experience has been on that side, in senior or executive roles, trying to navigate succession, urgency, and system strain. I've seen how tempting it is to solve structural issues with symbolic trust. And I've tried to stay aware of that trap, even as I've sometimes contributed to it.

This second piece focuses on the other side of that exchange: the perspective I didn't centre before.

And here's a reflection I've returned to many times since: In my years leading teams, and supporting others through coaching or mentorship, I've often seen people step eagerly into new leadership roles, even when I've advised caution. At times I wondered whether it came from overconfidence, or from a kind of courage fuelled by inexperience. But I've come to see something else beneath it: how structural gaps create emotional pressure, how visibility turns into obligation, and how "yes" becomes the only story left to tell.

This piece is for them.

Some yeses are not decisions. They're just what's left when there's no room to say no.

You say yes. But not from certainty.

Not from a burning desire to lead, or a clear plan for the future. Not even from confidence.

You say yes with a smile that feels too tight. A breath you didn't know you were holding. A nod too quick. Relief, maybe, that they see you. And dread, because now they do.

You say yes since it feels easier than saying no. The organization doesn't make it safe to refuse. Loyalty starts to feel like obligation. And being noticed often means being used, even if no one means it that way.

This is a pattern I've seen more times than I'd like to admit. Not just in teams I've led, but in people I've coached, mentored, or simply known well enough to notice the shift. Sometimes they reach out for advice. Sometimes they don't. But the shape is always similar: a loyal, steady person gets pulled into a leadership role, often after months of keeping things together without the title.

Despite the hesitations, the doubts, the warnings, they still say yes. Not always out of ambition. At times out of hope. At times out of fear. Often just out of momentum.

Take M., a senior engineer who had been quietly patching cross-team issues for months. When offered a team lead role, he hesitated, but said yes. Within six weeks, his calendar doubled, his IC work shrank, and his mental bandwidth dissolved. No one had clarified scope. No one had checked in. Six months later, he asked to step down, and the system treated it as personal failure.

Capable. Steady. Helpful. Not pushing to be in charge, but the one people rely on when things fall through. The one who stays late without being asked. The one who patches over gaps no one else notices.

One day, a title is offered. It comes with more responsibility, unclear authority, vague support. But it's framed as a compliment: "You've already been doing the job. This just makes it official."

So there's a smile. And a yes.

Yet behind the smile is something else. A quiet calculation.

If no, then what? Will trust disappear? Will they be seen as ungrateful? Difficult? Will this be the last time they're thought of for anything?

And maybe, just maybe: will this role finally come with support?

It doesn't.

Within weeks, the shift is clear. The people who congratulated them now ask them to make decisions. The same problems they used to fix quietly are now their official responsibility. The boundaries disappear. All the unclear parts become theirs to handle.

And they carry it, through syncs and standups, ambiguity and expectation, all the subtle shifts no one names.

Until they wonder if the role was meant to support them, or if it was just designed to soak up problems.

Because here is the truth:

Most organizations don't plan for people to say no. They plan for people to absorb problems.

They reward helpfulness with responsibility. Loyalty with visibility. And visibility with pressure.

The job description stays vague: "you'll figure it out." The support is informal: "you know who to ask." The responsibilities multiply, not through mandate, but by default.

A team lead starts managing performance without clarity. A staff engineer becomes the de facto product owner, not because it was agreed, not because no one else stepped in.

Structure, mentorship, reinforcement? These remain absent.

Instead, there's applause. And they're left standing under it.

What makes a "yes" believable is not its volume, but its inevitability.

That yes didn't come from conviction. It came because no one asked what they would need to thrive. Only whether they would accept.

They said yes because there was no way to express doubt. No way to say "maybe." No way to stay visible without taking on responsibility.

And this silence compounds.

Engineers, designers, leads, promoted not out of readiness, but out of convenience. Because someone had to. Because someone was there. Because someone didn't resist.

It still unsettles me. Because I've offered those roles. I've watched people say yes, and I've wondered whether we truly made space for what that yes demands.

Sometimes, there is no real choice. The person on the receiving end doesn't resist, not because they're ready, but because resistance isn't designed into the system. When structure can't hold uncertainty, even good intentions become quiet pressure. And the cost of saying yes doesn't show up until it's too late to take it back.

And for some, there's simply no luxury of refusal. Economic pressure, visa constraints, family obligations: these too shape the "yes." And they rarely show up in the promotion memo.

This dynamic plays out differently across cultures. In some contexts, refusal isn't just difficult, it's seen as disloyal or even insubordinate. In others, hierarchy makes "yes" a ritual, not a choice. But the cost of silence still lingers, even when the reasons differ.

They are leading now. Are they carried, though?

That's the question many can't name out loud.

Because if they are no longer being carried, if the weight never shifts back, is this still leadership? Or just a floating title, separate from the support it was supposed to include?

From the outside, it might look like composed confidence. Steady hands. A calm presence.

Yet calm isn't always clarity. At times it's just containment: the effort to seem okay, when no one's checking beneath the surface.

Inside, they remain alone with the doubt. They keep hoping that someone will check, not just on delivery, but on them. They continue stretching to hold a space that was never reinforced.

Some try to compensate by over-functioning: doing more, saying less. Others withdraw, shrinking the role to something manageable, even if that means leading in name only. And some burn quietly: carrying the role, the perception, the silence, until the cost shows up elsewhere.

And the irony is, from the outside, it still looks like they're succeeding. Because nothing visibly breaks. Until the part that stretched too far does, and by then, it rarely looks like a system problem. It just looks like they couldn't keep up.

I wrote this not to correct the first essay, but to complete it. Because the real harm of these promotions isn't only in the system that gives them, but in the silence that surrounds them.

Sometimes it works. When trust comes with proper support, and visibility comes with backup, early leadership becomes a platform, not a trap.

And if we don't listen to that silence, we'll mistake compliance for conviction and leave people to carry what was never theirs alone.

That's not sustainable leadership. It's trust that quietly becomes burden.

Understanding this pattern won't fix it. But it can protect your sense of self and help you name what the system forgot to offer.

If you're in this role now, unsure whether you're growing or absorbing, start with one question: What support do I need that no one named? Sometimes, just being able to say it out loud is a start.

Because if no one names it, nothing changes.

And eventually, the person breaks, not with noise, not with drama, but through gradual distance, gradual resignation, or gradual exit.