Slow Wi-Fi describes the experience, but it does not identify the cause. The bottleneck might be a device, a wireless connection, the internet service, or one application. A few structured observations help a consultant investigate the right part of the environment.
Describe one reproducible example
Write down the affected task, location, time, device, and whether other people noticed the same problem. A meeting that disconnects in one conference room is a different starting point from every employee losing internet at once.
Record error messages without capturing confidential content. If the issue is intermittent, keep several examples instead of changing settings after each incident. Include recent changes such as moved desks, new equipment, or an internet upgrade.
- Which rooms and work areas are affected?
- Does the same device work better elsewhere?
- Is one application slow or is everything affected?
- Does it happen at a particular time or occupancy level?
- Are phones, printers, or wired devices affected too?
Compare carefully rather than resetting everything
An authorized technician can compare wired and wireless behavior, different devices, and relevant network measurements. Those comparisons help narrow the fault. A single speed test cannot establish coverage, call quality, or application reliability throughout an office.
Avoid repeated factory resets or unplanned firewall changes. They can erase useful evidence and disrupt working services. Preserve current configurations and agree on the impact before any diagnostic change.
Review the space and equipment together
Access-point placement, building materials, cabling, power, device capabilities, and configuration all affect the investigation. A higher-priced router or a faster internet plan may leave the original problem untouched.
Share a floor plan and describe busy areas, guest use, conference rooms, and equipment that cannot easily move. An on-site review may be needed when remote evidence cannot explain the physical conditions.
Agree on a practical acceptance test
Define the business outcome before approving changes: reliable calls in the meeting room, usable coverage in a specific work area, or stable access for a defined group of devices. Then test that outcome under representative conditions.
Keep the observed results, configuration changes, and remaining limits in the handover record. Network improvements should be tied to the diagnosed problem; no equipment choice can guarantee every application's performance.