Make your next development conversation about a responsibility you want to learn to handle, the team problem it could address, and the support needed to try it.
The outcome does not have to be a promotion promise. It can be a well-defined assignment, access to feedback, or a clear explanation of what opportunities the organization can currently provide.
This guide helps you prepare that conversation and turn it into a development plan you can revisit.
Start with a responsibility, not a vague ambition
“I want to grow” gives your manager little to respond to. Describe what you want to become more capable of doing:
- Explaining an analysis well enough for someone to make a decision.
- Coordinating a project across teams.
- Reviewing work and giving constructive feedback.
- Handling a more complex customer problem.
- Developing deeper judgment in a specialist area.
Then explain why that responsibility matters to the team. You are looking for an overlap between your development needs and useful work—not inventing a business benefit to justify any activity you happen to prefer.
The US Office of Personnel Management describes an individual development plan as an ongoing employee–supervisor partnership, supported by preparation and feedback. It distinguishes development planning from performance evaluation. That is a helpful distinction for this conversation, although your employer’s own process may use different documents or combine discussions. OPM career development guidance.
Prepare a specific request
Bring a short note covering five points.
The responsibility you want to develop. Make it narrow enough to observe. Replace “be more strategic” with “compare options and explain a recommendation, including its trade-offs.”
Your current evidence. Include an example of something you can already do and a candid account of what you still need to learn.
A suitable assignment. Suggest a task in which the capability could be practiced. Check whether the work is genuinely needed.
The support required. This might be a reviewer, access to relevant meetings, training, protected time, or an experienced colleague to shadow. Make the time cost visible.
What would count as progress. Name the artifact, behavior, or decision that can be reviewed. Completing a course may be part of the plan, but it does not by itself demonstrate independent performance.
If you are also seeking promotion, ask separately about the applicable criteria, decision-maker, timing, and available positions. A useful development assignment does not establish that a promotion is available or approved.
A conversation you can adapt
“I’d like to get better at coordinating work across teams. The upcoming handoff project seems relevant because responsibilities are still being clarified. I can already maintain the action list, but I need practice resolving dependencies and presenting decisions. Could I coordinate a limited part of it, with you retaining decisions outside my authority? I’d like us to agree what good work would look like and when you could review it.”
Follow with questions that reveal practical constraints:
- Which part would be appropriate for me to own?
- What should I stop or hand over to make time?
- Who can give feedback on the work itself?
- What decisions would remain with you?
- If this assignment is unavailable, what smaller opportunity could meet the same learning need?
A constructive answer may be a different assignment. Evaluate whether it practices the capability you wanted rather than judging only whether your first proposal was accepted.
Copy this development agreement
Use this as a discussion record, not a contract or a scoring instrument.
| Item | What to agree |
|---|---|
| Development focus | The responsibility or capability to practice |
| Team purpose | The useful problem the assignment addresses |
| Starting evidence | What you can already demonstrate and what remains uncertain |
| Assignment and boundary | What you will own; |
Send a concise written recap after the conversation and invite corrections. If something was not agreed, record it as unresolved rather than presenting silence as approval.
Worked example: developing coordination skills
This fictional example shows a development discussion and its limits. It does not represent a typical promotion outcome.
Jordan works in customer operations. They maintain accurate records but want experience coordinating work between support and implementation teams.
Jordan proposes running an entire onboarding improvement project. Their manager explains that the scope is too large alongside current responsibilities and that no training budget is available.
They narrow the assignment: Jordan will coordinate the handoff checklist for one existing project. The manager will retain staffing and priority decisions. A more experienced coordinator will review Jordan’s first dependency list, and one routine reporting task will be deferred during the trial.
Their agreement defines three review questions: Are owners clear? Are unresolved dependencies visible? Do requests for decisions reach the appropriate person?
Jordan’s first draft lists tasks but assigns several of them to “the team.” The reviewer asks who will actually act. Jordan identifies a specific owner for each action, confirms the responsibilities with the people involved, and refers one unresolved ownership decision to the manager.
At the review, Jordan brings the original draft, the corrected version, and feedback. The evidence shows progress in identifying dependencies and clarifying requests. It does not show that Jordan can independently manage every kind of project.
The manager offers a second, slightly more complex assignment. There is still no approved promotion vacancy. Jordan records both facts: a development opportunity exists; promotion timing remains unknown.
If the conversation does not produce a workable plan
“Keep doing good work.” Ask for an example of the additional responsibility or standard the manager has in mind. If the answer remains vague, propose a concrete task and ask what would make it useful.
An assignment is added without anything being removed. Estimate the work involved and ask which commitments should change. Do not treat unlimited extra work as the default price of development.
The manager supports the idea but cannot provide feedback. Ask whether another qualified colleague can review the work. Agree what that reviewer can assess and what decisions remain with the manager.
The opportunity disappears. Return to the learning objective. Shadowing, a smaller contribution, or a sample task may be alternatives. Be clear about which parts they cannot demonstrate.
The organization cannot explain the next career step. Separate what you can learn here from what the organization can offer. You may continue a useful assignment while gathering information about other internal or external options.
The discussion becomes a performance concern. Clarify the current expectations and any formal process first. Do not assume a development worksheet replaces the employer’s performance procedures.
Your next step
Write one development request and identify an existing task where it could be practiced. Ask for a conversation with the person who can allocate the work and support.
Use Improve Workplace Competitiveness to design the practice itself. Use Annual Career Review System when you need to compare these opportunities with the rest of your career evidence.