Consider a designer leaving a review with praise for a complex redesign but no clear explanation of why the promotion did not happen. The feedback sounds positive, yet it gives them little to act on. When you have been passed over for promotion, use the next conversation to separate concerns about your work from gaps in how that work was documented or presented. Bring one or two concrete projects, and leave with expectations you can check against future work.
A redesign might have involved difficult tradeoffs, research findings, and collaboration with engineering. “Great project” does not tell you whether the review considered your individual decisions, the scope you handled, or the outcome. The items below help you find out without treating an uncertain decision as a verdict on your career.
What should you clarify after being passed over for promotion?
Ask about the decision while the examples discussed are still fresh. You may not get a complete account of every conversation, but a specific question can reveal what to document next.
- Identify the stated gap. Ask which expectation for the next level your current evidence did not establish. Write down the answer in terms you can test against a project.
- Check whether the issue was work or visibility. Ask whether the concern is the scope of work you took on, its outcome, or the evidence available to support it. Each calls for a different response.
- Request an example of stronger evidence. Ask what a convincing example for that expectation would show. This is more useful than a general instruction to “show more impact.”
- Confirm what you personally owned. If the review focused on a team result, ask whether your decisions within that work were clear to the people assessing it.
Write down the answers in your own words after the conversation. Where the feedback remains vague, record the uncertainty rather than translating it into a requirement nobody actually stated.
If several projects fit the stated gap, this guide to choosing promotion case examples can help you weigh scope, ownership, and proof.
Which work should you document before the next review?
A promotion case needs enough detail for someone else to understand the scale of your contribution. Effort matters, but long hours alone do not establish the judgment, scope, or effect of the work.
- Select a project tied to the stated gap. If the concern was ownership, choose work where you made a consequential design decision rather than listing every deliverable you produced.
- Record the starting constraint. Note what users, teammates, or the existing workflow needed before you made a change. That gives your result a meaningful reference point.
- Separate your decision from the team's output. For a redesigned flow, name the tradeoff you resolved and the work your collaborators owned. Precision helps others trust the account.
- Check each outcome claim. Use a reliable measure when you have one. Otherwise, describe what you directly observed without turning encouraging feedback into an unsupported business result.
- Locate permissible proof. Note where approved research summaries, design decisions, or feedback can be found at work. Do not transfer confidential designs, private user information, or sensitive company materials into a personal tool.
Capture these details as projects finish, then spend a short weekly check-in filling the most important gaps. Waiting until the next review makes it harder to recover why you chose one solution over another.
What should you agree on for the next discussion?
A stronger record cannot make a promotion decision predictable. It can make the next conversation more specific, including when the answer is that you need different work rather than better documentation.
- Name an opportunity to demonstrate the missing expectation. Ask what work would give you a fair chance to show it in your current role. If no such opportunity is available, record that constraint.
- Agree on a point to revisit progress. A check-in before the next formal review gives you time to learn whether your evidence is addressing the concern.
- Test one example aloud. Briefly explain the problem, your decision, and the result to your manager. Ask which part still needs proof or clearer ownership.
- Keep the decision and the feedback distinct. Record what was said, what you plan to do, and what remains unresolved. That prevents an unclear conversation from hardening into a false rule about your performance.
How do you keep the evidence ready?
Pick one recent accomplishment and apply the relevant items before your next check-in. If you can explain your ownership but cannot support the result, you know what to verify. If the result is clear but your decision is missing, add the reasoning while you still remember it. That is a practical way to make the next discussion more grounded, whatever its outcome.
Keep a promotion evidence record in ImpactLogr as the work happens, so your next conversation can draw on specifics rather than recollection.