Last week, I watched a 28-year-old engineer explain Slack workflows to a 52-year-old project manager who kept insisting email was faster. Twenty minutes in, they weren’t even arguing about tools anymore—they were arguing about respect, pace, and what “professional” meant. The junior engineer thought the PM was stuck in the past. The PM thought the engineer had no patience for process.
They were both right. And both missing the point.
After over a decade of team performance work, I’ve noticed something counterintuitive: the teams crushing their goals right now aren’t the ones who’ve eliminated generational tension. They’re the ones who stopped pretending it didn’t exist.
The conversation everyone’s avoiding
Here’s what happens in most teams. Someone makes a generational joke—”OK Boomer” or “typical millennial”—and everyone laughs nervously. Then they go back to their desks and silently fume about how their colleague “doesn’t get it.”
I used to work as a trainer for high performers who looked composed but ran on anxiety internally. The generational stuff? It ate at them constantly. The 25-year-old who felt dismissed as “just another entitled Gen Z.” The 45-year-old who sensed younger colleagues rolling their eyes when she referenced pre-digital processes.
These weren’t small irritations. They were daily friction points that shaped every interaction.
Alex Shubat, former Forbes Councils member, puts it bluntly: “In my experience, unchallenged generational stereotypes fuel workplace friction.”
The keyword there? Unchallenged.
Most teams treat generational differences like weather—something to complain about but never actually address. Meanwhile, those stereotypes calcify into resentment. The senior employee who prefers phone calls gets labeled a technophobe. The junior employee who wants flexible hours gets tagged as uncommitted.
Nobody wins this game.
What actually happens when teams talk about it
Six months ago, I observed a tech startup that decided to run an experiment. Instead of another team-building exercise, they held what they called “friction sessions”—structured conversations about generational assumptions.
The rules were simple: Share an assumption you hold about another generation. Then share one about your own generation that frustrates you.
The 58-year-old CTO went first: “I assume younger employees will job-hop the moment things get hard. But I hate when people assume I can’t learn new tech.”
A 26-year-old developer followed: “I assume older colleagues will shoot down new ideas. But I’m tired of people thinking I need constant praise.”
Within ten minutes, the room shifted. People weren’t defending their generation anymore. They were acknowledging patterns—and exceptions to those patterns.
Here’s what struck me: Once they named the friction, it lost its power. The assumptions didn’t disappear, but they became discussable. When the CTO later resisted a new tool, the team could ask directly: “Is this about the tool itself, or are we falling into our old pattern?”
The real cost of avoiding the friction
I’ve watched teams waste months on problems that boiled down to generational miscommunication. A healthcare startup nearly imploded because senior leaders interpreted quick Slack messages as disrespectful while younger employees saw formal emails as passive-aggressive.
Neither side was wrong about their preferences. But by not talking about it, they created an environment where every message became a minefield.
Think about your own team. How many conflicts that seem to be about “process” or “communication style” are actually about generational expectations? How many times have you thought “they just don’t understand how things work now” or “they have no respect for experience”?
These unspoken tensions don’t just create bad vibes. They sabotage actual work. Projects stall because people interpret silence differently across generations. Innovations die because younger employees don’t feel heard and senior employees don’t feel valued.
The friction is already there. The only question is whether you’ll use it or let it use you.
How to make friction productive
Start small. You don’t need a company-wide initiative. Pick one recurring tension point and get specific about it.
I worked with a team where video call etiquette was a constant source of irritation. Younger employees kept cameras off to multitask. Older employees saw this as disengagement. Instead of making a blanket policy, they talked about it. Turns out, the younger employees weren’t disengaged—they were anxious about their home setups. The older employees weren’t controlling—they missed visual cues that helped them communicate.
The solution? Camera optional for routine updates, cameras on for brainstorming or difficult conversations. Not perfect, but workable because everyone understood the why behind different preferences.
Another approach: reverse mentoring with actual teeth. Not the token “teach me TikTok” version, but structured sessions where different generations share their problem-solving approaches. A 24-year-old teaching a 50-year-old about AI tools while the 50-year-old shares negotiation tactics from twenty years of client management.
The key is making these exchanges explicit and valued, not casual watercooler moments that may never happen.
Why addressing friction beats avoiding it
Teams that talk about generational friction develop a superpower: they can separate identity from behavior. When someone sends a formal email, it’s not automatically “because they’re a Boomer.” When someone wants instant feedback, it’s not automatically “because they’re Gen Z.”
This distinction matters. Once you stop assuming every behavior stems from someone’s birth year, you can actually problem-solve. Maybe the formal email writer values documentation. Maybe the feedback seeker is managing anxiety. These are workable challenges, not immutable generational traits.
I’ve seen teams transform simply by adding one question to their retrospectives: “Did generational assumptions affect this project?” Not to assign blame, but to surface patterns.
One engineering team discovered their code reviews were suffering because senior developers gave feedback differently than younger developers expected it. Seniors saw detailed critiques as mentoring. Juniors saw them as micromanagement. Once they named this, they could design a review process that worked for everyone—brief comments for minor issues, detailed discussions for teaching moments.
Bottom line
The most effective teams right now aren’t generational utopias where everyone thinks alike. They’re groups of people who’ve decided that pretending differences don’t exist is more exhausting than addressing them head-on.
Your next step isn’t complicated. Pick the generational assumption that most irritates you about your team. Then ask someone from that generation if it’s accurate. Not accusingly—genuinely curious. “I’ve noticed X pattern and wondered if that matches your experience.”
Half the time, you’ll be wrong about the cause. The other half, you’ll be right but discover there’s a reason behind it you hadn’t considered.
Either way, you’ve started the conversation that most teams are still avoiding. And that conversation—messy as it might be—is what separates teams that struggle with friction from teams that harness it.
The friction isn’t going away. But once you start talking about it, it stops controlling the conversation.
