“The computer is slow” describes an experience, not a diagnosis. Identify the task that takes too long: signing in, opening a file, loading a website, joining a call, or running a particular application. The pattern points to the next useful test.
Compare tasks and users
If local files open quickly but one online service is slow for everyone, investigate that service or shared connectivity. If only one computer struggles with many tasks, look at that device’s workload and condition. Record when the issue occurs and whether it follows a recent change.
Ask users for a concrete example with a time and file or application name. Avoid including confidential file contents in general support messages. A repeatable example lets support compare behavior before and after a change.
Check competing work
Updates, synchronization, large transfers, and resource-intensive applications can overlap. Review activity using the operating system’s normal tools with IT support. Do not disable security tools simply to make a performance graph look better.
Low free storage, unreliable hardware, or an unsuitable device configuration may require a different response from excessive browser tabs. Confirm which resource is constrained before buying an upgrade.
Examine the work environment
Compare a docked and undocked setup when appropriate. Check whether delays happen only in one room or on one network. A weak wireless connection can resemble a slow computer when the employee’s work depends on cloud applications.
Make one measured change
Record the baseline, apply an approved change, and repeat the same task. Changing many settings at once makes it difficult to know what helped. Keep the result in the support record so recurring problems can be recognized.
For room-specific issues, use the office Wi-Fi guide. For unreliable hardware, prepare the repair checklist.