Training and development: 9 things companies must finally change

I'll start this article with a question you probably hear regularly — usually in a meeting with the business, usually at the worst possible moment. "Hmm, what did we actually get out of all that training?"

What do you do then? You probably open a report from your training platform, show the number of completions, the percentage of plan execution, maybe an attendance chart. The business nods, and an awkward silence sets in. Nobody is happy — not you, not them. Everyone knows that's not actually an answer to the question. It's an activity stat, not proof of value from your development programs.

If any of this sounds familiar, this piece is for you. Not to reassure you that "it's a tough subject and everyone's dealing with it." To say it plainly: the way most companies approach training and employee development is fundamentally broken. And switching tools won't fix it.

Below you'll find nine things that need to change — not next year, not "as part of the next L&D strategy," but now.

1. Stop measuring course completions

Completion rate is one of the most damaging metrics in training and development. Not because it's bad in itself, but because it became the goal instead of just a signal. When you measure whether an employee clicked "complete," you're measuring activity. Not learning. Not behavior change. Not business impact.

Picture this: the head of sales asks you, "Are our reps selling more after that training?" — and you answer, "92% of them finished the course." That isn't an answer to the question, but it's the only answer you have.

The problem is that the entire ecosystem of traditional LMS systems was built around exactly this metric. Their operating model is course → completion → report. The platform delivers a course, the employee "passes" it, the system generates a report. Process closed. Success logged. Except, from a business perspective, nothing actually changed.

How do you change that?

Measure what actually matters: knowledge retention after a week, two weeks, a month. Measure whether what people learned in training is being applied in practice. Connect development data with operational data — like customer service quality, error rates in processes, ramp-up time for new hires, or individual and team goal attainment. That's the conversation the business wants to have.

2. Training is an event. Learning is a completely different process

The classic approach to training assumes learning looks roughly like this: an employee gets an invitation to a training session, attends the session, comes back from the session, and — somehow, magically — does something differently from that point forward. It's a model that may have worked in the 1990s, when work was linear, roles were stable, and knowledge changed slowly.

Today, the reality is different. Job roles evolve faster than ever. Skills go out of date in months, not years. People learn when they need to solve a real problem — not when they have a course scheduled. The brain just works that way: information absorbed in the context of a real task sticks. Information absorbed in advance, "because we planned the program that way," is forgotten within days.

Learning is a continuous process. It starts before any formal training — in onboarding, in the first weeks on the job, when a new hire absorbs work standards and tries to understand what "good work" actually means in this specific role and this specific organization. It runs alongside everyday work as knowledge available when it's needed. It's reinforced by practice, manager and peer input, and regular exposure to the material. And it evolves as roles, teams, and goals change.

A company that treats training as a one-time event with a clear start and end isn't building competencies. It's building a catalog of completed line items.

3. One program for everyone is a recipe for a wasted budget

Recently rolled out a big training program for sales? Great. So how does that program differ for a rep with a year of experience versus a newly hired manager taking over a team?

The answer that usually comes back lands somewhere between "Not at all" and "We have a shared course catalog and the paths only differ in nuance."

This is a real problem. Not because the paths are bad, but because they assume every employee has similar needs, similar skill gaps, and a similar work context. In reality, every person operates on a different team, hits different goals, has different baseline skills, and faces completely different challenges. A rep handling enterprise customers needs different support than one selling mass-market products. A manager mid-restructure has different priorities than a manager building a new team from scratch.

A unified training program is the illusion of effectiveness. It looks impressive — big, polished rollout, everyone took the same courses, you can show it in a deck. But what does it look like from the perspective of a single employee? They get content that half-doesn't apply to their situation, doesn't answer the questions they're wrestling with, and doesn't help them in the here and now. Instead of helping with their work, it gets in the way — pulling them away from the things they're actually measured on.

A modern approach to L&D must be hyper-personalized — and this isn't just about letting an employee pick a course from a catalog. It's about deeper fit: development tied to role and career stage, knowledge served when it's needed in the context of current work, paths built on actual skill gaps rather than a generic model. That level of personalization requires a different approach to development content: it should be short and high-density, and there should be a lot of it — that's what lets you build individualized combinations matched to the needs of single employees.

Gamfi People Platform approaches it from exactly this angle: development paths are built for specific roles and tied to what a given person actually needs to do their job better.

4. Knowledge evaporates. If you don't practice it, you lose it

Most of what employees "learned" in a training session three weeks ago is already out of reach. That's not opinion — it's neuroscience. Ebbinghaus's forgetting curve shows that without review we lose up to 80% of new information within days. A one-off test at the end of a course doesn't change this — at most it checks short-term memory, not durable knowledge.

And yet the vast majority of training programs are designed exactly this way: course, test, certificate, done. L&D closes out the topic in the system and moves on to the next one. In the background, the employee returns to their job and within a few weeks doesn't remember most of what was in the training.

What works? Regular reviews spaced over time, and practical tasks anchored in the context of everyday work. Not more courses, but short, engaging knowledge-check sessions — ones the employee comes back to because they want to, not because they got another reminder from the system.

In Gamfi People Platform, alongside knowledge tests and quizzes, we introduced knowledge duels — where an employee goes head-to-head with a colleague from the organization. The opponent is automatically matched by the system; alternatively, an employee can challenge someone to a duel themselves. The system generates questions from the training paths and walks both sides through the same question set. Knowledge wins, not time spent on a course. In a few minutes a day you can go through several similar duels, getting real-time input on the mistakes you make and on your knowledge level — your own and that of your colleagues.

5. A completed course ≠ an acquired skill. They're not the same and everyone knows it

Reading a slide doesn't make someone better at handling a customer. Watching a video about tough conversations doesn't make someone better at having tough conversations. Passing a project management course doesn't mean the project will land on time.

This sounds like a truism — and it is one. The problem is that the entire reporting system in classic LMS platforms is built on the assumption that if an employee "passed" a course, the goal has been achieved. The status flips from "incomplete" to "complete" and that's the end of the story.

A skill isn't knowledge. A skill is knowledge applied in practice, validated in real situations, and reinforced through repeated action. That's why the most effective development programs don't stop at a test — they include implementation tasks: something the employee actually does in their real job, confirmed either by themselves or by their manager. Not "I'll say I know it now," but "I did it, here's the proof."

This is a fundamental shift in how to think about L&D: from delivering content to designing experiences that actually change behavior. And yes — it takes a bit more work to design. But it also delivers something a catalog of completions never will: credible proof that the training mattered.

6. L&D is stuck in firefighting mode. Time to change that

Out of nowhere it turns out you have an audit in a week and… you're stuck. You check, and 140 employees have expired data-privacy certifications. You sit down and send reminder emails to retake the training. Half the people don't react. You call the managers. The managers say "it's a busy period right now." Pressure comes from above. You stay late and manually track who's done what, nudging the holdouts.

You probably know this from personal experience. You know what's most frustrating about it? Not the audit itself — it's that this same scenario, focused on catching up on backlog, repeats regularly. And that while you're chasing the backlog, you're not doing anything strategic. You're not analyzing skill gaps. You're not designing new programs. You're not talking with managers about what their teams actually need.

L&D teams shouldn't be certification-collection departments. They should be architects of the environment that lets people work effectively — and that's a completely different role. It demands time, attention, and data. And if you're spending half your time manually chasing who hasn't opened the link to the safety training, you simply don't have that time.

Automating mandatory processes isn't a luxury — it's the condition for L&D to do something valuable. When the system itself watches certification expiry dates, sends reminders, and generates an audit-ready report, you can finally focus on what's central to your role.

In Gamfi People Platform, mandatory training runs automatically: the system tracks certification validity, sends reminders at the right time, assigns the renewal to the employee with no manual intervention, and the day before an audit generates a report with full history and e-signature confirmation. That kind of automation frees up significant resources for the work that actually creates value. Note: examples reflect common compliance frameworks; specific regulations vary by jurisdiction.

7. Training has to reach every employee — not just the office crowd

How many companies roll out new procedures through a training platform and assume everyone has read them, because the link was sent? And then it turns out company VPN access only works from the office. Or people work shift schedules and haven't logged into any system for a week.

This isn't a marginal issue. A large share of the workforce works outside the office: in stores, on production lines, in logistics, in the field. These employees have just as much right to good onboarding, up-to-date knowledge, and access to training as their office colleagues. And often it's exactly these people who are the first line of customer contact, sitting in the area where the skill gap hurts the most.

Training on a phone, accessible without VPN and without complicated login, in the format of a four-minute module that someone can get through between shifts — that's not a tech fad. It's basic equity of access to knowledge inside an organization. And that's the direction modern platforms have to move, leaning on mobile-first and microlearning instead of hour-long sessions at a laptop.

8. Building a course shouldn't take weeks

You're looking at a new 40-page customer service procedure. It's part of a broader change to service standards. The new approach has to be communicated to an entire 500-person department in a distributed structure and rolled out so everyone is operating by the new rules. How long does it take you to turn that procedure into a course people will actually go through?

If you use a traditional, LMS-based approach, you typically brief an agency, wait several weeks for content production, adjust another draft, upload to the system, and organize the rollout. The budget runs into the tens of thousands of dollars. From decision to finished course: four, six, eight weeks. And in two months, the procedure changes again.

This isn't a criticism of the agencies — it's a criticism of the system that assumes producing training content requires an external studio. It doesn't have to be that way. Today, AI-powered tools let you build engaging courses — with narration, graphics, and quizzes — directly from a PDF document, a PowerPoint deck, or a video recording. Training material can be ready in a few hours, not weeks. Question banks for review can also be generated by AI with no additional work on the L&D side.

That changes more than just speed of work — it changes the whole philosophy: knowledge stops being something to "produce" and becomes something living, growing with the organization. L&D stops being a bottleneck in the flow of knowledge.

9. Training tools live their own life, disconnected from the rest of the company

This may be the most important point — and the hardest to address, because it requires systems thinking, not a fix to one element.

In most organizations, onboarding happens in one tool, training in another, communication in a third, goal management in a fourth, and reviews and performance assessments in yet another. Each of these tools operates with its own logic, collects its own data, and generates its own reports. The employee bounces between systems. The manager doesn't get one view of what their team knows, what they're missing, and how that translates to results. L&D can't connect training data with operational data, because they live in different places.

The effect? Data is fragmented, the employee experience is inconsistent, and L&D remains an "island" in the organization — something that happens next to everyday work, rather than alongside it.

Swapping one LMS for another LMS won't solve this. Because the problem isn't the quality of the tool — it's the underlying assumption that people development can be handled by a single, specialized, isolated system. Organizations are increasingly looking for platforms that connect the dots: where training isn't a separate process but a part of a larger system in which development, goals, onboarding, performance input, and communication form a coherent environment.

Gamfi People Platform works on exactly this logic: the Learning & Development module is part of a platform that covers the whole employee lifecycle. L&D data is connected with operational data and goals. Managers see in one place the progress of their team's Academy, skill gaps, and how development activities translate to KPIs. L&D can show the leadership team not a slide with completion rate, but a report linking the investment in development with business outcomes.

This isn't a utopian vision of the future. It's the direction companies that want to take L&D seriously must move in.

To wrap up: why changing the tool isn't enough

If I still have your attention, there's a good chance that at least a few of these points hit something you're wrestling with. And you've probably had the thought that the fix is simpler than it seems: swap the LMS, roll out a new platform, clean up the course catalog.

That's exactly where the trap lies. Many organizations decide to switch systems in the hope that a new tool will bring real improvement. At first there's a freshness effect — better interface, new features, team enthusiasm. A few months later the same questions come back from the business: where's the value? Why didn't results improve? Why does L&D still not have the data the leadership team wants to see?

Because swapping one point system for another doesn't change the underlying architecture. Training is still separated from everyday work. Learning is still treated as a one-time event. You still measure activity instead of outcomes.

Real change starts not with the tool but with how you think: about what training is for, what should be measured, how knowledge should be embedded in daily work, and how L&D should be perceived in the organization. The tool matters — but it's secondary to that shift in thinking.

If you feel your current LMS isn't meeting expectations and isn't delivering the value you want to show the leadership team — it's worth checking whether the problem is the tool or the approach. And it's worth checking before you commit to another implementation.

‍

‍