At a workshop in Gurgaon last year, a manager in his fifties described his team in three categories: the ones who wanted a promotion in eighteen months, the ones who wanted to be left alone, and the ones who asked why the work mattered. Then he paused and said the third category included two people older than him. The room laughed, because everyone recognised the error. He had been describing life stage and temperament, and calling it generation.
This is the usual shape of the conversation. Someone reads that millennials need constant feedback, someone else reads that they are disloyal, and a manager ends up running two versions of the same meeting for two age groups that contain the same variety of people.
The labels are a bad hypothesis
A generation label is a description of an average, applied to an individual, and the individual is who you manage. The average also shifts with the sample: a person who joined your firm at 34 to change careers has more in common with a graduate than with a colleague born in the same year who has been in the same role for a decade.
There is a second problem. When a manager believes a group needs handling, they change their behaviour towards that group, and the group responds to the handling rather than to the belief. The 26-year-old who is watched closely becomes cautious. The 48-year-old who is assumed to be settled stops asking for development. Both outcomes then get read as confirmation.
Three differences that are real
Drop the labels and something more useful appears. Three differences do show up in teams, and none of them maps cleanly onto age.
Career pace. Some people want the next role in two years and will accept discomfort to get there. Others want depth, stability, or a shorter commute. Both are legitimate, and both can appear at 24 or 54. What differs is not ambition but the trade a person is willing to make, and only the person can tell you what that is.
Feedback preference. Some people want it in the moment, plainly, in front of the team. Others want it private, considered, and in writing. Poorly delivered feedback is read as an attack regardless of age. The variable is how the person receives information, which you learn by asking and by watching what they do after a difficult conversation.
Meaning at work. Almost everyone wants their work to matter. What differs is which part: the customer, the craft, the team, the money, or the mission. A 29-year-old in a support queue may care most about the customer; a 45-year-old in finance may care most about the craft. Assuming the younger one needs purpose and the older one needs a bonus gets both wrong.
What looks like a generation gap is usually a gap between what the manager assumes and what the person has actually said.
What the labels hide
Once a team is sorted into cohorts, other explanations stop being considered. Four of them usually explain more.
| The story being told | The variable underneath | What to test |
|---|---|---|
| “The young ones want everything now” | Time in role, prior experience, cost of living | Ask each person what pace they want and why |
| “Older staff resist new systems” | Whether the system was explained or imposed | Involve two sceptics in the rollout and watch |
| “They have no loyalty” | Whether internal moves are possible | Count internal transfers in the last two years |
| “They need constant praise” | Whether anyone told them what good looks like | Set one clear standard and review against it |
The fourth row is the one managers miss most. A team that asks for frequent feedback is often a team that has never been told, in concrete terms, what a good month looks like. Uncertainty produces requests for reassurance. Remove the uncertainty and the requests drop.
What a manager can test
The alternative to a generational strategy is a short set of experiments on your own team, each cheap enough to run this month.
- Ask the question directly, once, in writing. “Over the next two years, what would you like to be doing?” and “How do you prefer to get feedback on something that went wrong?” Two lines each. The answers will not align with birth years.
- Run one project with a stated outcome instead of stated hours. If the work gets done and the person is reachable when it matters, the result tells you more about their working preference than any article.
- Change the format of one meeting. If the complaint is that younger staff do not speak up, try written comments before the discussion. If the complaint is that older staff dominate, try round-robin. Either way you are testing the meeting, not the cohort.
- Check your own distribution of stretch work. List who got the last five visible assignments. If the same two people appear, the team’s sense of who is “ready” is being set by you, not by their age.
Where the real management work sits
Most of what gets called a generational problem is a management system problem: unclear standards, no route to a next role, feedback that arrives only at appraisal time, and work assigned by habit. A team with those conditions will produce frustration in every age group, and the frustration will get labelled.
That is why the useful intervention is rarely a session on understanding millennials. It is normally a review of how work is assigned, how performance is described, and whether people can see a path. Those are jobs for the manager, not the cohort, and they respond to structure rather than sensitivity training. Our consulting work on competency and role design usually starts here, and a training solution for managers is worth running only once the expectations are clear enough to train against.
Two things are worth saying plainly. First, a manager who treats people as individuals will occasionally get it wrong, and that is recoverable; a manager who treats people as a category will get it wrong consistently and never find out why. Second, the differences in a team of twelve are larger within the age groups than between them, and the manager who accepts that ends up with a simpler job: ask, watch, adjust.
Start with the two questions above, this week, with everyone on the team. If the answers look like the person rather than the year they were born, the labels were never doing any work. For a wider look at what keeps people once the basics are in place, see our note on engaging and retaining employees.