How To Progress In Your Career

The Unwritten Rules of Moving Up

Most people think career progression is about working harder or learning the right skills. It's not. I watched two people in the same cohort at my last company get promoted at the same time while I was still grinding for a title that took another eighteen months to materialize. The difference wasn't skill. It was visibility and leverage, and almost nobody talks about that openly. Here is what actually happens when you try to move forward. You do good work, then you wait. Waiting is the default state for most mid-level professionals. The trick is making sure someone who can affect your trajectory knows you exist and that you're competent, which sounds obvious but most people skip because they believe competence should speak for itself. It doesn't. I learned this the hard way after spending two years building infrastructure that three VP-level managers had never heard of.

How To Progress In Your Career

The framework I use is straightforward enough that it feels underwhelming when you write it down. It has three components: scope expansion, strategic visibility, and transferable proof. Scope expansion means you don't wait for a bigger title to start acting like you have a bigger one. Strategic visibility means the right people know about your output before performance review season. Transferable proof means you accumulate evidence that travels with you when you switch teams or companies. Let me be specific about scope expansion because this is where most people mess up. You take on a problem that's currently owned by nobody or by someone who doesn't have the capacity to solve it. This is different from volunteering for extra work because that just makes you the person everyone dumps tedious tasks on. There's a line. The way I found it was simple: I looked for problems that caused friction between departments and volunteered to document the workflow and build a bridge. Documentation doesn't get you promoted on its own. What gets you promoted is being the person who removed a friction point that half the org complained about quarterly. I once encountered a very specific edge case with scope expansion that I want to mention because it's easy to get wrong. A senior engineer at my last company, let's call him Marcus, took over a cross-team integration project that was already failing. He built the solution in three weeks, submitted it, and got zero recognition because he never looped in the stakeholders during development. He assumed the finished product would speak for itself. It didn't. The project was already politically complicated and two managers claimed ownership of the outcome. Marcus ended up with a performance footnote instead of a promotion. The workaround is brutal but simple: send a one-paragraph update to all stakeholders every Thursday while you're building the thing. Not a detailed report. Just three sentences about what you're working on and what blocker you've removed. By the time the work ships, people feel invested in the outcome because they were kept in the loop. You become associated with the solution in their minds before they even see it.

Strategic visibility is the component most people hate because it feels like politics. It is politics. That's not a bad thing. Politics is how decisions get made when more than two people are involved. You don't need to schmooze or play office games. You need to make sure the people who make promotion decisions know what you do. The practical way to do this is to write internal briefs. I'd write a half-page doc every quarter describing a problem I solved, the approach, and the measurable outcome. Then I'd send it to my manager and cc anyone who might benefit from knowing. This takes about twenty minutes per quarter and it compounds. After a year you have a paper trail that shows consistent impact without you ever having to say "I deserve a promotion." Here's a counter-intuitive point about visibility that nobody warns you about. Promoting you from within is cheaper and less risky than hiring someone externally. So if you're invisible and competent, a competent visible person will always beat you because the decision-maker perceives lower risk. This means you should sometimes apply for roles outside your company before you apply inside for a promotion. Not because you want to leave. Because having an external offer changes how seriously your current employer takes your requests. It's blunt and some people won't like it. It works though. I've seen it resolve stalled promotion conversations that had been sitting for six months in about three weeks. Transferable proof is the last piece and the most neglected. It's everything that proves your value beyond your current org's internal systems. Promotions, awards, shipping records, salary bands at other companies. Most people don't track this systematically. I kept a running Google Doc with dates, project summaries, metrics, and peer feedback. When I needed evidence for anything, I had it ready in five minutes instead of spending a week digging through emails and Slack history. This also becomes useful when you're negotiating. You can't negotiate with feelings. You negotiate with data.

There are serious limitations to this approach that I should be honest about. Scope expansion only works in organizations that are large enough to have ambiguous ownership. If you're at a startup with fifteen people, everyone knows what you do and the framework adds noise instead of signal. Strategic visibility breaks down in companies with genuinely toxic leadership where honest high performers get punished regardless of exposure. And transferable proof has no value if your industry doesn't have transparent compensation data, which is still the case in several sectors. If your company culture is genuinely misaligned with meritocratic progression, no amount of framing will fix it. The workaround in that scenario is to document your growth aggressively and leave on your own terms rather than waiting for a process that isn't going to work for you. That's not defeat. That's a rational use of your time. The one pitfall I see repeatedly is people treating this as a checklist instead of a habit. Sending quarterly briefs, expanding scope proactively, and maintaining your proof doc takes roughly thirty minutes a week. That's it. The people who fail at career progression usually aren't failing because they lack talent. They're failing because they treat career movement as something that happens during review season instead of as a continuous process you manage the same way you manage a project. Pick one component and start this week. The rest follows from there.