Day 13: Design a Learning and Development Plan

The concept

Training is an event. Development is a change in capability.

This distinction is simple but powerful. Many organisations spend money on training and then wonder why performance does not change. Employees attend sessions, complete modules, and collect certificates, but the work looks the same afterward.

AI can help design development plans that connect learning activities to performance outcomes. The goal is not to create a longer training calendar. The goal is to help people do real work better.

Plain English

A useful development plan says what capability needs to change, how the person will practise it, and how the manager will support transfer into work.

Start with the capability gap

Do not begin with courses. Begin with the gap.

Ask:

• What does the person or team need to do better?
• What can they already do well?
• What will the future role or performance level require?
• What business problem does this development solve?
• What evidence shows the gap exists?

For example, "needs leadership training" is too vague. A clearer gap might be:

Needs to lead cross-functional project meetings where priorities conflict and decisions must be made without direct authority.

That gap suggests different development activities than a generic leadership course.

Blend learning modes

Formal training can help, but it is rarely enough.

A strong development plan mixes:

• Formal learning: courses, workshops, certifications, reading
• On-the-job practice: stretch assignments, project ownership, presentations, case handling
• Peer learning: shadowing, communities of practice, peer review
• Manager coaching: feedback, reflection, goal setting, support

The mix matters because people build capability through practice and feedback, not content alone.

Make manager behaviour explicit

L&D plans often fail because the manager's role is assumed rather than stated.

Managers should:

• agree the development goal
• create opportunities to practise
• give timely feedback
• remove blockers
• review progress regularly
• connect learning to real work
• reinforce behaviour after training

If the manager does not do these things, the development plan becomes an HR document rather than a performance tool.

Define success measures

Every development activity should have a success measure.

Completion is not enough. "Attended workshop" does not prove capability changed.

Better measures include:

• delivered a client review independently
• handled two escalations with manager observation
• produced analysis with fewer revisions
• led a team meeting with structured feedback
• improved quality score
• reduced dependency on manager approval

Success measures should be visible in work.

Keep the plan realistic

Development plans often fail because they ignore workload.

If someone has two hours per week for development, do not create a plan that assumes five. If the manager is overloaded, do not rely on weekly coaching unless their calendar can support it. If the team works shifts or time zones, design around that reality.

AI can create an ambitious plan. HR must make it executable.

Review:

• time required
• cost
• manager capacity
• business seasonality
• employee workload
• access to practice opportunities
• psychological safety
• review cadence

Realistic plans are more valuable than impressive ones.

Use 90-day reviews

Development needs checkpoints. A 12-month plan without review points becomes stale quickly.

At each 90-day review, ask:

• What activity was completed?
• What was practised in real work?
• What changed in performance?
• What evidence supports that?
• What support is still needed?
• What should be adjusted for the next period?

This keeps development alive and responsive.

Connect development to retention

Development is not only about capability. It is also about trust.

Employees are more likely to stay when they can see a future path and when managers invest in their growth. A clear plan does not guarantee retention, but it signals that the organisation is paying attention.

This is especially important for high-potential employees, employees preparing for promotion, and employees whose skills need to evolve with the business.

Prioritise the few capabilities that matter most

Development plans fail when they try to improve everything.

Choose the two or three capabilities that will create the most meaningful performance change. If the plan lists ten development priorities, the employee and manager will struggle to focus.

Use these questions:

• Which gap is blocking performance now?
• Which capability will matter most in the next role?
• Which skill creates the greatest business value?
• Which behaviour can be practised in real work soon?
• Which development priority has manager support?

AI may generate a broad plan. Your job is to narrow it.

Design for transfer

Learning transfer is the point where new knowledge becomes changed behaviour at work.

To design for transfer, add:

• a real work assignment
• a practice opportunity
• feedback from the manager
• reflection after the task
• a second chance to apply the feedback

For example, if the goal is stronger stakeholder presentations, the plan should not stop at "attend presentation training." It should include preparing an actual presentation, rehearsing with the manager, delivering it to stakeholders, receiving feedback, and applying that feedback in the next presentation.

This is where development becomes performance.

Make constraints visible

Constraints do not make a plan weaker. Ignoring them does.

Common constraints include:

• limited budget
• seasonal workload
• manager availability
• shift patterns
• remote teams
• time zones
• compliance requirements
• employee confidence
• lack of practice opportunities

Ask AI to design within these constraints. A modest plan that can happen is better than a sophisticated plan that nobody has time to run.

Give the employee ownership too

Development should not be something done to an employee by HR and their manager. The employee needs clear ownership.

Ask the employee to document:

• what they are practising
• where they need feedback
• what felt difficult
• what improved
• what support they need next

This creates shared responsibility. It also gives the manager better information for coaching conversations.

It also makes progress visible between formal checkpoints.

Today's practice

Choose one role, team, or employee group. Run the prompt and review the output.

Ask:

1. Is the capability gap specific?
2. Does the plan include practice, not just training?
3. Is the manager role clear?
4. Can progress be measured in work?
5. Is the plan realistic for time and budget?

By the end, you should have a development plan that feels practical enough to implement and clear enough to review.