A slow computer does not automatically need replacement parts. A delayed accounting screen, a large Excel workbook and a slow sign-in need different investigations. Start by describing the interruption with a repeatable example from the employee's actual work.
1. Identify where the delay begins
Compare the operation using a local file, a shared folder and the relevant application. If only server files are slow, the network or file server needs attention alongside the workstation. Record when the delay starts, roughly how long it lasts and whether colleagues see it too. Hide customer information in screenshots; the support team does not need a real invoice to understand a delay. The same complaint across several employees can point to a shared service dependency.
- Example: the same report, the same user and the same connection.
2. Observe resource usage
Observe CPU, memory and disk usage in Task Manager while the delay occurs. Comparing a screenshot with normal working conditions is more useful than interpreting one high reading. One hundred percent disk activity alone does not establish a disk failure. Record startup application names, while leaving managed security, backup and device management components to the administrator. Include the free space on the system drive.
- Distinguish persistent load from a short update or scan.
3. Plan changes around the workflow
A useful assessment combines application requirements, device specifications and storage condition. Before cleanup, updates or upgrades, identify a current copy of business files and an appropriate maintenance window. Changing several things together makes their individual effects hard to judge. Afterwards, time the original report or file again and record the employee's experience during normal work.
- Measure first, define the intervention, then compare the result.
Official technical sources
This is general information. Version- and environment-specific work needs an authorised technical assessment.