Should you replace the computer or fix what’s slowing it down?

The front desk says its computers are slow every morning. The owner is ready to replace three of them. Before I’d order anything, I’d ask somebody to show me the wait. Does the computer take ten minutes to become usable after sign-in, or does the scheduling application hang when staff open the first appointment? Those are both frustrating. Only one of them might be fixed by a faster computer.

I’d put the purchase decision on hold long enough to compare the same task on two machines. That small comparison can tell you whether to investigate a workstation, look at a shared service or replace equipment that’s already due to go.

Start with one task and one comparison

In this example, have someone open an appointment on the computer where they notice the delay. Ask when it starts, whether it goes away later and whether other tasks feel slow at the same time. Run the same task on a known-good computer during the same part of the morning. Use an appropriate test record where you can, especially if the application contains private customer information.

If the front desk computer struggles with sign-in, the browser and the scheduling application while a comparable computer works, a device-specific problem becomes more likely. IT can look at what the computer was doing during the wait. For instance, a busy disk while several applications start is a lead to investigate. It’s worth checking which activity is causing the delay and whether anything can be changed safely before buying a replacement. Microsoft’s Windows performance troubleshooting documentation covers the evidence technicians can collect.

If both computers are responsive until they open the same appointment screen, I’d ask whether the delay follows the application, the connection or the user’s workflow. Two slow machines don’t prove there’s a server problem, but they give you a reason to test a shared dependency before replacing three desktops. This is where a short recording of the problem or the exact time it happened helps the application vendor investigate.

Give the repair a stopping point

A computer that’s well within its supported life and has one identifiable fault may be a good repair candidate. Decide what success looks like before spending time on it. For the front desk, the test might be signing in and opening the first appointment reliably during the morning rush. If the machine comes back from a repair and feels quick in an empty office at 3 p.m., run the original test again the next morning.

I’d also set a limit on how much disruption the office will absorb to keep a marginal machine running. Count the staff time lost while it’s out of service and what a replacement would take to set up. If the same employee loses 15 minutes every morning, that’s an hour and a quarter in a five-day week. Use the observed delay to decide how long you’re willing to investigate and how soon you need a working spare. That time only belongs in the case for replacement once you know the replacement addresses the delay. If there’s a spare that can run the scheduling application and the required peripherals, using it temporarily can give the technician time to investigate without making the receptionist sit through another slow morning.

Replace it when there’s a reason you can explain

There are good reasons to replace a workstation even if it can be made faster. It may be unable to run a supported operating system or an application version the business needs. A recurring hardware fault can make the front desk unreliable. The repair might cost enough, or require enough downtime, that replacement is the better use of the budget.

Write down the reason in a sentence before approving the purchase. “This machine can’t run the supported scheduling client” gives you a requirement to check on its replacement. “It’s slow” leaves you hoping the complaint goes away. For broader budgeting decisions, see business technology planning.

In the front desk example, I’d put one repaired or replacement machine back into the actual workflow before committing to the other two. Test the scheduling screen, the printer and any scanner or card reader staff rely on. If the original wait disappears under the same conditions, you have a reason to repeat the fix. If the wait follows the application to the new machine, you’ve caught that before spending the rest of the budget.