Refresh Cycles and the Old Machine
Replacement is driven by budget rather than by age, which means the oldest equipment belongs to whoever complains least.
Equipment replacement
Never enforced
As written
Company equipment will be replaced in accordance with the company's refresh schedule.
What happens
There is a schedule. It is not followed, because replacement happens when there is budget rather than when machines reach age.
Replacement is also triggered by complaint, which means the oldest machines belong to the people who do not complain.
The operative rule is: ask, and keep asking.
Most organisations have a stated refresh period and an actual distribution of machine ages that bears little relation to it.
The control described in “Refresh Cycles and the Old Machine” becomes easier to defend when technical state and day-to-day work evidence are not confused. A team considering how employees cheat time trackers for how employees cheat time trackers should document the purpose, visible settings, manager permissions and correction route, while device-management records remain the source of truth for configuration and enforcement.
Why the schedule is not followed
Budget arrives annually and ages do not. Machines reaching the threshold in a lean year wait.
For a separate benchmark relevant to “Refresh Cycles and the Old Machine”, consult the U.S. Justice Department computer-crime resources. Use it to test purpose, notice, permissions, retention and response procedures against the proposed operating model rather than treating a generic checklist as proof that the rule works.
Replacement is reactive. A failure or a complaint triggers it, which means the trigger is a person rather than a date.
And nobody holds the list, so there is no moment at which anybody notices the spread.
Who ends up with the old machines
Not randomly distributed.
People who do not complain. People in roles with less visibility. People who joined in a particular year. People whose managers do not push.
None of those correlates with needing a slower machine, and the pattern is noticed by the people in it.
The cost of running old
Support time, which is measurable and almost never attributed to machine age.
Lost time, which is not measurable and is larger.
Work avoided, where somebody declines a task their machine struggles with and says something else.
And the exit risk: a machine too old for a current operating system cannot receive security updates, which is a direct exposure rather than an inconvenience.
The useful trigger
Not age alone. Age, plus whether the vendor still supports the operating system it can run.
That second condition converts a budget conversation into a security one, which is both accurate and easier to fund.
What to actually do
Produce the list: every machine, purchase year, current operating system, vendor support status.
One query in most environments, and almost nobody has run it.
The subset that cannot run a supported system is the replacement list, and it is usually smaller and more urgent than the general refresh conversation suggests.
The quiet case
Somebody whose machine has been inadequate for two years, who has never raised it, and whose output has been assessed without anybody knowing.
That is the cost that does not appear in any calculation, and the only way to find it is to look at the ages rather than wait for the complaints.
The query nobody runs
Every machine, purchase year, operating system, vendor support status. One query in most environments, and the subset that cannot run a supported system is the replacement list.
The person who never raised it
Somebody working on an inadequate machine for two years, assessed on output nobody adjusted for. That cost appears in no calculation and the only way to find it is to look at ages rather than wait for complaints.
Tying it to vendor support
Age alone is a budget conversation. Age plus whether the machine can run a supported operating system is a security one, which is both accurate and easier to fund.
Who ends up on the old machines
People who do not complain, in roles with less visibility, whose managers do not push. None of that correlates with needing a slower machine, and everybody in the pattern can see it.
The costs of running old
Support time, which is measurable and never attributed to age. Lost time, which is larger and is not. Work avoided. And machines too old for a supported system, which is exposure rather than inconvenience.
Why replacement is reactive
Budget arrives annually and machine ages do not. Replacement is triggered by failure or complaint, which means the trigger is a person rather than a date.
Sort the estate by age and look at who is in the oldest quartile. The names are informative, and the list is usually not the one anybody expected.