Promotion standards rarely fail because they are fully secret. They fail because they are partly visible, unevenly interpreted, and hard to translate into day-to-day work. That is why learning how to understand your promotion criteria matters so much. If you misread what the next level needs, you can spend a cycle doing solid work that never turns into a persuasive case.
For most individual contributors, the issue is not effort. It is interpretation. You are trying to figure out whether the next step depends on broader scope, cleaner execution, more independent judgment, stronger cross-functional influence, or simply better evidence of work you already do.
Do you already have written criteria, or are you working from hearsay?
Start here because the next move depends on what exists. Some companies have a career framework, level guide, or review rubric. Others have partial documentation and a stronger unwritten layer. If you only know the hallway version of the criteria, your first job is to get closer to the official source.
Look for:
- role expectations by level
- review rubrics or competency descriptions
- examples of what the next level is trusted to own
- language used in past promotion packets, if those are shared internally
If written criteria exist, read them like a translator, not a believer. Terms such as "drives outcomes," "operates independently," or "influences across teams" sound clear until you try to prove them. Pull out every vague phrase and ask what visible behavior would demonstrate it in your work.
If there is no written guidance, ask your manager for the clearest available version. You are not asking whether promotion is possible. You are asking how the case is judged. That distinction tends to produce better answers.
When the criteria exist, can you map them to actual work?
Many people stop too early here. They find the framework, read a few bullets, and assume they understand it. Usually the hard part starts after that.
Take each criterion and test it against recent work. For example:
- "Handles ambiguous problems" becomes an example where requirements were unclear and you shaped the path forward
- "Increases team leverage" becomes a system, process, template, or analysis others reused
- "Works across functions effectively" becomes a case where you aligned people with different incentives and moved the work anyway
- "Demonstrates stronger judgment" becomes a decision with tradeoffs, not just correct execution
If you can map a criterion to two or three concrete examples, you probably understand it well enough to build toward it. If you cannot, the phrase is still too abstract. Bring that gap into a conversation with your manager and ask what good evidence would look like.
That is also where a lightweight capture habit helps. A promotion case gets easier when the details were saved close to the work, not rebuilt from memory months later. ImpactLogr is useful here because it keeps examples tied to outcomes and proof instead of letting them dissolve into scattered notes.
Is the gap about scope, or is it about proof?
This branch changes your plan.
Sometimes you truly are not yet doing next-level work often enough. Your projects may be too narrow, too supervised, or too execution-heavy. In that case, the answer is not better writing. You need different opportunities.
Other times, the work is already there, but your case is weak because nobody can easily see the pattern. You solved hard problems, influenced decisions, or improved a process, yet your examples live in message threads, meeting memory, and half-finished docs.
Ask yourself:
- Have I owned work with broader reach than before?
- Do I make decisions instead of waiting for them?
- Have I handled tradeoffs that affect other people?
- Can another person quickly explain my impact with specifics?
If your answer is mostly no, focus on changing the shape of your work. If your answer is mostly yes, focus on preserving evidence and making the pattern visible.
Those are different problems. Confusing them can waste an entire cycle.
Are you being measured on output, judgment, or influence?
Promotion criteria often blend all three, but one usually matters more at your next level. That priority affects what examples you should collect.
If output is the main signal, your strongest material will show reliable delivery, quality, and ownership of meaningful work. If judgment carries more weight, save examples where you made calls under uncertainty, chose between imperfect options, or prevented downstream issues through better thinking. If influence matters most, document how you got alignment, unblocked another team, or changed a process without formal authority.
A simple way to test this is to look at who gets praised and promoted around you. Do promotion discussions emphasize volume, trust, complexity, systems thinking, partner relationships, or visible initiative? You are not copying another person. You are learning which proof the system repeats back.
Once you identify the dominant signal, tune your logging around it. Keep short notes on the work itself, the outcome, and the reason it counted. Avoid storing sensitive internal material in a personal tool. Capture the substance in your own words.
Do you need a clearer ask from your manager, or a clearer story from yourself?
Sometimes the blocker is upstream. Your manager may be giving vague feedback like "keep doing this" or "show more leadership" without translating that into observable work. In that case, ask narrower questions:
- What would someone at the next level be trusted to do here that I am not yet doing consistently?
- Which recent example looked closest to the bar, and what was still missing?
- In promotion discussions, what evidence is easiest for others to repeat about a strong case?
Sometimes the blocker is your own story. You know you are growing, but your examples are scattered and your pattern is hard to articulate. Then your job is to organize what already happened into a case another person can carry into a room you are not in.
If the issue is manager clarity, push for sharper examples and expectations. If the issue is story clarity, build a tighter record of ownership, impact, and proof.
What should you do next based on your answer?
Here is the practical decision tree for how to understand your promotion criteria:
- If no written criteria exist, ask for the clearest evaluation standard your team uses and write it down in plain language.
- If criteria exist but feel vague, translate each phrase into visible behaviors and recent examples.
- If the work is below the bar, seek projects with more scope, judgment, or cross-functional reach.
- If the work is already near the bar, improve the evidence trail so the pattern is obvious.
- If your manager is unclear, ask narrower, example-based questions.
- If your own case is unclear, organize your examples into a reusable promotion narrative.
Promotion criteria become more understandable once you stop treating them as abstract labels and start treating them as claims that need evidence. That shift makes the next action clearer.
Turn the criteria into evidence you can actually use
Understanding the bar is useful. Keeping a record of work that maps to that bar is what saves you later. Once you know what counts, capture examples while the details are still fresh enough to prove ownership, judgment, and outcome.
You can create a structured record in ImpactLogr to track the examples that match your promotion criteria before review season forces you to reconstruct them.