Why good HR ideas often get stuck in seminars.
A case study from our consulting practice: We are sharing it because it often helps HR, change, and organizational development teams in similar situations, without any hero stories or consultant jargon.
The problem
The organization operates at a fast pace. Roles change quickly: requirements shift more frequently, interfaces change, teams reorganize, projects come and go. But what remains are personnel development tools from a different era.
The HR department draws a logical conclusion: the classic job description as a “fixed point” and the associated idea of developing employees along defined positions no longer reflects reality. So HR develops a new model (competence- or role-oriented, much closer to the dynamics of work) and introduces it into the organization in an internal training course.
In the first year, the mood is clear: the participants are enthusiastic. Finally, something that “fits.” The seminar runs again the following year – and again with strong feedback. In the third year, a sentence is uttered that sticks in the mind because it doesn't sound like resistance, but rather honest irritation:
“Why doesn't everyone do this if it helps us?”
The participants now realize that the approach makes sense. And they know that there are colleagues who are familiar with it and could apply it. Nevertheless, it hardly ever comes up in everyday life. The new model is present in the seminar, but not in the system.
Our hypothesis
The system would make significant progress if... the organization not only trained individual groups, but also consistently restructured the old HR control mechanisms in such a way that they compellingly support the new model or consciously end the old approach.
As long as central routines and artifacts remain unchanged, i.e., annual reviews, job descriptions, “position-to-position” development logic, forms, IT masks, and KPI logic, they send a stronger message every day than any training program: This is how we really do things here.
In this logic, qualification even becomes paradoxical: People learn a helpful approach in a seminar and then encounter processes that pull them back into the old model. This creates the impression that the new approach is “nice to have” or an HR program, but not workable in the operating system.
Our solution and intervention
The key is a change of perspective in the assignment: not “developing managers individually,” but system and organizational development.
Important here: we do not roll out the new model across the board. It is implemented specifically where the work is actually characterized by high dynamics, modern role models, and rapidly changing requirements. It is precisely in these areas that the greatest benefits arise and, at the same time, the greatest need to replace old instruments with something more suitable.
In concrete terms, this means:
- System map instead of list of measures:
- Together with a pilot group, we first identify where the old model is still present: in documents, routine discussions, rules and regulations, responsibilities, tools, and habits. Not as a question of blame, but as a diagnosis: What levers keep the old way of thinking stable?
- Alignment of all personnel development systems with the target model:
- All previous PD systems are reviewed: What can be converted to the new model? What needs to be eliminated because it works against it structurally? What needs a transitional solution?
- The core is less about “new content” and more about consistency:
- same terms, same logic, same expectations in all relevant systems.
- Rollout in waves: with managers as users, not as the target group
- The new model is not “communicated” but introduced in waves: first where there is a real need and connectivity is high. At the same time, managers are trained. Not abstractly, but in concrete new routines: How do I conduct ROLE-oriented conversations? What are the strongest sets of requirements that define the role now and in the future? How do I make development decisions? How do I use the new tools in a way that makes work easier?
- Review and adjustment after one year
- After twelve months, the model is not only “evaluated,” but also readjusted: Which elements are being used? Where are workarounds emerging? Which formulations, templates, or process steps are too difficult? This loop is important because it sends a signal: the model is not being defended, but improved.
The result
After two years, the new model has been introduced in 80% of the relevant, dynamic areas and successfully tested in application. Further feedback loops are planned – not as a “change remnant,” but as a conscious operating principle: The model should learn along with the organization.
However, the most important effect is already apparent earlier: The question “Why do I never encounter this in everyday life?” disappears because the new model no longer exists only in the seminar, but in the daily interfaces of the organization. Not because people suddenly become “more open” – but because the system stops holding them back.
And so the initial question almost becomes a rule of thumb:
If something helps in the seminar but does not appear in everyday life, it is usually not a lack of motivation, but a lack of system connection.
