Gallup reported in January 2025 that only 30% of employees strongly agree someone at work encourages their development, down from 36% in March 2020. That is the real cost of how most companies handle employee development and training. Money goes into the program, people show up, and by Friday the skill has faded.
The problem isn’t that managers don’t care. It’s that they were never given a system for what happens after training ends. The workshop gets booked, the LMS gets stocked, and then the manager is left to hope the learning survives contact with real work. It usually doesn’t.
This playbook gives you that system. We’ll walk through a skills gap analysis your managers can run with data they already have, an individual development plan (IDP) they can build in one conversation, the 70-20-10 model applied to how you design programs, a post-training reinforcement cadence for the first 30 days, and a way to measure behavior change instead of completion rates. Two of those sections come with ready-to-use artifacts you can copy into your next planning cycle.
What is employee development and training, and why most programs don’t work
Employee development and training are two different jobs that need two different designs. Treating them as one is the first reason programs fall flat.
Training versus development
Training closes a specific skill deficit the role needs now. Someone can’t give clear feedback, so you teach a feedback model and they practice it. Development builds capability for future roles. A strong engineer who might lead a team next year needs to grow judgment, influence, and people skills long before the title arrives.
The design logic differs. Training is targeted, short, and measured against a clear before-and-after. Development is longer, tied to a career path, and measured against growth over quarters. A plan that mixes the two without naming which is which ends up doing neither well.
The transfer-gap problem
Here is where most programs actually break. Ebbinghaus’s forgetting curve shows that roughly 70% of new information is forgotten within 24 hours, and about 90% within a week, without reinforcement. The content was fine. The retention system didn’t exist.
The gap is in what happens after training, not in the quality of the training itself. And the person best positioned to close it is the manager, who is usually absent at exactly that moment. LinkedIn’s Workplace Learning Report found that only 15% of employees say their manager helped them build a career plan in the past six months.
So the rest of this playbook focuses on the after. Gap analysis tells you what to develop. The IDP gives the employee a plan. The 70-20-10 model tells you where learning actually happens. The reinforcement cadence makes it stick. Measurement proves it worked.
How to run a skills gap analysis your managers can actually use
A skills gap analysis fails when it turns into a survey project. Managers don’t need a new data collection exercise. They need to read the data already sitting in front of them.
Where to look
Three sources cover almost everything a manager needs, and all three already exist:
- Performance review themes. The same feedback showing up across multiple reviews points to a real, recurring gap, not a one-off.
- 1:1 patterns. The problems an employee keeps raising, or keeps avoiding, in weekly conversations are the clearest signal of where they’re stuck.
- Project post-mortems. When a project slips or a launch goes sideways, the retro usually names the skill that was missing, if you read it as a development signal instead of a blame exercise.
What to measure and prioritize
For each gap, score two things: business impact and coachability. Business impact asks how much this gap costs the team if it stays open. Coachability asks how realistically this person can close it with support in a reasonable window. A high-impact, high-coachability gap is where your effort pays back fastest.
| Team Member | Role | Current Level (1-3) | Target Level | Gap | Business Impact (H/M/L) | Coachability (H/M/L) | Priority |
|---|---|---|---|---|---|---|---|
| Sarah Chen | Senior Analyst | 1 | 3 | Delegation | H | H | Develop now |
| Mark Reilly | Team Lead | 2 | 3 | Giving feedback | H | M | Develop with support |
| Priya Anand | Engineer | 2 | 3 | Stakeholder influence | M | H | Develop with support |
| Tom Becker | Coordinator | 1 | 2 | Prioritization | L | M | Monitor |
Skills Gap Snapshot: rate current and target on a simple 1-3 scale, then let business impact and coachability set the priority. Copy this for each direct report.
The output is a prioritized list in three tiers: develop now, develop with support, and monitor. That triage stops managers from spreading thin attention across every gap at once. To run this across a team without rebuilding the grid each time, start from our skills gap analysis template, and if you want to tie gaps back to formal training options, the training needs analysis template pairs with it.
The employee development plan (IDP): a manager’s step-by-step guide
An individual development plan is where the gap analysis becomes a commitment. A good IDP is short, specific, and observable. A bad one is a wishlist nobody revisits.
What belongs in it, and what to leave out
Five fields make an IDP usable:
- A goal tied to a business outcome. Not “improve communication” but “run team standups that surface blockers, so delivery stops slipping.”
- The specific skills that goal requires, drawn straight from the gap analysis.
- Learning activities mapped to 70-20-10, so the plan isn’t only a course link (more on that ratio below).
- The manager’s committed support. What you will actually do: observe a meeting, give feedback, open a stretch assignment.
- A 30/60/90 measurable milestone, so progress is checkable, not vibes.
Leave out vague aspirations, anything without a timeline, and goals you can’t observe. If you can’t picture what “done” looks like in a real work moment, the goal needs rewriting.
The IDP conversation
The plan comes out of a growth conversation, not a performance review. The difference matters: a review looks backward and grades, a growth conversation looks forward and builds. Move through four stages, reflect, aspire, plan, then commit, and let the employee do most of the talking.
| Conversation Stage | Manager Prompt | What to Listen For |
|---|---|---|
| Reflect | ”Looking at the last quarter, where did you feel most and least effective?” | Self-awareness; whether their read matches yours |
| Aspire | ”Where do you want to be in a year, and what role would stretch you?” | Genuine motivation versus a default answer |
| Plan | ”What’s one skill that, if it grew, would unlock the rest?” | A focused priority, not a long list |
| Commit | ”What will you try first, and how will we both know it worked?” | A concrete, observable next step |
IDP Conversation Guide: your job is to prompt and listen, not to assign. The plan sticks when the employee names the goal.
This is also where two of the most requested development skills tend to surface. If delegation comes up, our delegation assessment gives the employee a baseline to work from. If the goal touches their own coaching skill, the coaching assessment does the same.
Run the IDP on a quarterly cadence. In month one, draft the plan and set the first milestone. In month two, do a mid-point check-in to catch drift early. In month three, review what changed and reset the goal for the next quarter.
The 70-20-10 model: what it actually means for how you design programs
The 70-20-10 model is one of the most cited ideas in learning and development, and one of the most ignored in practice. Once you take it seriously, it changes where you put your budget.
What it says
The model holds that roughly 70% of development comes from experiential learning (doing the work), 20% from social learning (other people), and 10% from formal learning (courses and workshops). Most training budgets are inverted. They pour money into the 10% and leave the 90% to chance.
Where managers actually spend, and where the leverage is
The 10% is largely outside a manager’s daily control once it’s scheduled. You book the workshop, people attend, and the calendar does its thing. The 70% and the 20% are different. They happen in every 1:1, every project debrief, every stretch assignment you hand out.
That is the leverage. A manager activates the 70% by deliberately assigning work that builds the target skill, then debriefing it. A manager activates the 20% by pairing the employee with someone stronger, or by getting in the room to give feedback. None of that needs a budget line. It needs intention.
The implication
Training events are inputs, not outputs. Attendance proves nothing about behavior. The best program isn’t the one with the slickest LMS, it’s the one wired to the best manager cadence around it. Which is exactly the cadence most teams never build, so let’s build it.
Why training doesn’t stick, and what managers must do in the first 30 days after
The single highest-return window in employee development and training is the 30 days right after a training event. It’s also the window almost nobody manages on purpose.
The forgetting curve in practice
Recall the numbers from Ebbinghaus’s forgetting curve: roughly 70% of new information gone in 24 hours, about 90% in a week, without reinforcement. The common reflex is to schedule a follow-up session. That just restarts the curve from a slightly higher point and decays again.
The only thing that actually works is spaced, low-stakes practice in the real work context. The skill has to get used, in a small way, soon after it’s learned, and then again, and again, until it’s wired into how the person works.
The post-training manager reinforcement cadence
This is the artifact most teams are missing. It’s a simple weekly rhythm the manager owns.
| Timeframe | What the manager does |
|---|---|
| Day 1 (within 24h) | Ask “what’s one thing you want to try this week?” Set a small micro-experiment tied to the skill. |
| Week 1 | Check the micro-experiment in the next 1:1. Give one piece of specific, behavioral feedback. |
| Month 1 | Observe one real situation. Give structured feedback against the IDP milestone, then adjust the plan. |
| Ongoing | Keep the skill an active 1:1 topic until it’s a default, not an effort. |
Post-training reinforcement cadence: this costs a manager roughly 10-15 minutes a week. That’s the whole price of making training stick.
How AI coaching fills the daily reinforcement gap within this cadence
Most managers want to reinforce. What they lack is headspace. Between standups, escalations, and their own deliverables, the daily reps the cadence calls for are the first thing to slip.
That daily gap is where AI coaching helps. Risely’s coach Merlin is native in Slack and Microsoft Teams, so it handles the between-1:1 reps right where work happens. An employee can run through a tricky moment with Merlin, grounded in their development goal, without waiting for the next meeting. Merlin is the reinforcement layer, not a replacement for the manager’s observation and feedback. You still do the noticing and the coaching. Merlin keeps the practice warm in between. You can try Merlin free to see how that works inside your chat tools, and if you’re building this into a broader learning and development strategy, the cadence is the engine that makes the strategy real.
How to measure development beyond completion rates: Kirkpatrick Level 3 (Behavior)
If you measure training by completion rates, you’re measuring whether people showed up, not whether anything changed. That’s the gap between activity and impact.
Why completion rates are the wrong metric
Enrolled, completed, quiz passed, satisfaction scored: every one of those measures exposure, not change. Kirkpatrick’s model lays out four levels of evaluation: Reaction (did they like it), Learning (did they absorb it), Behavior (did they apply it on the job), and Results (did the business outcome move). Level 3, Behavior, is where return on the investment actually lives. It’s also the level almost nobody measures, because it’s harder than reading an LMS dashboard.
A manager-level before-and-after model
You don’t need a research team to measure Level 3. You need one observable behavior per goal.
Before the training, name the specific behavior change you expect to see, such as “raises blockers in standup without being asked.” Then document instances of that behavior for 30 to 60 days after. A short log, a couple of concrete examples a month, is enough. This is not a 360 survey or a survey project. It’s a simple record of whether the behavior is showing up more often than it did.
Leading versus lagging indicators
To run development like a system, sort your metrics into three buckets and weight them correctly.
| Indicator Type | What it Measures | Example |
|---|---|---|
| Lagging (outcome) | Results that arrive after behavior has already changed | Retention, promotion readiness, performance rating |
| Leading (behavior) | The behavior change itself, in near real time | Frequency of observed target behaviors, IDP milestone hit rate |
| Activity (vanity) | Effort and exposure, not change | Completion rate, attendance, quiz score |
Leading, lagging, and vanity indicators: completion rate is the vanity metric. Base program decisions on leading indicators, because they move first and tell you whether the lagging outcomes will follow.
Run the measurement on a steady cadence: IDP milestone reviews at 30/60/90, a manager observation log updated two to three times a month, and a quarterly team rollup so HR can see patterns across managers. If you want a structure that ties all of this into a single measurement view, our L&D strategy framework maps the indicators to decisions.
How AI coaching fills the gap between training events
Step back from the weekly cadence for a moment and look at the shape of the problem. Formal training is episodic. Behavior change is continuous. That mismatch is structural, and no amount of better courses fixes it.
The gap formal training can’t fill
Training happens on a calendar. Decay happens daily. Managers coach weekly or biweekly at best, which means there’s always a stretch of days where a skill is fading and nobody is there to reinforce it. The Tuesday afternoon when an employee has to handle a tense conversation is the moment that decides whether the training mattered, and it almost never lines up with a scheduled coaching slot.
What Merlin does in Slack and Teams
Merlin lives natively in Slack and Microsoft Teams, not in a separate app someone has to remember to open. When an employee hits a hard delegation call, a feedback moment, or a difficult conversation, they can ask Merlin right there, and the guidance is grounded in their own development goal. Merlin covers 83 skills, including the people skills that show up in most IDPs. Manager cadence plus Merlin gives you full 70-20-10 coverage: the manager runs the 20%, formal training handles the 10%, and Merlin activates the 70% in the flow of daily work.
What this means for HR and L&D program design
You don’t replace your existing programs. You add the daily layer that was always missing. The workshops, the LMS, the IDPs all stay. Merlin fills the space between them, which is where development quietly dies in most companies. That’s how you start closing the gap Gallup measured, the one where only 30% of employees feel someone at work encourages their development, without adding a single line of headcount.
Build the system, not just the program
Training rarely fails on content. It fails on the reinforcement system that was never built. The workshop happens, the forgetting curve does its work, and the skill is gone by the following week because nothing was there to catch it.
This playbook is that system: the gap analysis, the IDP, the 70-20-10 design logic, the 30-day cadence, and Level 3 measurement. Merlin fills the daily gap inside it, in the tools your people already use.
Start where the leverage is. Try Merlin free and see the daily reinforcement layer in action. If you’re an HR or L&D leader scoping this across teams, book a demo and we’ll map the cadence to your programs.