Turn experience and feedback into a development plan
Help an employee explore their next role and identify a manageable sequence of skills to develop.
How this works
Help an employee explore their next role and identify a manageable sequence of skills to develop. Use this when an employee wants to explore a next role and turn feedback into a manageable learning sequence. The plan should reflect the employee's goals and real role requirements rather than prescribe a career from a model's opinion.
Collect factual experience, voluntary goals and relevant feedback, then map them to the requirements of a chosen direction. Separate strengths with evidence from skills needing practice. Draft small learning actions and review checkpoints with the employee, preserving their control over the plan.
Before you start
Employee goals
Obtain the person's stated interests, constraints and desired direction.
Experience evidence
Use relevant projects, self-reflection and permitted feedback.
Target-role requirements
Collect current internal role expectations or representative professional requirements.
Prepare the inputs
- goals
- Required
preferred direction and practical constraints
Do not infer ambitions from current title.
- experience
- Required
activities, examples and outcomes
Keep unsupported self-claims clearly attributed.
- feedback
- Required
relevant observations with source and date
Separate opinion from demonstrated behavior.
- role_requirements
- Required
competencies and evidence expectations
Avoid treating one vacancy as a universal career standard.
Implementation, step by step
Clarify the direction
- Discuss the employee's goals and which options they want to explore.
- Keep alternative directions open when preferences are uncertain.
Checkpoint: The plan has an employee-owned purpose.
Map evidence
- Connect experience and feedback to target competencies.
- Distinguish demonstrated skills, partial evidence and unknowns.
Checkpoint: The gap map is factual.
Choose a small learning sequence
- Prioritize a few skills that matter for the chosen direction.
- Prefer practical exercises or bounded work opportunities with observable outputs.
Checkpoint: The sequence is manageable.
Define support and review
- Identify resources, practice opportunities and people who can provide feedback.
- Do not promise promotions, assignments or budgets without owner agreement.
Checkpoint: The plan has realistic dependencies.
Review with the employee
- Refine actions and timing based on their preferences and workload.
- Record agreed checkpoints and leave unapproved opportunities as proposals.
Checkpoint: The employee can accept, revise or decline the plan.
Decisions along the way
Feedback conflicts
Explore context and avoid treating the most negative statement as truth.
Target role is unclear
Compare a few directions before prescribing a curriculum.
Practice requires manager support
List it as a dependency rather than an assigned responsibility.
What you will produce
development-plan.md
MarkdownAn employee-reviewed learning sequence.
Include: goal · evidence · gaps · practice_actions · resources · checkpoints
development-evidence-map.csv
CSVA factual basis for progress conversations.
Include: competency · evidence · gap · next_example
Check the result
- Confirm goals come from the employee.
- Verify recommendations connect to actual role requirements.
- Check actions have observable outputs and realistic support.
- Remove promises of promotion or employment outcomes.
When something goes wrong
Feedback is too vague
Ask for examples before making it a development priority.
Learning plan exceeds available time
Reduce scope and agree a smaller sequence.
Role requirements change
Revisit the gap map rather than continue an obsolete plan.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Synthetic: plan a move toward project coordination.
Inputs
Employee wants to coordinate projects and has organized two small events. Feedback supports clear follow-up but provides no evidence of budget tracking.
Expected result
Synthetic result: propose a small project-planning exercise and supervised budget-tracking practice. Mark budget skill as unassessed, not deficient, and avoid promising a role change.
Run a small pilot
Start small
Create one plan with a few actions and a scheduled employee review.
Record the baseline
Record planning effort and whether actions produced useful evidence.
Agree success criteria
Agree progress indicators with the employee before expanding the plan.
Stop or revise
Stop if recommendations override the employee's goals or become unsupported performance judgments.
Keep the scope clear
- The employee remains in control of development choices.
- A learning plan does not authorize promotion, staffing or compensation decisions.
Check before using
Keep the employee in control and validate the recommendations against real role requirements.
Business activities
- Support and develop employees
- Deliver courses and training
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Employee’s experience · Self-described interests · Peer feedback · Target role
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow