When people on the same team disagree about boundaries, feedback, or process, it is tempting to call it a generational problem.
That label can feel like an explanation. Often, it is a way to stop asking questions.
One employee leaves at the end of the workday while a colleague stays to finish. Someone asks why a process exists before following it. Direct feedback lands as unnecessarily harsh. A manager hears resistance where an employee hears a reasonable request for context.
Age and career stage can shape what people expect from work. Experience with a particular system, authority, or job insecurity may matter. And sometimes the problem is not a misunderstanding: someone has missed a commitment, and the team is paying for it.
But “they’re from a different generation” does not tell you which is happening.
It turns a dispute about conduct into a judgment about character. One person becomes lazy. Another becomes rigid. Once those labels take hold, the team stops examining the actual disagreement.
What was expected? Was it explicit? What does the work require? What is the impact when someone does something different?
Those questions are less satisfying than a story about work ethic. They are also more useful.
A process may protect quality, reduce risk, or help people coordinate. It may also be a habit nobody has revisited. A request for flexibility may be workable, or it may leave a colleague carrying an unfair share. Asking for the reason behind an assignment can improve the work; it does not automatically excuse ignoring it.
Neither age nor tradition settles the argument. The work does.
As a leader, your job is not to make every person prefer the same style. It is to make the standard clear enough that differences in style do not become confusion about responsibility.
Say what outcome is required. Explain why a process matters, if it does. Be specific about where people have room to choose their approach. When a commitment is missed, address the missed commitment and its impact—not a theory about what an entire age group believes.
This can require changing a rule. It can also require holding someone to one.
The uncomfortable part is that you may have to defend the reason for a standard you inherited. “That’s how we do it” is not a reason. If the rule is necessary, make the case. If you cannot, be willing to reconsider it.
And if someone pushes back, do not rush to call the pushback entitlement or disrespect. Get precise. What are they objecting to? What are they asking for? What would happen to the work if you said yes?
That does not mean every objection deserves a change. It means you should know what you are saying no to.
Generational labels make it easy to decide who is the problem before you understand what the problem is. A team can lose time to unclear expectations, strained collaboration, or people quietly withdrawing while everyone argues about attitude.
So when the room divides over a rule, ask what the rule is for—and who bears the cost of keeping it.
You may find that someone needs to change their behavior. You may find that the rule needs to change. Sometimes you will find both.
Do not let a label make that decision for you.
If this raised a question for you, The Self Aware Leader goes deeper every week. Subscribe free at jasonrigby.substack.com.
