6 Pieces of IT Equipment Advice Everyone Gives That's Actually Wrong

There's a version of IT equipment advice that gets passed around like it's been stress-tested: handed down from finance teams, repeated in procurement meetings, and treated as settled wisdom. Most of it hasn't been tested at all. It's just old.

The real problem isn't that companies are making reckless decisions. It's that they're making careful decisions based on frameworks that were designed for a different era of work: before distributed teams, before contractor-heavy workforces, before a single offboarding failure could become a compliance incident. The advice sounds reasonable. That's what makes it persuasive.

Here are the top six pieces of IT advice that deserve a second look.

Advice 1: "Let accounting set the refresh cycle", or why your three-year depreciation schedule is an IT policy in disguise

Depreciation schedules exist to satisfy finance, not to reflect how hardware actually ages under real workloads. A three-year straight-line depreciation model tells you when an asset loses book value, but it says nothing about when a device starts costing more in lost productivity, failed updates, and security exposure than it would cost to replace.

The problem is that when finance sets the cycle, IT inherits it. The refresh decision stops being a performance question and starts being a budget calendar event. Devices that are genuinely degraded stay in circulation because they haven't hit year three. Devices that are still performing get replaced because they have.

Imagine a software engineer whose MacBook Pro is 28 months old and running hot under compile loads, dropping frames on video calls, and failing to install the latest OS update. Under a three-year cycle, that device has four more months to go. The engineer works around it. IT knows about it. Nobody acts because the policy says not to.

The bottom line: When accounting sets the refresh cycle, IT is no longer managing device performance but a de facto depreciation schedule. Those are not the same job.

Advice 2: "Get warranty coverage, and you're protected" — what warranty actually covers, and what it quietly doesn't

Warranty is sold as protection. What it actually covers is manufacturing defects and hardware failure under normal use. It does not cover accidental damage. It does not cover theft. It does not cover the three weeks a device spends in a repair queue while a new hire works from their personal laptop. And it does not cover the data on the device if it leaves the building without being wiped.

The advice to "make sure everything's under warranty" creates a false sense of coverage. IT teams check the warranty box and move on, without asking the harder question: what happens operationally when a device fails, gets lost, or needs to be recovered from a remote employee in a country where you have no local presence?

Warranty is a manufacturer's promise about the hardware. It says nothing about what happens when a device is lost, delayed, reassigned, or never recovered. That's where most operational risk actually lives.

Find out what happens when access isn’t revoked on time.

Advice 3: "Use a standard asset tag and spreadsheet to track your fleet" — why the spreadsheet that's accurate in January is fiction by October

Asset tagging is the right instinct. The spreadsheet is where it goes wrong. A spreadsheet is a snapshot: it reflects the state of the fleet at the moment someone last updated it. Devices get reassigned without a row being edited. Contractors return hardware that gets put in a drawer and never logged as available. A new hire in a new country gets a device sourced locally and never entered into the master sheet at all.

By the time an audit request arrives, or a device goes missing, or IT needs to know how many machines are running an outdated OS, the spreadsheet is already months behind reality. The team that built it knows this. And as the fleet grows and changes, the spreadsheet gradually falls behind.

Here is the problem: yes, the advice to "keep a good asset register" is correct. But the assumption that a spreadsheet is a good asset register is not. At any meaningful scale (and "meaningful" here starts at around 50 devices), a spreadsheet cannot maintain accuracy without a level of manual discipline that no real team sustains.

The bottom line: If ‘asset tagging can wait’ is the advice, the cost is a spreadsheet that's accurate in January but fiction by October.

Find out about the top 6 IT procurement challenges.

Advice 4: "Contractors can use their own devices — it's simpler" — but what happens to company data when the engagement ends?

BYOD for contractors gets framed as a convenience decision. It is actually a data governance decision, and most companies are making it without realizing that's what it is.

When a contractor uses a personal device, company data (files, emails, Slack messages, browser-cached credentials, downloaded documents) lives on hardware the company has never enrolled, never configured, and has no ability to wipe. When the engagement ends, offboarding typically covers access revocation: the accounts get closed, the Slack is deactivated. The data already on the device stays there.

This isn't a theoretical risk. A contractor who worked on a product roadmap, a financial model, or a client proposal has local copies of those files. But the company's ability to recover or erase them is zero if the device was never under management.

The advice to let contractors use their own devices because "it's simpler" is only simpler at the start. The complexity arrives later, in the form of data (and compliance exposure) you can no longer account for.

Learn what happens to company data when an employee leaves.

Advice 5: "Buy software licenses separately from hardware to keep procurement clean" — why decoupled purchasing creates a shadow IT problem

The logic here is tidy: hardware goes through one budget, software through another. Finance likes the separation. Procurement likes the separation. The problem is that the separation creates a gap between what's installed on a device and what IT has licensed and can see.

When hardware and software procurement are managed independently, with no shared system of record, license tracking becomes a reconciliation exercise. IT knows what was purchased, but it doesn't always know what's running. Employees install tools that weren't provisioned centrally. Licenses expire on devices that are still in use. Paid seats sit idle on devices that were reassigned or returned.

According to a 2024 study conducted by Zylo, the average company loses $18M on SaaS licenses, up 7% year over year. That figure isn't caused by reckless purchasing but by the structural disconnect between who buys software and who tracks where it ends up.

Keeping procurement "clean" by separating hardware and software budgets doesn't reduce complexity. It just moves the complexity somewhere less visible.

The bottom line: Decoupled purchasing doesn't simplify IT management, it just ensures the mess is harder to find.

See also: 5 ways to reduce IT costs.

Advice 6: "Wipe the device when someone leaves" — why treating offboarding as a single action misses where the exposure actually is

Wiping a returned device is the right thing to do. The advice to "make sure you wipe it" implies that the wipe is the hard part. It isn't. The hard part is everything that has to be true before the wipe is meaningful: the device has to be returned, the data has to not already be elsewhere, access has to have been revoked before the employee had a reason to copy anything, and the wipe has to be certified in a way that satisfies an auditor.

Most offboarding processes treat the device wipe as the final step in a checklist. What they miss is that by the time the device comes back, the window for data exposure has usually already passed. Files were downloaded in the last week of employment. Credentials were shared. A personal cloud sync was running in the background for months.

The advice to wipe the device is not wrong. It's just answering the wrong question. The question isn't "did we wipe it?" but rather "did we maintain control of the data throughout the entire employment period, not just at the end?"

Find out more about the common offboarding failures on remote teams.

Why this advice keeps circulating even when it doesn't work

None of the advice above is malicious. Most of it made sense in a context that no longer exists: smaller teams, co-located offices, simpler contractor relationships, software that lived on servers rather than in browsers and local caches. The advice calcified before the context changed.

The other reason it persists: the cost of following bad IT advice is almost never visible on a single budget line. A three-year refresh cycle doesn't produce a line item called "productivity lost to aging hardware." A BYOD contractor policy doesn't produce a line item called "data we can no longer account for." The costs are real and show up in support tickets, in audit findings, in security incidents, in employee frustration. They are distributed across enough teams and time periods that no one connects them back to the original advice.

That invisibility is what keeps the advice alive. It never fails loudly enough to be corrected.

How Deel IT helps you move beyond outdated IT practices

Deel IT helps IT teams manage the entire device lifecycle—from procurement and deployment to access management, compliance, and offboarding—in one platform, replacing fragmented workflows with automated, policy-driven operations.
Deel IT replaces the fragmented stack that makes inherited advice feel necessary:

• Procure and deploy devices globally in 130+ countries, pre-configured and ready to use
• Enforce security and compliance from day one with MDM enrollment, remote lock and wipe, and certified data erasure at offboarding
• Manage access from one place with centralized application access, permissions, and identity controls
• Automate lifecycle workflows with HR events triggering device provisioning, application access, and instant access revocation when people join, move, or leave
• Track devices, applications, and licenses with real-time visibility across your global fleet
• Support distributed teams worldwide with 24/7 global IT support

Book a demo and see what IT management looks like when it's built around how distributed teams actually work.