Responsibility can expand before your title or compensation changes. A dry promotion leaves you doing work associated with a broader role without the formal recognition you expected. To address it, you need a clear account of what changed, evidence of how you performed, and a direct conversation about the decision process. For a designer, that shift might mean moving from delivering assigned screens to setting interaction patterns that other teams adopt. Document the change before asking your manager to assess it. Otherwise, the conversation can collapse into competing impressions about how hard you have worked.
Step 1: Write down the change in scope
Put your earlier responsibilities beside the work you have taken on. Focus on ownership rather than volume. “More design requests” describes a heavier workload; “defined the interaction approach used across several related flows” describes a different kind of responsibility. Include when the shift began and which decisions you now make without waiting for someone else to set the direction.
Keep this account specific enough for your manager to check. Name the projects, collaborators, and deliverables, but leave confidential design files and sensitive business details in approved company systems. You should be able to explain the difference in your scope without relying on a new title to prove it.
Step 2: Collect evidence of the work's effect
A broader remit alone does not establish that you performed well in it. Select a few examples that show what you decided, why it was difficult, and what happened afterward. An interaction pattern you defined that another team adopted can show influence beyond your own deliverable; feedback that a revised flow resolved a recurring usability issue can show the quality of the decision.
Preserve the source of each claim while the details are accessible. Record who can speak to the work and where approved evidence lives. If an outcome is still uncertain, say what has been observed rather than projecting a result. You are building material that can withstand a follow-up question, not trying to make every project sound decisive.
Step 3: Ask your manager how the case will be evaluated
Bring your scope summary and examples to a dedicated conversation. Try a direct question such as, “Which expectations for the next role have I demonstrated, and where do you still need evidence?” Then ask who contributes to the promotion decision and when your work could be reviewed. Processes differ across workplaces, so get the answer for yours rather than assuming that strong feedback automatically becomes a formal change.
Think about what your manager would need to explain when other people assess the case. They may need to distinguish a sustained increase in scope from temporary coverage, and your contribution from the team's overall result. If their answer is vague, ask for a concrete example of work that would resolve the uncertainty. That gives you something more useful than “keep doing what you're doing.”
A practical list of questions to ask your manager about getting promoted can help you press for specifics when the answer is vague.
Step 4: Agree on a review point and record what happens
Close the conversation by confirming the expectations you discussed and when you will revisit them. A brief written recap can prevent two people from remembering different commitments. Continue noting work that bears on the open questions, especially examples that show the expanded scope has lasted beyond a single urgent project.
At the review point, compare the agreed expectations with the evidence you have gathered. You may learn that a formal change is possible, that more proof is needed, or that the organization has no clear plan to recognize the role you are already performing. None of those outcomes is guaranteed by good documentation, but each gives you a clearer basis for deciding what to do next.
Keep the case usable between conversations
A dry promotion is difficult to discuss when every meeting starts with reconstructing the same history. Maintain a short account of your changing scope, the strongest examples, and the questions still awaiting an answer. ImpactLogr can help you retain those work records so you can update your case without rebuilding it from memory.
Keep your expanded-scope evidence together in ImpactLogr before the next discussion with your manager.