TL;DR:
Ask for where something is and how to do it in the program you have open, not in general.
Being shown on your own screen beats a written list of menu steps that may not match your version.
Do each step yourself, so the location sticks.
Opening a new program for the first time can feel like stepping into a cockpit. There are panels, icons, menus, and none of it has your name on it. Most people cope by clicking around until something works. An assistant that can see your screen offers a better way: ask, get shown, and do it yourself.
The example here is a photo editor, but the approach works for a video tool, a design app or a spreadsheet.
Why written instructions fall short
Instructions from a web page say things like "open the Adjust panel and drag the Exposure slider". That is fine if your version has the same layout. Programs change, menus move, and labels differ between versions and between Mac, Windows and Linux. The result is a lot of "I cannot find that button".
A helper that looks at your actual window can say "the slider is in the panel on your right, near the top" and point at it. Same goal, but tied to what you see.
Walk-through: finding a setting in a photo editor
Your photo came out too dark and you want to brighten it. You have never used this editor before.
Say what you want: "I want to make this photo brighter. Where do I do that?" You name the goal, not a feature, because you do not know the feature's name.
It names the idea: The answer: this is usually called an exposure or brightness adjustment. That gives you words to look for in any editor.
It shows you where: On your screen, it points to the panel or menu where that adjustment lives in your version of the program.
You do it: You drag the slider a little and watch the photo change. You also notice a neighbouring slider for contrast.
You learn the neighbours: "What does that one do?" It explains that contrast changes the gap between light and dark areas. You try it and undo it.
You note the undo: Before you leave, you ask "how do I undo?" and learn the shortcut for your system.
In a few minutes you did the task, learned the vocabulary, and discovered where the adjustments live. Next time you will not need to ask.
Questions that work well
"Where do I find ... ?" when you know what you want but not where it is.
"What is this button for?" while pointing at it.
"What is this called?" when you can describe it but not name it.
"Is there a faster way?" once you can do it the slow way.
"How do I undo or go back?" before you experiment.
Learn the vocabulary as you go
Every program has its own words for the same few ideas: layers, panels, tools, filters, exports. Each time the assistant names something, write the name down or say it back. A short personal list of ten terms is often the difference between searching the help pages successfully and not knowing what to type.
It also helps to learn how the program groups its features. Most keep the tools you use while working in one place and the settings for the whole file in another. Knowing that rule of thumb makes the next unfamiliar program less daunting.
Keep your hands on the controls
The learning is in doing. If the assistant does the click for you every time, you will keep asking. If it shows you and you click, your hands learn the path. Ask for the path, not the result, unless you only need the result once.
Tip: Work on a copy of your file while you learn. That makes experiments safe, and you can always go back to the original.
What to watch for
Assistants can be wrong about a specific program, especially a newer or less common one, or a recent version. If the button it names is not where it said, tell it what you see instead. The correction helps it find the right answer, and the program's own help menu is a good second source.
Be careful with anything that changes or deletes many files at once, such as batch edits or exports to a folder that already has your originals. Look before you confirm.
Privacy and control
Your editor window may show private photos or file names. DuckyHelper looks at your screen only while the pill is open and for that answer, so close or hide anything you would rather not share before you ask. On a Mac the key is fn, and on Windows and Linux it is Ctrl+Shift+Space.
Try it yourself
Open a program you have been avoiding. Pick one small thing you want to do, ask where it is, and do it. Then ask what the three nearest controls do. In ten minutes you will know more about its layout than from an hour of clicking around.
Frequently asked questions
Will it work for any program?
Whatever is visible on your screen it can look at, though common programs are familiar to it and rare ones less so. If an answer does not fit what you see, describe your screen to it.
Is it better than a video tutorial?
They complement each other. A video teaches a whole workflow, while an assistant answers the small question you have right now.
What if my version looks different from what it describes?
Tell it what you see and ask again. It can adjust to your actual window.
Get started
