Early in my career, I believed what most people believe about getting promoted.

I was leaving my first corporate management role.

I'd been brought in to lead an SEO team inside a large organization that built websites for attorneys. It was a specific role with a specific scope. I understood what I was hired to do and I did it.

And then I kept going.

I sought permission to work closely with our product team to launch a new product that increased customer website traffic. I built systems that increased cross-functional communication and cross-trained people from other departments. I didn't wait for someone to tell me there was more to own. I just kept identifying problems adjacent to my core responsibility and solving them. Building things the team needed that didn't exist. Taking on work that didn't have a clear owner because it needed to get done and I could see how to do it.

By the time I decided to leave, the role I was actually doing looked almost nothing like the role I'd been hired for.

I found out later what happened when my director sat down with the VP to talk about backfilling my position. The VP asked a question that stopped the conversation cold.

"What role are we trying to fill? Are we trying to fill the one we hired him for or the one he turned that role into?"

They couldn't answer it. Because the role I'd built over those years didn't have a title or a job description. It existed because I had created it.

I didn't know it at the time, but that question is one of the most valuable things anyone has ever said about my career. Not to me — about me. And it clarified something I've believed ever since.

💡The Vault Insight: The people who advance fastest don't just fill roles. They redefine them. And when they leave, their organization can't figure out how to replace them.

Most employees operate inside the four corners of their job description. They do what they were hired to do, they do it well, and they wait to be recognized for it. That's not wrong. But it's also not a path to accelerated advancement.

The managers and leaders who consistently rise — across industries, company sizes, and functions — share a specific behavior. They treat their job description as a starting point, not a boundary. They master what they were hired to do first, and then they look up and ask: what else needs to exist here that doesn't yet?

That question is where great careers are built.

It's also where the span of control lever gets pulled most naturally. When you solve problems nobody asked you to solve, influence outcomes outside your formal scope, and build capabilities the organization didn't know it needed — you are demonstrating exactly the kind of expanded influence that makes the case for the next level.

Not through ambition. Through evidence.

What this looks like in practice

It doesn't require grand gestures or political maneuvering. It starts with a simple habit: every time you encounter a problem adjacent to your core role — something that affects your team's performance, the organization's results, or a gap nobody else seems to be addressing — ask yourself one question.

Is there a reason I can't own this?

Usually there isn't. Usually the only thing standing between you and expanded scope is the assumption that someone else will handle it or that it's not your place to step in.

It is your place. That's exactly your place.

The managers who wait for someone to expand their role formally are always behind the managers who expanded it themselves and then let the org chart catch up.

A word of caution

Expanding beyond your role only works if you've mastered what you were actually hired to do first. Taking on adjacent problems before you've delivered on the core ones signals poor judgment and creates resentment from the people who are counting on you for the basics.

The sequence matters: nail the job you were given, then reach beyond it. Never the other way around.

And when you do reach beyond it — document it. In your career document, in your performance reviews, in the language you use to talk about your own contributions. Because the value of expanded scope is only visible to the organization if you make it visible.

The VP who asked that question about my role was seeing something I hadn't fully articulated myself. Your job is to articulate it before you're already walking out the door.

The question worth asking yourself right now

If your manager had to describe your role to a VP today — not the role you were hired for, but the role you've actually built — what would they say?

If the answer is roughly the same as your job description, that's useful information.

The gap between those two answers is where your next promotion might live.

—Sean McGinnis, 2X President, CMO, COO & EOS integrator