Reverse Mentoring

Someone asked you to show him Slack. Or the company runs a formal program and you two were matched. Either way, you are younger, and you are in the teaching role. That is the part worth thinking about before you sit down with him.

What Happens

• He shows up on time, sits down, and says “okay, let’s do this”. He does not mean it.
• He asks why the old system was replaced before you have opened the app.
• He reaches for the mouse before you finish explaining the step.
• He says “I’m not really a tech person” at least once. It is both true and a preemptive excuse.
• He masters something small, then skips ahead and breaks the sequence.
• After the session, he tells a colleague it was “not as bad as I thought.”

Why It Happens

Being a beginner is uncomfortable at any age. Being a beginner in front of someone younger is harder. He has spent decades as the person who knows how things work. This role is genuinely new.

The tool is not the real issue. He is managing the feeling of being The Late Adapter: needing help with something basic. The friction in the room is about that feeling.

His standing at work matters to him. The Need for Respect is why: he built respect over years and does not want to lose it in a single session. He holds back questions because asking out loud feels like giving something away. Authority Preservation is a reflex here. He is not choosing to be difficult.

There is also a quieter worry. He wonders whether the company sees him as behind. The mentor match feels like a signal, even when it is not meant as one. Fear of Vulnerability is easy to trigger in this setup. The Self-Doubt Undercurrent does not disappear with seniority.

Underneath all of it, he wants to matter. The Need for Relevance is real for men in their fifties. A session where he knows nothing, taught by someone half his age, works against that. The setup needs to feel like an exchange.

What You Can Do

Keep it one-on-one. An audience adds pressure. He cannot show confusion without someone noticing. Book a room, close the door, just the two of you.

Pick one task and stop there. Choose something he will use tomorrow. Walk him through it once. Then ask him to try it himself while you watch. Say: “We’re going to do one thing today. By the end of this hour, you’ll be able to do it on your own.” One thing he can repeat beats ten things he watched.

Keep your hands off his keyboard. Point. He clicks. The moment you take over, he becomes a passenger. Wait ten seconds before you say anything. Give him time to find it himself.

Make it a trade. Before you start the demo, say: “You show me how you pull the client history. I’ll show you the export. Deal.” He has knowledge you do not have. Client history, how the operation really runs, the context behind the numbers. An exchange keeps his standing intact. He is a mentor too, and he needs to feel that.

Quick Tip

End every session by naming one thing for him to do alone before you meet again. “Before we meet next week, run last month’s report yourself and see how far you get.” A solo win between sessions builds more confidence than anything you explain in the room.

Let pauses happen. He will stop before clicking. Do not fill the pause with more instructions. Wait. Jumping in signals that you think he cannot manage. Ten seconds of silence is fine.

If it is a formal program, match for mutual value. Pair him with someone who genuinely wants what he knows. He can smell an assigned babysitter. The program only works if he believes the other person needs something from him in return.

See also: Patience and Step-by-Step Support