The best trainers do not point at the screen. They teach people to read it. Here is a simple method for describing software so learners can navigate on their own, long after the session ends.
One of the biggest mistakes software trainers make is saying "click here." It works in the moment, while everyone is watching your cursor. But the second the learner is on their own, the pointer is gone, and so is their confidence.
The goal of good training is not to finish today's lesson. It is to help people navigate software on their own tomorrow. That starts with how you describe the screen.
Instead of pointing, tell learners where to look using consistent directions, colors, and landmarks. Give the instruction the same way you would give someone directions to a room in a building.
"Click Settings."
"On the left side of your screen, in the navy-blue navigation panel, select Settings."
The second version does three things at once: it gives a direction (left side), a color landmark (the navy-blue panel), and the label to look for (Settings). The learner's brain now has a map, not a memory of where your mouse went.
Most people already think in terms of left, right, top, and bottom. Lean on that. Divide any screen into nine simple regions and name the one you mean. "Top right," "bottom center," "middle left." Everyone knows where those are without a pointer.
Name the region first, then the item: "In the top right, select your profile picture."
Before you teach a single task, take thirty seconds to walk the screen and name its parts. Once learners know the landmarks, every later instruction lands in a place they recognize.
Navigation menu: how you move between sections, usually down the left or across the top.
Toolbar: the row of actions and icons, usually near the top.
Search box: where you type to find things, often top center.
Work area: the big space in the middle where the real work happens.
Action buttons: Save, Add, Submit; often bottom right or top right.
Account area: your profile and settings, almost always top right.
Labels change from one app to the next, but color and shape stick in memory. When something is visually distinct, say so. "The orange button in the bottom right." "The icon that looks like a gear, that's Settings." "The magnifying glass is search."
You are giving the brain a picture to hold onto. Most people will not remember the word "configuration," but they will remember the little wheel in the corner.
Consistency is what lets a skill transfer to the next piece of software. Pick a vocabulary and stick to it, in the session and in your documentation.
When you always call it a "tab" and always call it an "icon," learners start to recognize those same parts in tools you never even trained them on. That is the real win: confidence that travels.
We train teams to navigate software with confidence, and write documentation that shows every button instead of just naming it. Tell us what your team is learning.
Book a Discovery Call →
Everything to prepare before training day, in one printable list.
Get it →
Guides that show every button, not just name it.
Explore →
See how we run a live session your team remembers.
Explore →