In your team, a 58-year-old engineer sits next to a 26-year-old project manager. He has been with the company for twenty years, knows every process, every client, and every shortcut. She has been there for eight months, prefers to work remotely, questions processes, and asks about the purpose behind tasks that he has never questioned. He finds her exhausting. She finds him resistant to change. Both are right. And both are wrong.
Generational conflicts are rarely true conflicts of values. Most often, they are differing expectations regarding communication, feedback, and work design. Those who understand this do not lead four groups, but one team.
A CEO I advised faced exactly this problem. His development team was split: the experienced engineers perceived their younger colleagues as erratic and demanding, while the younger ones saw the older ones as blocking progress and being overly hierarchical. In truth, both wanted the same thing: to do good work. But they had fundamentally different ideas of what good work looks like, how collaboration works, and what makes a good manager.
An important principle first: experience is not measured in years of service, but in adaptability. A 50-year-old can have the most agile mindset in the room, while a 25-year-old has the most rigid. No generation is right. None is wrong. Each has good reasons for its expectations. Three levers help to combine these differences productively.
Most generational conflicts arise because expectations remain implicit. And expectations are so different because the formative experiences are: people who entered professional life in the 1980s and 1990s experienced a world where loyalty was rewarded and a career meant staying for a long time. People entering in the 2020s have seen loyal employees lose their jobs in restructuring and expect meaningful work and development instead of lifelong employment. The experienced employee expects problems to be resolved in a personal conversation. The young colleague expects everything to be documented in a shared tool. No one talks about it; both are frustrated.
In practice, this manifests in five areas of tension: in communication, where some prefer a phone call and others prefer chat. In feedback, where annual performance reviews meet the expectation of continuous feedback. In work location and hours, where presence is interpreted as commitment, while others think purely in terms of results. In career and development, where hierarchical advancement meets the desire for specialized expertise and project variety. And in dealing with authority, where the focus on the “what” and “how” meets the “why,” as younger employees want to understand first before they implement.
| Area of tension | Older expectation | Younger expectation |
|---|---|---|
| Communication | Personal conversation, telephone | Chat, asynchronous, documented |
| Feedback | Annual, formal | Continuous, timely |
| Work location | Presence = commitment | Results count, not location |
| Career | Hierarchical advancement | Projects, learning, depth of expertise |
| Authority | Position decides | First the why, then the what |
Your job as a manager is not to prescribe one channel or one model for everyone. Your job is to clarify with the team how collaboration should work. Which meetings take place in person? How quickly should messages be responded to? When is availability expected? These rules of the game must be co-created by the team, not decreed from above.
Experienced employees have knowledge that isn’t in any manual: client relationships, informal networks, the understanding of why certain things are the way they are. Younger employees bring fresh perspectives, technological competence, and a willingness to question the status quo. Both are valuable. The question is whether you create situations in which this knowledge flows in both directions.
A division head I supported during the reorganization of a mixed team introduced reverse mentoring: not only did the experienced colleague coach the younger one in client contact, but the younger colleague coached the experienced one in digital working methods. This broke down entrenched hierarchies and created mutual respect based on competence rather than years of service.
As Amy Edmondson shows in her research on team learning: teams that learn from each other need psychological safety—the certainty that one will not be shamed for a question or a mistake. In generationally mixed teams, this safety is particularly fragile because older members fear being perceived as obsolete, and younger members fear being labeled as immature. Consciously create situations where both sides can contribute: mixed project teams, joint problem-solving, targeted tandems for new tasks.
One topic deserves special attention: the transfer of experiential knowledge. In the coming years, the baby boomer generations in many organizations will retire. With them goes knowledge that is not stored in databases. Identify the critical knowledge holders in your area and create opportunities for transfer—not through documentation projects that no one reads, but through collaborative work.
The most common leadership mistake in mixed teams: treating everyone the same and considering that fair. A 55-year-old specialist with thirty years of experience needs a different feedback format than a career starter. Fairness does not mean equal treatment. It means leading everyone in the way they need to perform at their best.
The second mistake is just as common: using generational clichés as an explanation. “The young people only want work-life balance” or “The older ones are just no longer ready for change.” Such phrases are convenient because they provide simple explanations. They are also wrong because they reduce individual people to stereotypes. There are 25-year-olds who love overtime and 55-year-olds who are enthusiastic about learning new technologies. Lead people, not generations. But understand the formative experiences people bring as a starting point, not as a pigeonhole.
And do not ignore the tensions. If the experienced colleague is frustrated because the young colleague works from home while he comes into the office every day, it won’t be resolved by looking away. It is resolved through a conversation in which you acknowledge both perspectives and find a solution together.
First: Do you know the specific expectations of your various team members regarding communication, feedback, and work design, or are you just guessing? If you are guessing, conduct three individual meetings this week and ask.
Second: Is there a situation in your team where knowledge specifically flows in both directions, where older colleagues learn from younger ones and vice versa? If not, start a tandem for the next suitable task.
Third: What experiential knowledge will your team lose when the most experienced employees retire in the next few years? Name the people and the knowledge. If you cannot name it, it is time to start.
Generational diversity in your team will not decrease. It will increase. You can treat this as a problem or as a leadership task. A team where everyone thinks the same makes quick decisions but overlooks blind spots. Generational diversity is demanding, but it is a competitive advantage.
The best teams do not consist of people who think alike. They consist of people who think differently but have learned to use this diversity productively. This doesn’t happen on its own. It happens through leadership.
Feedback that lands – Why annual reviews are not enough and how continuous feedback bridges generational boundaries.
Developing talent – Building stretch assignments and successors only works if you know the different development needs.
All Insights can be found in the overview.
Proven tools and models for self-application are available under Solutions.
If you want to take these thoughts further for your company, a no-obligation initial conversation is worthwhile.
