Notes on understanding today's generation · Finding shared understanding at work
How to turn a junior colleague's “Why?” into a conversation
A question about the reason can sound like pushback. Distinguish a question about the task's purpose from uncomfortable wording, and align the results you expect.
Look for the information needed behind the question
A senior colleague says, “Please reorganize this material,” and a junior colleague asks, “Why?” The senior colleague may hear refusal, while the junior colleague may want to know what to change. Neither has yet heard the background to the other's question.
First clarify: “Are you asking why this is needed, or is the organization standard unclear?” If understanding the purpose is necessary to choose what to include, explaining the reason can also improve the actual result.
Welcoming questions does not mean accepting every way of expressing them. If the wording bothered you, separate content from delivery: “Questions are welcome. It's easier to answer if you tell me specifically what you're wondering about.”
Four things to include in a work request
- Purpose: Explain whose decision the material supports and what that decision is. For example: “The team lead wants to compare reasons for delays across clients.”
- Deliverable: Set the required fields, length, and format. You could say, “Put the client, scheduled date, and actual completion date in one table.”
- Deadline and priority: Confirm when it is needed and what comes first if it overlaps with existing work. Say whether the schedule can be adjusted if it is difficult.
- Scope for independent decisions: Distinguish what they may decide themselves from what requires advance confirmation. For example, the format is flexible, but it must be checked before being sent to the client.
If senior and junior colleagues each change one sentence
Senior colleague: “We want to compare delay causes in Friday's meeting. We need one table by 3 on Thursday. Does this overlap with the tally you're already working on?”
Junior colleague: “I understand the purpose. Should I include reasons for each case or group them by client? Could I move the tally I'm doing to Friday morning?”
In this example, questions help set the work's scope and priorities. The junior colleague first states what they understand and makes the remaining questions specific; the senior colleague explains how the deliverable will be used.
If there is no time for a long explanation, set a separate check-in. Distinguish what can be done now from what needs confirmation: “I'm in a client meeting now. Let's align for five minutes at 2. Before then, please just gather the original files.”
Talk about this task instead of “young people these days”
In feedback, describe observable behavior rather than age. “People these days lack responsibility” makes it hard to know what to change next. “The meeting materials were delayed because I didn't receive an update by the 3 p.m. deadline we agreed yesterday” clearly identifies the issue.
Then agree on the next action: “Let's decide when and how you'll let us know if a deadline becomes difficult to meet.” Junior colleagues can likewise reflect on what they did not know and when they should have asked rather than ending with “You didn't explain it.”
This article suggests finding the missing information in this task and one action to change next time, instead of trying to explain each other's age groups.
How this was written: This conversation guide is based on situations that can arise between parents and adult children or senior and junior colleagues at work. Every example is fictional and does not represent research explaining a particular age group's personality or actual inner thoughts. Use it to ask directly about each other's preferences. Report an error or contact us