How to Have a Promotion Conversation With Your Manager
By Daniel Okafor
Prepare a promotion conversation with a one-page evidence brief, manager scripts, clear criteria, and a practical follow-up plan.
Career Guide | Published 2026-10-27
Turn vague promotion feedback into clear expectations and an agreed next step.
A promotion-readiness conversation should connect specific work evidence to the employer's next-level criteria, distinguish readiness from business opportunity, and end with an agreed owner, action, support, and review date. This guide includes a worked example, discussion scripts, and a reusable one-page brief.
Leave with criteria, a next step, and a review date A useful promotion conversation answers three questions: which next-level expectations you already meet, what evidence is still missing, and, where your employer considers it, whether there is a business need or available role at that level. Bring a short evidence brief, ask your manager to test it against the actual criteria, and agree on what happens next. You do not need a polished speech about everything you have done. You need a discussion that turns “keep doing good work” into an observable, realistic plan. Use the one-page brief Find out which decision you are asking for Before booking the meeting, choose the target. Do you want a promotion to a defined level, a move into management, recognition of responsibilities you already perform, or a development plan towards a future role? These requests need different evidence. A promotion conversation should not quietly become a team-transfer request or an open-ended promise to take on extra work. Ask for the current job framework, role description, promotion process, and submission dates if those exist. Check who recommends, who approves, and whether a vacancy or business justification is required. If your employer has no written framework, ask your manager to identify the responsibilities and behaviours they would need to see. Record that understanding as a working agreement, rather than inventing your own official criteria. For a concrete employer example, GitLab's promotion process considers individual readiness alongside business opportunity and uses a promotion document. That is GitLab's process, not a rule every employer follows. Its distinction is useful: more evidence of readiness may not resolve a missing role or budget. A simple meeting request is: “Could we spend our next development conversation reviewing my readiness for [level or role]? I will bring three examples against the expectations. I would like to understand what is already convincing, what is missing, and how the decision is made.” Match three examples to the next level Choose examples for relevance, not size. Finishing a large volume of current-level work may demonstrate reliability while leaving a next-level expectation unanswered. If the next level involves handling ambiguity, explain a decision you made when there was no ready-made instruction. If it involves wider influence, show how other people used your work. Ask your manager to confirm that these interpretations fit your employer's framework. For each example, write the expectation, your action, the observable result, and the boundary of your contribution. Include a second occurrence if the expectation is sustained behaviour. A colleague's specific feedback can support a claim, but praise without an example does not explain what you did. Expectation Useful evidence Question to resolve Own a problem through delivery You clarified the problem, chose an approach, coordinated dependencies, and checked whether the result was used. Was the scope and independence enough for this level? Improve work beyond your tasks You introduced a handoff method that another team adopted and adjusted it after feedback. Does this show wider influence, or only a useful local improvement? Help others become effective You supported a colleague through a new responsibility, with specific feedback on what they could then do independently. What further evidence of sustained support would matter? You can use qualitative results when reliable numbers are unavailable. Describe what changed and how you know. Do not invent revenue, time savings, or a percentage to make a promotion case look stronger. Keep sensitive work evidence within the systems and access rules your employer permits. Turn a project story into a readiness claim Consider an operations specialist seeking a senior role. Their strongest example is a recurring handoff problem between scheduling and customer support. The title of the project alone does not show senior-level work. Too broad: “I improved our handoff process and worked with several teams. This shows I am ready to be senior.” More useful: “The senior-role description includes resolving issues across team boundaries. I mapped where requests lost an owner, proposed a shared escalation rule, and coordinated the trial with scheduling and support. Both teams adopted the agreed rule. My contribution was the analysis and coordination; the team leads approved the change. I have a similar example from a separate rollout. Do these demonstrate the scope you expect, or is the missing piece longer-term ownership?” The second version lets the manager assess a particular expectation. It distinguishes personal contribution, team credit, and remaining uncertainty. It also invites a useful disagreement. Your manager may say the examples are strong but too local, or that you need to demonstrate the behaviour over a longer period. That response gives you something concrete to discuss. Keep the supporting detail available, but start with a one-page brief. A chronological list of every task can bury the few examples that matter most. Ask questions that make “not yet” usable Open with your target and the strongest example. Then ask your manager to assess the case rather than endorse your preferred conclusion. “Which expectation does this demonstrate?” is more useful than asking whether they agree you work hard. If the feedback is “show more leadership”: “What would that look like in my role? Could we name a decision or responsibility I should own, and what successful delivery would show?” If the evidence is incomplete: “Which one or two gaps most affect readiness? What example would address each gap?” If the manager supports the case: “What needs to be prepared for the decision, who owns it, and when is the next possible review?” If there is no available role: “Is the constraint the opportunity rather than my readiness? When can we review that constraint, and which development options are realistic meanwhile?” When the answer stays vague, offer a small proposal: “Would leading the next handoff review be a suitable way to demonstrate cross-team ownership?” Ask what authority, support, and workload changes would make it possible. Avoid accepting an unlimited list of extra responsibilities in exchange for an undefined future outcome. Allow room for a genuine gap. If you have not done an important part of the target role, agree on an opportunity to practise it. A development activity is evidence you are building, not evidence you already have. Agree on a bounded plan The University of Rochester's career conversation guide recommends development goals with action steps, timing, and criteria for success. Apply that structure to the specific gap you discussed, using your employer's process. For example, agree that you will lead one upcoming planning session, document the options and decision, and collect feedback from the relevant stakeholders. Your manager will clarify your authority and review the evidence with you in a month. The month is a checkpoint for learning, not a promised promotion date. Send a short follow-up: “Thanks for discussing [target]. My understanding is that [evidence] supports [expectation], while [gap] needs further demonstration. I will [action], with [support] from you. We will review [evidence or outcome] on [date]. The next formal decision depends on [process or opportunity]. Please correct anything I have misunderstood.” At the checkpoint, compare the result with the agreed criterion. If circumstances changed, ask what changed and update the plan. If criteria repeatedly move without a clear explanation, seek clarity through an appropriate manager or HR conversation before committing to more work. Keep the record factual. Your one-page promotion brief Copy this into a document your manager can review. Fill it with evidence you can explain and are permitted to share. If there is no defined target level yet, make agreeing on that target the first meeting outcome. Target role or level: Reason I want this scope of work: Actual criteria and decision process: Expectation 1: My action, result, and supporting evidence: Expectation 2: My action, result, and supporting evidence: Expectation 3: My action, result, and supporting evidence: What I have not demonstrated yet: One proposed development action: Support or authority needed: Question about available opportunity: Agreed owner, next step, and review date: Before the meeting, practise explaining the strongest example in a minute, then answering a question about your personal contribution. Leave room on the page for your manager's assessment. The finished brief should help you decide what to do next even if the answer is “not this cycle.” If you already use AskMyCareer, its Career Graph can help organise non-confidential career evidence for these conversations.