Career Growth Plans for Employees: How Managers and Employees Set Development Goals Together

A career growth plan template is most useful when it links an employee’s ambitions with work they can take on now and is informed by career growth plan examples that show what a strong plan looks like, while making the manager’s role explicit. It is not an annual form or a vague promise to “talk about your future sometime.” It is a working agreement in which both people define what growth means, decide how the employee will practice it, and agree on how to recognize progress.

Start With a Shared Picture of the Employee’s Next Growth Step

The opening conversation should establish direction before anyone starts listing courses or assuming a promotion is the goal. Employees need space to explain what interests them, where they want more responsibility, and which parts of their work leave them energized or frustrated. The manager can then connect those interests with opportunities that fit the team’s actual work.

Growth does not necessarily mean becoming a manager or receiving a new title. An employee might want to have more influence in cross-functional work, sharpen their technical judgment, communicate more effectively with clients, or learn to run a project. Each can be a meaningful next step, even when a promotion is not immediately available.

It helps to distinguish between two questions:

• What does the employee want to explore over the longer term?
• What development step would be most useful over the next few months?

For example, an employee may eventually want to lead projects involving several teams. Their next step does not have to be a management title. They might own a small cross-functional launch, coordinate a project timeline, or lead a meeting in which several groups need to reach a decision.

Manager–Employee Conversation Prompts

Use questions that open up a real discussion instead of inviting a prepared response.

Questions for the employee

• Which parts of your current work would you like to do more often?
• What kind of work challenges you in a productive way?
• Which skills would help you contribute at a higher level?
• Where do you feel underused, stuck, or less confident than you would like?
• What responsibility would you like to take on next?

Questions for the manager

• What upcoming work could offer the employee a safe but meaningful stretch opportunity?
• Which capabilities matter most in the employee’s current role or likely next step?
• Which strengths should the plan build on rather than neglect?
• What constraints, such as workload or limited project access, could make the goal difficult?
• What support can I realistically provide?

The purpose is not to resolve an employee’s entire career in a single meeting. It is to agree on a next step that is useful, achievable, and tied to real work.

Choose One or Two Capabilities That Will Make the Biggest Difference

A plan is easier to use when it concentrates on one or two capabilities instead of a long list of broad intentions. “Improve communication” and “be more strategic” may sound reasonable, but neither gives the employee much to practice or the manager much to assess. Specific behaviors give both people a clearer basis for action.

Communication, for example, might involve leading a monthly project update that explains risks, decisions needed, and next actions. Strategic thinking might involve analyzing customer feedback, spotting patterns, and recommending a change to a process or service.

For each capability, discuss three things:

• Current level: What does the employee already do well, and where would more practice help?
• Target behavior: What would stronger performance look like in day-to-day work?
• Evidence of progress: Which work product, feedback, or new responsibility would indicate improvement?

Consider an analyst who wants to work more effectively with senior stakeholders. Their development priority might be presenting recommendations with greater clarity and confidence. Possible evidence includes concise briefing materials, better meeting preparation, and feedback indicating that leaders understand both the recommendation and the decision being requested.

The capability needs to matter to both parties. The employee should see a connection to their interests, while the manager should see a sensible link to the role, team needs, or available work. Plans that serve only one side generally lose momentum.

Turn Development Priorities Into Measurable Growth Goals

Development goals should provide enough detail to guide action without turning into a rigid scorecard. A useful goal identifies the capability under development, explains where it will be practiced, sets a milestone, and states what evidence will indicate progress.

Use this sequence to write each goal:

1. Name the capability. Select a skill or behavior that can be observed at work. Examples include facilitating meetings, analyzing customer data, delegating tasks, managing project risks, or presenting recommendations.
2. Identify the work setting for practice. Specify where the employee will use the capability. This might be a project, recurring meeting, client interaction, process review, or cross-functional assignment.
3. Set a realistic milestone. Include a date, project phase, or number of practice opportunities. The milestone should create momentum without turning development into a race.
4. Define the evidence of progress. Agree on what will demonstrate improvement. Evidence might include completed deliverables, recurring feedback themes, fewer revisions, clearer decisions in meetings, or a broader scope of responsibility.
5. Include practice as well as outcomes. New capabilities rarely develop fully after one attempt. Include learning activities such as observing an experienced colleague, preparing with a mentor, or trying a technique several times before evaluating the result.

Sample Development Goal

Capability: Leading clear stakeholder updates

Goal: Over the next quarter, the employee will lead two project update meetings for a cross-functional initiative. They will prepare an agenda that states progress, risks, decisions needed, and next actions. After each meeting, they will ask two participants for feedback and use that feedback to improve the next update.

Evidence of progress:

• Meeting agendas and follow-up notes are clear and sent on time.
• Stakeholders can identify decisions and owners without needing a separate explanation.
• Feedback shows improvement in clarity, preparation, or meeting facilitation.
• The employee is trusted to lead a larger or more complex update later in the project.

This goal includes a clear outcome—leading the meetings—as well as deliberate practice and feedback. That combination matters because completing an assignment does not necessarily mean the underlying skill has developed.

Agree on Support, Opportunities, and Ownership

A development plan should not become a task list that is handed to an employee and then ignored. The employee is responsible for their effort and preparation, but the manager also needs to create access, provide coaching and feedback, and make room for practice.

Make this working agreement explicit before finalizing the plan.

Shared Development Plan Checklist

The employee will:

• Prepare for the agreed assignments, meetings, or learning activities.
• Ask for feedback and consider what to apply next time.
• Raise barriers early, including workload conflicts or unclear expectations.
• Keep brief evidence of progress, such as completed work, feedback notes, or examples of improved output.

The manager will:

• Provide suitable opportunities to practice the target capability.
• Clarify what good performance looks like before the employee begins.
• Give timely, specific feedback rather than waiting for a formal review.
• Protect reasonable time for preparation, learning, or mentoring where possible.
• Remove obstacles that are within the manager’s control.

Together, they will:

• Confirm that the development work fits alongside core responsibilities.
• Decide which evidence of success they will review.
• Adjust the scope if the original assignment is too small, too large, or no longer available.
• Keep the plan focused enough to manage.

For example, an employee developing process-improvement skills might own the research, draft a proposal, and present the recommendation. The manager could provide access to performance data, review an early draft, explain who needs to be consulted, and arrange a meeting with the operations group.

This division of responsibility helps avoid a familiar problem: the employee is told to “take initiative,” but has no time, information, audience, or decision authority to act on it. Initiative still requires a place to lead.

Review Progress Through Short, Useful Development Check-Ins

Development plans remain active when they are discussed in short, regular conversations. A monthly check-in may be a practical starting point for goals that involve ongoing practice, but the right schedule depends on the role, workload, project pace, and employee’s needs. Some goals call for shorter, more frequent conversations; others may need less frequent reviews combined with timely feedback after key assignments. A more thorough review every few months gives both people a chance to assess progress and reset the plan if necessary.

Keep the conversation grounded in evidence rather than general impressions. Instead of asking, “Do you feel like you are improving?” ask what the employee practiced, what happened, what feedback they received, and what they plan to change next.

Use each development check-in to work through the following steps:

1. Review what the employee practiced. Discuss the specific meeting, assignment, analysis, presentation, or responsibility connected to the goal.
2. Look at evidence and feedback. Review work samples, stakeholder comments, quality improvements, or examples of increased independence. Feedback should be specific enough to apply, not simply “nice job.”
3. Identify the next stretch. Once the employee has built confidence with a smaller assignment, consider a somewhat broader or more complex opportunity. Growth requires increasing the challenge rather than repeating the same task indefinitely.
4. Remove one obstacle. Ask what is getting in the way. It could be competing deadlines, limited access to information, uncertainty about authority, or a need for more coaching.
5. Confirm actions for both people. End with a clear next step for the employee and the manager. Without next actions, a check-in can become a pleasant conversation that changes very little.

A Brief Review Cadence

A simple rhythm keeps the plan visible without creating unnecessary administration.

• At the start: Agree on the goal, workplace opportunity, success evidence, and support commitments.
• As appropriate: Use part of regular one-to-ones to discuss practice, feedback, barriers, and the next action. Monthly discussions may work well for many ongoing goals, but adjust the frequency when the work or employee needs call for it.
• At the end of a project or milestone: Review what the employee learned and whether they are ready for more scope.
• Every few months: Decide whether to continue, strengthen, replace, or pause the goal based on changing work priorities and career direction.

For example, an employee developing facilitation skills might begin by observing planning meetings and preparing agendas. After demonstrating reliable preparation and follow-through, they might lead a smaller session. Later, they could facilitate a meeting that requires different teams to agree on priorities.

A useful career growth plan changes as the surrounding work changes. Projects end, priorities shift, and employees discover new interests. The plan works when the manager and employee continue to treat it as a shared agreement: practical enough to guide the next step, flexible enough to stay relevant, and supported enough to give growth a genuine opportunity.