A slow application can lead quickly to a request for more network capacity. Before changing a connection, a government support team needs to understand where the delay appears and which observations would help distinguish possible causes.
Compare the same task
Ask affected staff to describe the exact action, location, time, and frequency of the delay. Compare the experience with an authorized user in another location or with another task on the same device. Keep the comparison controlled enough to be meaningful and avoid collecting sensitive application content in an ordinary ticket. These observations guide investigation without declaring a cause prematurely.
Bring the right owners together
Share the findings with the teams responsible for the application, endpoint, and connection as appropriate. Ask each team what evidence it needs and who will coordinate the case. Record any change made during investigation so a later improvement can be assessed against a known sequence. Test the original user task again before closing the issue. Keep one coordinator responsible for gathering the observations from the participating teams.
Practical takeaway
Treat capacity as one question within a broader investigation. A repeatable description helps the team choose a proportionate response instead of purchasing an answer before identifying the problem.