We All Got a Promotion

The question everyone is asking wrong

Every conversation I have with customers right now circles back to the same place. What’s my future with AI? What happens to my team? What happens to me?

It’s the dominant narrative. White collar workers, knowledge workers, the entire professional class asking some version of: am I about to be replaced? LinkedIn is full of it. Conference keynotes are full of it. The dinner table is full of it.

I get it. I asked myself the same thing for a long time.

But I think this framing is fundamentally wrong. Not because the disruption isn’t real. It is. Not because there won’t be casualties. There will be. But because the defensive posture, the “what happens to me” question, blinds you to what actually happened.

What actually happened is you got a promotion.

What a promotion used to look like

When I was at GE, I worked as an architect and product owner. When I had a new idea, something I believed could drive real value, I couldn’t just go build it. I had to make the case. Write up the use case. Estimate the return on investment. Identify the resources I needed, which always meant people. Then I had to argue for those people, because every person I wanted on my project was a person pulled from someone else’s.

That’s how it worked. You had an idea, and then you spent weeks or months selling the idea before you could even start executing it. And most of the time, you didn’t get what you asked for. You got a fraction of the team, a compressed timeline, and a mandate to make it work anyway.

That dynamic wasn’t unique to GE. That’s how most organizations operate. The bottleneck was never the idea. It was the resources to execute.

Now think about what happened in the last year. That bottleneck collapsed. Not partially. Almost entirely.

You got a team

I want to coin this, because I’ve been saying it to customers for months and I think it’s the most accurate framing of what’s happening: we all got a promotion.

Not in title. Not in pay, not yet anyway. But in capability and scope. The thing that used to take years or decades of career progression, building and leading a team, happened to all of us in about six months.

Think about how career progression typically works. You start as an individual contributor. If you’re lucky and you’re good, eventually you get to manage one or two people. Then maybe a small team. Get to ten direct reports and you’re considered an established leader in most industries. Twenty, thirty, forty people under you? That’s senior leadership territory. Hundreds? That’s executive scope.

Most people never make it past the first rung. Most individual contributors stay individual contributors for their entire careers. Not because they lack the talent, but because the opportunities are scarce and the competition is fierce.

And then AI showed up and handed everyone a team.

Why “promotion” and not just “tool”

I’m deliberate about this word. I don’t like the framing that we all got little minions working for us, or that AI is just a faster typewriter. That misses what actually changed.

I’ve been a team leader. I’ve been an engineering leader. I’ve had the benefit of working with really good leaders and the misfortune that most of us share of working with really bad ones. And a few things surface to the top when I think about what separates them.

A good leader has a strong vision. They know where they want to take the team. They structure that vision into something actionable: to get to this endpoint, we need to do X, Y, and Z. But they allow for autonomy in the specifics. They don’t dictate every line item inside X, Y, and Z. They say: here’s where we’re going, here are the major steps, now help me figure out the details along the way.

That, to my mind, is exactly what we all have now with AI-driven tooling. The ability to set a vision, define the high-level architecture, sequence the work, and then let the execution happen with autonomy inside those guardrails.

And that is the hard part of being a professional. Especially in technology.

The skill gap nobody is talking about

I’ve watched people throughout my career spend decades in the specifics. They’re brilliant at the task inside X or Y or Z, but they don’t know how X, Y, and Z fit together. They don’t care to know. They don’t want to set the vision. They want to be told what to build, and they want to build it well.

There’s nothing wrong with that. It’s honest, valuable work. But it’s the work that just got automated.

The part that didn’t get automated is the part most people never practiced: setting direction, defining architecture, sequencing decisions, and knowing when to push back on what your team gives you.

When I work with AI, I consistently remind myself: I have to be the linchpin. I set the vision. I set the high-level architecture. I set the sequencing. And then, critically, I solicit feedback. Good leaders do this. They look for people to challenge their thinking. They don’t just hand down edicts and walk away.

The same thing applies with AI. If you prompt without clear architectural guidance, you’ll get a result that technically works but doesn’t fit your broader vision. If you don’t push back, if you don’t challenge the output, you get something that just acquiesces to you. That’s not leadership. That’s abdication.

The people thriving right now are the ones who already thought like leaders, even when they were individual contributors. They know how to decompose a problem. They know how to evaluate output critically. They know how to iterate. They know how to say “this isn’t good enough, here’s why, try again.”

The people struggling are the ones trying to do their old job, just faster. They’re using AI as a typewriter when they should be using it as a team.

The replacement narrative is a trap

I’m biased. I’ve been a technologist and a builder my entire career. I don’t know what “having a team of AI experts” means if you’re an accountant or a lawyer. I’m not going to pretend I do.

But in my world, for builders and people who ship things, this is the biggest unlock I’ve seen in my career. The ability to go from idea to execution without begging for resources, without waiting for headcount approval, without compromising your vision because you could only get two of the five people you needed.

That’s not a threat. That’s the opportunity most people spend their entire career waiting for.

The replacement narrative is a trap because it keeps you in a defensive posture. You’re so busy worrying about whether you’ll have a chair when the music stops that you miss the fact that the music changed entirely. It’s not musical chairs. It’s a completely different game, and the rules favor people who can think at a higher level of abstraction.

So what do you do with it

Yes, there’s going to be serious disruption. I don’t dispute that. It’s going to be uncomfortable for a lot of people. But I’d really encourage a reframing.

Rather than “I’m going to be replaced,” ask yourself: what is the opportunity I previously would have had to fight, yell, kick, and scream for resources to achieve? What’s the project I shelved because I couldn’t get headcount? What’s the vision I deprioritized because the team was stretched too thin? That’s your starting point.

Stop doing work. Start parceling work.

This is the single biggest shift. All of us need to move our thinking from day-to-day tasks to how do I sequence and parcel work in a consumable fashion. The exact same way a tech lead does.

When I was a tech lead, 80% of my job was taking a big vision, cutting it into bounded pieces, defining the clear edges of those boundaries, and handing each piece to a developer. Not micromanaging the implementation. Not writing the code myself. Just making sure the boundaries were clean, the dependencies were clear, and the developer had enough context to operate autonomously within their scope.

That’s the job now. For all of us.

Think like an architect

There’s an idea I keep coming back to: architects are like city planners. They define where the school goes, where the hospital goes, where the houses go. But they don’t define what the school, hospital, and houses look like. That’s left to the people building them.

I think we’ve all just become information architects. And that, in a lot of ways, is what managers and leaders have always been. They’re information architects. They decide what gets built and where it fits, not how every brick gets laid.

Pull your vision forward

This is the part I think will be the hardest, because having visionary ideas is genuinely difficult. It’s a muscle most of us haven’t had to flex because execution constraints kept our ambitions in check.

Before, you might have thought about your work in terms of tasks, days, weeks, maybe months. The bigger visions, the quarter-scale and year-scale ideas, those lived on a someday list. When I have a bigger team. When I’m a director. When I have the resources.

That someday is today. The promotion already happened. The resources are here.

Those projects you were waiting on a team of five or ten people to execute? Start now. Craft the vision. Parcel the work. See how AI can execute as your team rather than your task assistant.

The things you were putting off until you had the seniority, the headcount, the budget? You have them. Not in the traditional sense, but in capability. The gap between “I have an idea” and “I can ship it” has never been smaller.

The reframe

I don’t see most people thinking this way yet. Not the customers I talk to, not the industry at large. We’re still stuck in the replacement loop, asking “what happens to me” when the better question is “what can I build now that I have a team?”

Stop defending your position. Start using it.