Everyday Helping other people with technology
Helping an older relative with technology without taking over
What actually helps: the setup decisions worth making once, the scam conversation that works, and how to support someone remotely without doing it for them.
The short answer
- Ask what they are trying to do, teach the route rather than the taps, and keep your hands off the device while they practice.
- The real obstacle is unfamiliarity with arbitrary interface conventions, not capability, and those conventions keep changing underneath everyone.
- A notebook of numbered steps written in their own words is more useful than any explanation you give in person, because it is there when you are not.
- Five one time decisions remove most future calls: accessibility settings, automatic updates, one password system, working account recovery, and fewer notifications.
- Agree a call back rule and a family safe word in advance, and promise there will be no blame if something goes wrong, because shame is what hides losses until they are permanent.
- Prefer screen sharing they start themselves over remote control software, which teaches exactly the habit fake support callers depend on.
Ask what they are trying to do, teach the route rather than the taps, and keep your hands off the device while they practice. Most of the friction on both sides is a mismatch of goals: you want the problem gone in two minutes, they want to do it again next Tuesday without calling you. The second goal is the one worth serving. Add a few one time setup decisions and an agreed plan for suspicious calls, and the emergencies mostly stop.
The difficulty is unfamiliarity, not capability
It helps to be accurate about what is hard. Someone who ran a department, raised a family or rebuilt an engine is not defeated by complexity. They are unfamiliar with arbitrary conventions nobody ever explained: that three lines mean a menu, that the back arrow sometimes leaves the app entirely, that a dimming screen means asleep rather than broken.
You know those conventions because you have seen a thousand variations and can guess the next one. That is pattern recognition built from exposure, not intelligence. Put a software engineer in front of an unfamiliar industrial control panel and they will be just as stuck, and just as annoyed at being told to click the obvious thing.
Interfaces also change underneath people. An app updates, a button moves, and steps memorized last month stop working. That is a design problem, not a failing of memory, and saying so out loud removes a lot of tension.
Ask what they want to do, not what to learn
Open with the goal, in their words. Send a photo to my sister. Pay the water bill without going into town. Then build the shortest reliable route to that one thing and ignore everything else on the device for now.
Motivation carries the learning. Nobody retains a tour of settings they did not ask for, but they do retain the four steps that put a photograph in front of a sibling. Teach the second thing only once the first is comfortable, and let them choose what it is.
Resist improving things nobody complained about. Switching their browser or moving their email to a better service turns a working system into an unfamiliar one, and every later problem now traces back to your change. If something truly needs replacing, explain why, get agreement, and sit through the transition together.
Teach the path, not the tap
Saying press the blue button in the corner produces a person who can press one blue button. Saying we are going into settings, then sound, because volume lives under sound, produces a person who can find the brightness control on their own next week. The path is the part that transfers.
Narrate the reason for each move. Apps hide their own options behind the three dots or the gear. Anything about the whole device lives in settings. A list usually offers more choices if you press and hold. Four or five rules like these cover a startling amount, and they survive the next redesign in a way button locations do not.
Waiting is the hard part. Silence while somebody hunts for an icon feels far longer to the watcher than to the searcher. Let it run.
Write it down, in their words
A notebook next to the device beats any explanation you give in person, because it is there at nine in the evening when you are not. Let them write the steps as you go, in their own phrasing, including the parts you think are obvious. Their words are the ones they will recognize later.
Number the steps, one action per line, and describe what the screen should look like after each one so they can tell when something went wrong. Leave margins, because apps change. The format matters far less than who wrote it.
The one time setup that removes most calls
A few decisions, made once and with their agreement, remove whole categories of problem.
- Accessibility settings, done properly. Larger text, bold text, higher contrast, reduced motion, a longer touch and hold delay, balanced audio for a weaker ear. These live under accessibility on every platform, and plenty of people in their thirties use them too.
- Automatic updates on. Security fixes arrive without a conversation, and changes come in small steps rather than one alarming jump after two years. Knowing which updates matter and which can wait lets you explain the reasoning rather than insisting.
- One decision about passwords. Either a password manager, where one vault holds everything behind a single strong passphrase, or a dedicated book kept somewhere private at home, which is a fair choice for someone whose real threat is forgetting rather than burglary. Scattered notes and reused passwords are the thing to fix.
- Recovery set up before it is needed. A current phone number, a second email that is actually checked, and a trusted contact. Almost every lockout traces back to a recovery method that stopped working years ago, so getting account recovery right in advance is the best half hour on this list.
- Less noise. Turn off notifications from anything that is not a person, remove apps they never open, and put the four they do use where they can always be found.
| The call you get | What it usually is | The change that stops it repeating |
|---|---|---|
| My email has disappeared | A different app opened, or the account signed itself out | One mail app in a fixed place, recovery details current |
| The writing is too small | Default display settings | System text size and contrast raised once, for every app at once |
| A message says my computer is infected | A browser pop up, not the computer | Practice closing the tab; agree never to call the number shown |
| It wants a password and I do not have it | A password saved on a different device | One password manager or one notebook, used everywhere |
| Everything looks different today | An app update moved things | Expect it, and update the written steps together when it happens |
| The screen is frozen | A dialog waiting for an answer, or a slow connection | Teach reading the box before tapping, and how to force close an app |
The scam conversation that works
Lectures do not work here, and neither does fear. What works is a rule that needs no judgment in the moment, because a scam is built to remove judgment.
Agree one sentence: we never act on an incoming call or message, we hang up and call back on a number we already had. The number on the bank card, on a statement, or already saved in the phone. That single habit defeats the whole family of calls insisting your money be moved to a safe account, because those depend on keeping the person on the line, and it handles caller ID, which can be set to any number the caller likes.
Add a family safe word for emergencies: a word that anyone claiming to be a relative in trouble must be able to say. This used to feel excessive and no longer does, because a convincing copy of a familiar voice now takes only a few seconds of audio. Agree it out loud, tell everyone, and never send it in a message.
Then say the part that matters most. If anything ever goes wrong, they can call you, you will not be angry, and you will never ask how they fell for it. Shame is what keeps losses hidden until the money is gone. Mention too that these attempts land on people of every age, because being cast as the vulnerable one is exactly what stops somebody picking up the phone.
Helping from three hundred miles away
Remote help is where well meaning advice goes wrong most often. Installing remote control software so you can take over the machine teaches exactly the behavior fake support callers rely on: that letting a distant voice drive your computer is normal.
Safer arrangements exist. Screen sharing inside a video call app they already use lets you see without touching, which is usually enough. If you do use a remote access tool, make the rule absolute: started only by them, only during a call they placed to you, never in response to anyone who contacted them first.
Whatever you use, describe what you are doing while you do it, and say when you have finished and disconnected. Watching a cursor move on its own with no explanation is unsettling, and it is also indistinguishable from what an attack looks like.
What to set up this weekend
If you have one visit, spend it like this. Ask what they wish the device did better and fix that first, because it buys goodwill for everything else. Turn on the accessibility settings together. Check that the recovery number and backup email actually work. Agree the call back rule and the safe word, and write both in the front of the notebook. Then leave the notebook, not a lecture.
Book a specific time to check in rather than saying call me any time, which most people will not do because they do not want to be a nuisance. If the household includes other adults, shared subscriptions or children, the same decisions are easier made once for everyone, which is what a household technology setup is for.
Common questions
How do I stop getting the same question every week?
Write it down together the next time it comes up, with numbered steps in their handwriting and a note of what each screen should look like. Repetition usually means the sequence was demonstrated rather than practiced. Have them do it twice while you watch and say nothing, then once more a week later. Steps performed three times stick far better than steps watched ten times.
Should I just manage their accounts for them?
Only if they ask you to, and even then keep them informed rather than in the dark. Taking over accounts removes their ability to solve anything alone and makes you a single point of failure when you are unreachable. A better middle ground is being named as a trusted or recovery contact, which gives you a way to help in a genuine emergency without holding the keys day to day.
What if they refuse to use a password manager?
Accept it and use the alternative properly. A dedicated notebook kept in a private place at home is a reasonable system for someone whose realistic risk is forgetting rather than burglary. What matters is that every account has its own password and that they are written down somewhere consistent. Scattered notes, reused passwords and guessing are the actual problem.
They insist a caller was really from their bank. What now?
Do not argue about the caller. Move the conversation to the rule instead: hang up and dial the number on the back of the card, from a different phone if possible. If they already gave details, call the bank immediately on that number and ask for the account to be protected. Banks expect these calls and would much rather hear from you early.
Is it patronizing to set up parental style restrictions?
Yes, if it is done to them rather than with them. Content filters and spending limits belong to the person whose device it is, and applying them without a conversation damages trust for no security gain. Explain what a setting does, what it blocks, and how to turn it off, then let them decide. Anything they cannot switch off themselves is a control rather than help.