When IT slows down, start by pinpointing where the time is lost.
A computer that is slow to start, files that take a long time to open and business software that responds poorly do not necessarily point to the same problem. The right decision starts with telling them apart.
Observe a specific task.
Pick an example: opening a folder, launching an application or saving an order. Say who is affected, since when and under what conditions. A concrete observation is more useful than an overall verdict on "IT".
Avoid replacing things blindly.
An old workstation may deserve an upgrade, but the slowness can also come from the application, the storage or the connection. We examine the dependencies of the chosen scenario before proposing any action.
Build a response from the findings.
The next step may be a maintenance operation, a targeted change or an infrastructure project. The measures needed and their limits are explained. Changes are prepared with users and, where needed, with the vendor of the software concerned.
Check the result in day-to-day work.
The result should be compared on a representative task, under conditions everyone can understand. The aim is to make the task smoother, not just to improve a technical metric that makes no noticeable difference to your teams.
Your questions
Do we need to replace all the computers?
Not without knowing their condition and the source of the problems. Replacement can be targeted.
Can you diagnose the problem through a form?
The form prepares the conversation. A technical conclusion requires suitable observations and checks.
Further reading
Got a digital issue? You don’t have to work out who should handle it.
Describe your situation in your own words. The Skill Group team will get back to you to talk it through.