If you've been listening to this podcast for any length of time, you know I like to pull ideas from real situations… not theory, not hypotheticals, but things people are actually living through at work. This week's episode came together exactly that way. I was scrolling LinkedIn and came across a post by Ethan Evans about an engineer who had been stuck in a mid‑level role for more than thirty years. Thirty years. Not because this person wasn't talented… not because they were lazy or disengaged… but because they focused exclusively on technical excellence and didn't care what their managers thought.

That post immediately took me back to Episode 75 of this podcast, where I talked about the transition from Junior to Senior roles. Ethan's story and that episode are really saying the same thing from different angles; careers stall when the rules for promotion change, but you keep playing the game the same old way. Today, we're going to connect those dots. We're going to talk about why excellence alone doesn't get you promoted… why that first major career transition is where a lot of people get stuck… and how to reframe your work so it actually translates into advancement. Whether you're early in your career, deep into it, or managing a team of people who want to grow, this episode is for you.

Let's start with something uncomfortable but important. Most people believe promotions are the reward for being really good at your job. That belief works… for a while. Early in your career, advancement is often driven by competence. You learn faster. You make fewer mistakes. You need less supervision. You can handle a heavier workload without things breaking. That's why those early promotions sometimes come quickly; Analyst I to Analyst II. Junior Engineer to Engineer. Associate to Senior Associate. It feels linear. Predictable. And then… it just stops.

That moment is what Episode 75 was really about. The transition from junior to senior is the first time your career asks something fundamentally different from you. Not more effort. Not longer hours. Not a bigger to‑do list. Something else entirely. And this is where Ethan's post fits perfectly. His point was simple but powerful; technical excellence alone does not create business value. Promotions, especially as you move up, are not awarded for effort or purity of craft. They're awarded for impact. That's not cynical… that's just how organizations work.

If you've been rewarded your entire career for being excellent at execution, it's logical to believe the way forward is to double down. Do better work. Take on more work. Be the person who fixes everything. Be the reliable one. But continuing down that path is a trap. It's how people accidentally build maintenance careers. Ethan used that phrase very intentionally. Doing maintenance work exclusively leads to a maintenance position; stable, valuable, necessary… but rarely fast-growing or far-reaching.

And maintenance work doesn't just mean keeping systems running or lights on. It shows up in every role. It's the analyst who produces flawless reports that nobody uses to make decisions. It's the marketer who executes campaigns perfectly without ever tying them to revenue. It's the project manager who keeps plans immaculate but never challenges whether the plan makes sense. All of this is high-quality output. All of it takes effort and skill. And almost all of it is invisible when promotion decisions are being made.

Now let's layer in the junior-to-senior transition. The biggest change at that point in your career is not scope; it's perspective. Senior roles require you to understand why the work exists, not just how to do it. They require you to connect your effort to outcomes that matter to the business. And that's where Ethan's three buckets become incredibly useful; revenue generation, cost reduction, and moat construction.

These aren't engineering concepts, or marketing concepts, or finance concepts. They're business concepts. They're the lenses leadership uses when deciding where to invest time, money, and attention. And the moment you start framing your work through those lenses, something shifts. You stop sounding like someone who executes tasks well and start sounding like someone who understands the business. That's the moment you begin thinking like someone who gets promoted.

Let's walk through each of these, but through a career lens rather than a technical one.

Revenue generation doesn't mean you personally sell something. It means your work creates the conditions for revenue to grow. Early in your career, that can look like asking better questions; who uses this output, how does it help them move faster, what decision does it enable? As you become more senior, it often means prioritizing work that expands capability rather than endlessly refining what already exists. And if you manage people, this shows up as translation. Helping your team understand how their work ties to revenue matters, because if they can't articulate that connection, you can't advocate for them effectively.

Cost reduction is often misunderstood. People hear that phrase and think layoffs or budget cuts. In reality, cost reduction is about efficiency; time, risk, rework, and complexity. Junior employees contribute here by eliminating friction, simplifying processes, and automating repetitive tasks. Senior employees contribute by redesigning systems, not just operating within them. Leaders contribute by making tradeoffs explicit and aligning effort to what actually matters. If your work reduces the effort required to achieve the same outcome, that's business value. But only if someone knows it happened.

Moat construction is the least obvious and the most senior-coded of the three. This is work that creates defensibility; knowledge that's hard to replicate, processes competitors don't have, capabilities that compound over time. Early in your career, this might look like developing deep expertise in a niche area that becomes strategically important. Later, it might look like standardizing best practices or mentoring others so the organization doesn't rely on a single hero. From a leadership perspective, moat construction often looks like culture, talent development, and institutional memory.

And here's the key insight that ties this back to Episode 75. When you move from junior to senior, you're expected to shift from producing outputs to shaping outcomes. That shift is invisible if you don't name it.

This is where so many careers stall. People are doing work that creates value, but they're not framing it in a way the organization recognizes. Or worse, they're doing work that feels valuable to them but doesn't map cleanly to revenue, cost, or moat. The engineer Ethan mentioned didn't get stuck because they lacked skill. They got stuck because they optimized for the wrong scoreboard. And organizations always promote against a scoreboard… whether they admit it or not.

Let's talk about force multiplication. In Episode 75, I described the shift from doing to influencing. This is another way of naming the same transition. When your impact is one-to-one, your ceiling is low. When your impact is one-to-many, your ceiling rises. Mentoring is force multiplication. Removing roadblocks is force multiplication. Clarifying priorities is force multiplication.

And every one of those maps directly to Ethan's framework. Mentoring reduces cost by increasing efficiency. Removing roadblocks accelerates revenue. Building better systems creates a moat. But again, none of this matters if you assume people will notice on their own.