When you manage someone much older than you, feedback can start to sound like a request for permission.
You qualify the point. You explain it three different ways. You phrase an expectation as a question, then let it slide when the answer is vague.
You may call that respect. Sometimes it is. Sometimes you are trying to avoid finding out whether this person approves of you as their manager.
Those are different things.
An older employee may have experience you do not. They may know something about the work that changes how you should handle the issue. Age and tenure can matter to context. They do not automatically give someone veto power over your responsibility to set expectations.
The job is not to act older or louder. It is to be clear about the work and curious about what you may be missing.
Jordan manages a team that includes people with far more industry experience. One of them needed to improve the documentation for a project. Jordan had raised the issue before, but the expectation remained unclear.
Eventually, Jordan made the request specific: which documents needed attention, what the work should include, and when it was needed. The employee acknowledged the request and asked about one of the deadlines.
That exchange did not prove that age had never mattered, or that directness solves every management problem. It did show that Jordan’s prediction of inevitable resistance was not the same as evidence.
This is where younger managers can get tangled. They treat respect for someone’s experience as if it requires uncertainty about their own role. They may need the employee’s knowledge; they may also need to give feedback. Both can be true.
If you are unsure whether your concern is fair, get specific before you get forceful. What happened? What was expected? What effect did the gap have on the work? Is there context you should understand before deciding what needs to change?
Then say what you need without wrapping it in so much reassurance that the point disappears. For example: “The project notes were missing the decisions and owners we agreed to capture. That made it harder for the team to pick up the work. Going forward, please include both in the notes after each review. Is there anything about that expectation or the process I should understand?”
That is not a performance of authority. It is a clear expectation with room for relevant information.
You do not have to pretend you know as much as the person you manage. You do have to distinguish between not knowing everything and not being allowed to lead.
Notice when you soften a message because the work is genuinely ambiguous, and when you soften it because you want the other person to reassure you that you belong in the role. The first calls for better questions. The second can leave your team guessing about what matters.
Respect their experience. Ask for context. Be willing to revise your view.
And do not make their approval the price of giving feedback you are responsible for giving.
