You send a direct message. A colleague sends an email. You ask for a quick chat; they want an agenda. You offer feedback; they hear criticism.
It is easy to decide the other person is being disrespectful, rigid, or difficult.
Sometimes age, experience, role, or familiarity with a tool may shape how someone prefers to communicate. But a mismatch does not explain itself. And it does not automatically tell you anything about the other person’s work ethic.
The trouble often starts when you mistake your own workplace norms for neutral standards everyone should already understand.
You may think a direct message is efficient. Someone else may see an email as clearer or easier to refer back to. You may think a quick conversation saves time; a colleague may want an agenda so they can prepare. Neither preference is automatically more professional.
But if your expectations stay unspoken, the difference gets interpreted as character.
“They never respond.”
“They are making this harder than it needs to be.”
“They do not respect my time.”
Now you are arguing about the person when the actual disagreement may be about what the work requires.
This is one reason generational explanations can be tempting. They offer a tidy answer: people from different age groups communicate differently, so each side needs to adjust. There may be real differences in experience or familiarity with particular tools. But age alone cannot tell you why this colleague wants an agenda or why that colleague prefers a quick conversation.
Ask what the practice is meant to accomplish.
Does the agenda help someone prepare? Does the message need a record? Is the quick chat genuinely quicker, or does it create follow-up that could have been avoided? What kind of feedback will make the expectation clear without turning it into a judgment of the person?
Those questions move the conversation from “your style is wrong” to “what will help us do this well?”
That does not mean every preference has to become a team rule. Teams need shared expectations. The point is to choose them deliberately, based on the work, rather than treating the loudest or oldest habit as the obvious default.
A leader can make that easier by naming the norm instead of assuming it. Say when a quick conversation is appropriate, when a written record matters, and what useful feedback should include. Then ask where the expectation is creating friction.
You may discover that the standard you considered obvious was only familiar to you.
That can be uncomfortable. If someone’s different approach feels like disrespect, pause before making it a verdict. You may be defending a useful standard. You may also be defending a preference you have never had to explain.
The goal is not to make everyone communicate the same way. It is to make sure people understand what the work requires, why the team has chosen its norms, and where there is room to do things differently.
Before you call a communication mismatch a generational problem, name the expectation. Then ask whether it serves the work—or simply feels like professionalism because it is the way you learned to do it.
If this hit something real, The Self Aware Leader goes deeper every week. Subscribe free at jasonrigby.substack.com.
