You’ve been at the same level for two years. Your reviews are good. Your manager says you’re “on track” but the calibration outcomes don’t match. You read promotion advice that says “do impactful work” or “increase your visibility” and it’s true but useless — it doesn’t tell you which dial to turn first.
This framework is the dial selector. It separates promotion into three distinct axes — scope, impact, and visibility — and takes a strong position on the order to optimize them in. Not all three matter equally. Not at the same time. The order is the framework.
The problem
The naive failure mode is treating “do better work” as the strategy. It isn’t. By the time you’ve been at a level for 18+ months, you’re almost certainly doing the level’s work. The reason you haven’t been promoted is almost never that you can’t do the work — it’s that one of the three axes is mismatched, and identifying which one is the entire game.
The other naive failure mode is the opposite: pure visibility play. Send a weekly status email, present at every all-hands, brand yourself. Sometimes this works. Often it produces a candidate who’s well-known but gets calibrated down because the work behind the visibility doesn’t hold up.
The framework’s claim: promotion at senior+ is scope, then impact, then visibility, in that order. Optimizing them out of order — the classic trap of trying to be visible before you have the scope to be visible about — is how strong engineers stall for years.
The framework: three axes, three diagnostic questions
The three axes are not parallel. They stack.
| Axis | What it is | Diagnostic question |
|---|---|---|
| Scope | The size of the surface you own and influence. | What system / org / problem is yours? |
| Impact | What changed in the world because you did the work. | Which numbers moved, and by how much? |
| Visibility | Who knows the first two. | Who, outside your team, would call you the owner of X? |
The diagnostic question for each axis is meant to be answered with specifics. Hedged answers (“I work on a lot of things across the platform”) fail the test. Strong answers are crisp (“I own the order processing pipeline; my team and one neighboring team depend on it”).
Why scope first
Scope is the gravitational center of senior promotion because the other two axes scale from it.
- Impact requires scope. You can’t move important numbers if you don’t own anything important. A senior engineer with no scope and great execution looks like a strong engineer who got lucky on a project, not someone ready for the next level.
- Visibility requires scope. People don’t get talked about for being a great pair of hands; they get talked about for owning something consequential. Visibility without scope reads as PR; visibility with scope reads as authority.
Scope is also the axis you have the most control over and the longest lead time to acquire. You earn it, sometimes over months, by:
- Finding work that’s unowned but consequential. The graveyard of half-broken systems on every team is a scope lottery — pick one, make it yours.
- Asking explicitly for ownership. The person who says “I’d like to be the technical lead for X” is treated differently from the person who gestures at being involved in X. Ambiguity costs you.
- Trading short-term comfort. The work that grows your scope is rarely the work you’re already good at. It’s the work nobody on the team has signed up for, that someone has to.
The signal-test for whether you have enough scope for the next level: at your target level, does someone on your team or an adjacent team have the same amount of scope you have, plus more? If yes, you don’t have the scope yet — you have the current level’s scope. The bar at calibration is “operates at the next level,” and operating means owning.
Why impact second
Impact is the axis that converts scope into a promo packet. Without impact, scope is just busy work; you owned a thing and nothing happened.
The trap with impact is that engineers reach for engineering metrics (latency dropped, reliability improved, technical debt removed) when the relevant metrics are usually one layer higher (revenue, conversion, team velocity, customer escalations). Engineering metrics matter, but they have to ladder up to a number a non-engineer cares about.
The diagnostic test for impact: can you write a single sentence that takes the form “Because of this work, X (a business or org metric) went from A to B”? If you can’t, you don’t have a packet — you have an activity log.
Examples of strong impact statements:
- “I cut p99 latency on the checkout API from 800ms to 200ms; this drove a measured 4% conversion improvement.”
- “I redesigned the deployment pipeline; the team’s deploy frequency rose from 2/week to 12/week and incident MTTR dropped from 4h to 45min.”
- “I led the migration off the legacy auth service; this freed two engineers who were 80% on maintenance to ship two new features in the next quarter.”
Each of these is a sentence with two metrics: an engineering one and a business/org one. The shape is non-negotiable for senior+ promo packets. The reason: the calibration room is full of people who don’t read your code. They’re reading the impact statement.
Why visibility last (and why it still matters)
Visibility comes third because it’s the axis with the most diminishing returns and the easiest to fake. But it’s not optional. A senior+ engineer with great scope and great impact whose calibration committee doesn’t know who they are is the most common quiet-promo-stall pattern.
The point of visibility isn’t fame. It’s to ensure the people who decide the promotion know about the scope and impact you’ve already accumulated. That’s a much smaller set than “everyone at the company” and the work to reach them is correspondingly smaller — but if you skip it, your scope and impact don’t matter.
The visibility moves that actually shift calibration:
- Your skip-level knows what you own. Not “knows your name” — knows what you own. Once a quarter, an explicit conversation with your manager about what should be communicated upward.
- One peer manager outside your team knows what you own. When the calibration discussion happens, having a second voice say “yes, X owns that and it’s been good” is the highest-leverage advocacy you can buy.
- A short paper trail. Design docs you authored, RFCs you led, an annual or semi-annual self-summary your manager can copy from. The committee reads documents, not memories.
The moves that don’t shift calibration as much as people think:
- Tweeting/posting about your work. Outside-the-company visibility is a different game (recruiting leverage, conference invitations) but it rarely moves your current calibration.
- Hand-raising in all-hands. Often raises perceived volume without raising perceived scope.
- Your team knows what you do. Your team is not the calibration committee.
The order matters: optimize visibility of existing scope and impact, not as a substitute for them.
How to apply it: three worked examples
Example 1: The two-year-stalled IC4
You’ve been an IC4 for two years. Your reviews are consistently “meets,” occasionally “exceeds.” Your manager says you’re “on track for IC5” but it isn’t happening. What’s the diagnosis?
Run the three diagnostic questions:
- Scope: what’s yours? If the answer is “I work on whatever the team is working on, with the team,” scope is the bottleneck. The fix is finding a system or initiative you can put your name on, not better execution on the existing flow.
- Impact: if you do have scope, can you write the “X moved from A to B” sentence? If the metrics are all engineering ones, your packet doesn’t ladder up. The fix is partnering with product or ops to attach a business metric to the engineering work you’re already doing.
- Visibility: if scope and impact are both there, who outside your team knows? If only your manager, you have a visibility gap. The fix is structured: skip-level conversations, one peer-manager advocate, document trail.
The most common diagnosis at IC4→IC5 is scope. The second most common is impact. Visibility is rarely the actual blocker at this transition; the engineer just thinks it is, because visibility moves are easier to do than scope-acquisition is.
Example 2: The visible engineer who can’t get promoted
The opposite shape: you’re well-known, you present in design reviews, people know your name. But the promo packet keeps getting deferred. The calibration feedback is something like “great communicator, but unclear what the actual technical contribution was.”
Diagnosis: visibility ahead of scope. You’re well-known for the position you’re already in, but there’s no underlying ownership producing the signal. The framework’s prescription is uncomfortable: stop investing in visibility moves until you’ve grown scope. Take on something hard and unowned, work on it relatively quietly for two quarters, then surface what you built. The calibration math at that point is dramatically different.
This is one of the bend cases the framework is designed to catch. The intuitive move (be more visible) is the wrong move; the framework’s ordering prescribes the opposite.
Example 3: The newly senior engineer one year in
You just made senior. You’re still doing senior-level work, but you notice the path to staff is foggy. The advice you’re getting is “show staff impact” — which sounds right but doesn’t tell you what to do Monday.
Diagnosis: at the senior → staff transition, the bar shifts. Scope at staff is cross-team, not within-team. Impact at staff is measured in quarters of the org’s roadmap, not features. Visibility at staff means your VP knows what you own.
The framework still applies but the unit of each axis steps up. “Owning a system” no longer counts as scope at the senior → staff transition; “owning a problem space across two or more teams” does. “Cut latency by 50%” no longer counts as impact; “shifted the architecture roadmap so three teams converged on one platform” does.
The fix is: explicitly redraw the diagnostic answers at the staff bar before deciding what to do next. The work of growing scope into a larger box is exactly the work of getting promoted to staff.
Where this framework breaks
Three places.
Companies without honest leveling. Some companies have flat or ill-defined ladders, no calibration process, or promotion-by-loud-voice cultures. The framework assumes a ladder where calibration is deliberate and roughly meritocratic. In a company where promotions are political or arbitrary, scope and impact still help but the framework’s predictive power drops sharply. The honest move there is often to change companies — promotion is downstream of the ladder you’re on.
Performance review systems weighted on different axes. Some places weight visibility more heavily than this framework recommends (think: sales-adjacent or partnership-heavy roles). Some weight scope much more (deep-infra teams). Read your company’s actual rubric and confirm the ordering. The framework’s ordering is a default; the axes are universal but the weights vary.
Early-career transitions (junior → mid). Below senior, the framework applies but lopsidedly. Junior promotions are mostly about demonstrated execution (a fourth implicit axis) and the three above matter much less. The framework is designed for the transitions where calibration committees deliberate, which usually starts at senior.
Tenure-driven companies. A few companies promote primarily on tenure-plus-not-being-bad. The framework’s prescriptions are noise in that environment; the prescription is to be patient and not be bad.
The framework also has one well-known failure mode: it can mislead you into thinking visibility is always third. There are inflection moments — joining a new team, returning from leave, a re-org — where a short, deliberate visibility push does matter, because the calibration committee is rebuilding their model of you. The general rule is “scope first,” but watch for these moments where visibility temporarily matters more.
What this framework is really saying
Promotion is not a meritocracy in the literal sense. It’s a mechanism that converts ownership and demonstrated impact into a level change, gated by who knows about the first two. The mechanism has a reliable shape: scope drives impact drives visibility, and trying to skip a step is the dominant reason senior+ engineers stall.
If you’re not getting promoted, the question isn’t “am I working hard enough?” It’s “which of the three axes is mismatched?” — and the answer is almost always the one furthest left in the chain.
Related
- Plan: Complete Senior Backend Interview Prep — if the right answer is to leave the company, this is the surface area for the next loop.
- Framework: What’s Durable vs What’s Hype — what to invest in for the long game beyond the next promotion.
- Aligning Projects With Your Next-Level Goal — how to pick projects that grow scope deliberately rather than by accident.