A user interrupted me with an "urgent" email issue. They were opening Outlook for the first time, and it asked them to enter an email address and click Next. The address that filled in automatically belonged to a sister company in our shared tenant, so they needed to replace it with their actual work address. Instead, they had no idea what to do and didn't consider simply typing the correct address into the field. How do you handle users who seem unwilling or unable to follow simple instructions or attempt basic troubleshooting?
4 Answers
Automate or simplify the common cases wherever possible. If users regularly get the wrong address in Outlook, fix the account discovery or onboarding process so the correct identity is selected automatically. For the human side, create short, searchable guides for the most common tasks and use training for people who repeatedly struggle. Support should solve the immediate problem, while management handles ongoing performance or computer-literacy issues.
Try not to treat every lack of technical confidence as stupidity. Some people are genuinely afraid they’ll break something, especially on a work computer, so they freeze when an unexpected screen appears. I explain the fix, keep the tone neutral, and let them perform the steps themselves instead of taking over the keyboard. That way they gain a little confidence and may remember it next time.
For a one-off request, just help them politely and move on. Everyone has areas where they’re not comfortable, and being condescending usually makes people even less willing to try. I often explain the solution briefly, then have the user repeat the steps while I guide them. The goal is to get them working without making them feel foolish.
There’s also a difference between someone who lacks experience and someone who deliberately offloads every trivial task. The first deserves patience; the second needs consistent boundaries and manager involvement.
The biggest improvement is setting boundaries and using a proper support process. Everything should become a ticket, and “urgent” should mean an actual business-impacting outage, not a user getting stuck on one setup screen. Document recurring issues, point people to clear guides with screenshots, and track repeat requests. If someone repeatedly refuses to read instructions or learn the process, involve their manager rather than quietly doing their work for them.
For a small team, even a simple rule like “submit a ticket before interrupting someone” makes a huge difference. It also gives management evidence when one person is consuming an unreasonable amount of support time.
I’ve found that asking questions like “What does the message say?” or “Which option looks like it matches what you need?” gets people thinking without making them feel embarrassed.