I had a conversation recently that stuck with me. Someone described how intimidating it can feel to be handed a new piece of technology—not because they’re incapable, but because of how it’s often introduced to them.
Too fast. Too little patience.
Learning to teach someone new technology well is a skill most of us were never actually taught, even though we’re expected to do it constantly—for a new hire, a parent, or a teammate adjusting to a new tool.
There is often not adequate transition time between the old and new way. Training isn’t designed for a broad range of abilities. When workforces span across generations, you have folks who grew up with technology and pick up a new application quickly, alongside many who didn’t depend on technology until well into their careers. These differences actually make your organization stronger and better able to serve diverse clients, but one place it often falls short is in technical training.
It’s usually the most capable or technically savvy team member who ends up expected to teach others. But being tech-savvy isn’t the same as being a good teacher—and that gap is easily felt. You’re left feeling slow, incapable, and learning less about the tool than you do about how impatient the person teaching you is.
Having the patience to teach others isn’t a skill everyone has or is even taught. The most important aspect of teaching isn’t having subject-matter expertise; it’s having the ability to slow down and share that knowledge without judgment, shame, or anger. As a teacher, you have the opportunity to build someone’s confidence—and the power to destroy it. Fear of failure is a significant predictor of whether someone adapts to change at all—it’s mentally easier and safer to avoid a new tool altogether than to risk investing time and still coming up short. Everyone you teach won’t require the same level of patience and detail, but a good teacher can adapt. Their goal isn’t just to check a box or get it over with, but to actually help someone feel competent and capable.
How to Be a Supportive Teacher
Whether you’re onboarding a new hire, helping a parent set up a phone, or introducing your team to a new way of doing things, the goal isn’t just to transfer information. It’s to help someone feel capable, not exposed. Here’s what that looks like in practice:
- Ask what they already know first. Don’t assume in either direction. Skip the condescension of over-explaining basics they’ve got, and the frustration of glossing over things they don’t.
- Slow down before you start, not after they’re lost. Set the pace at the very beginning—not as a correction once you notice their eyes glaze over.
- Name what you’re doing before you do it. “I’m going to click here to open settings” gives someone a map. Silently clicking through five screens does not. Pay attention to your word choices—saying “click the gear icon in the upper right corner to see settings” helps people who don’t memorize technical feature names.
- Normalize the learning curve out loud. “This part trips everyone up the first time” does more to calm nerves than any amount of technical accuracy.
- Let them drive. Watching someone else’s hands move fast is not the same as learning. A great flow to use is: I drive/you watch, then you drive/I watch. Hand over the mouse, the keyboard, or the phone.
- Check in with a real question, not a rhetorical one. “Does that make sense?” invites a polite yes. “Is there any part of that you want me to go over again?” invites the truth.
- Disarm past tech anxiety. If they’ve been burned, rushed, or shamed before, they might be overly apologetic for not knowing things. You can repair that damage right away: “There’s nothing to apologize for,” “I’m not in a rush, it’s okay,” or “Don’t worry, you’ll get the hang of it—I’m here to help.”
- Watch your tone, not just your words. A sigh, a rushed voice, or a “just” (“just click here”) can undo the safety being created.
Compassion in tech training isn’t about lowering the bar—it’s about raising your empathy. And it isn’t just a nice-to-have: psychological safety reliably predicts whether people adopt a new tool in the first place. Confidence isn’t a side effect of good teaching. It’s the mechanism that makes adoption possible. It’s about remembering that confidence is built one small, well-explained win at a time.
When someone has been made to feel inferior during a transition, their instinct is simple: self-preservation. 42% of employees have pretended to understand a new workplace tool when they actually didn’t, and 27% have avoided using one entirely out of fear of making mistakes. They won’t just avoid asking for help—they will avoid the tool, the software, or the new process altogether. They’ll stick to old workarounds, go rogue, or quietly badmouth the process to their peers. Your patience and clear, well-paced guidance can actually help people embrace change.
Every time someone learns something new without feeling small for not already knowing it, you’re not just teaching a tool—you’re building trust in the process of change itself. That trust is what makes the next transition easier than this one.
They are worth your time, I promise.
Leave a Reply