Hardware Refresh Cycles: The Great Debate

Three years, four, or five? Three curves you can measure in your own environment — and why the confident numbers are the least trustworthy. Somebody in your organization decided how long a laptop lives. Ask where that number came from and you'll usually get "it's industry standard," "that's what the lease term was," or a long pause. Meanwhile it quietly determines a seven-figure line item every year. This episode doesn't hand you a number. It hands you a method. The Three Curves — failure, cost, and value — each measurable in your own environment from data you already have, and where they intersect is your refresh cycle rather than a vendor's. Along the way: why the widely quoted refresh statistics don't survive being traced to their sources, what actually fails in a modern laptop and why it's cheaper to fix than you think, the residual value you forfeit by stretching a cycle, and how the Windows 11 hardware requirements turned refresh from a hardware question into a platform runway question. Plus a listener question from Tony in Toledo, whose CFO wants to move from four years to six — and the argument that actually works in that meeting. IN THIS EPISODE - Why most refresh cycles have no documented origin - The provenance problem: tracing the widely quoted statistics back to dated or vendor-funded sources - Curve one — failure: what actually breaks in a modern laptop, and why it's rarely the drive - Curve two — cost: building your own support-cost-by-age curve in an afternoon - Why the cost curve turns upward exactly when the warranty expires - Curve three — value: the residual recovery you forfeit by stretching the cycle - Paying twice, in two different budgets, across an accounting seam - How Windows 11 hardware requirements changed refresh from hardware to platform runway - Buying for supported life rather than unit price - The AI PC question, and whether NPU capability justifies acceleration - Weeding the collection: why librarians never withdraw a book for turning four - Segmenting the fleet — why one cycle is wrong for most of your users CHAPTERS (00:03) - Refresh Debate Begins (02:22) - The Three Curves (04:09) - Failure and Cost (07:01) - Push Back with Data (07:22) - The Value Curve (08:46) - Security Changes the Game (11:01) - The Library Analogy (12:01) - Segment Your Fleet (12:39) - Refresh Is Economics (14:02) - Disposal Next Time TRANSCRIPT Click here to view the episode transcript. SOURCES & FURTHER READING Microsoft — Windows 10 end of support https://www.microsoft.com/en-us/windows/end-of-support Microsoft — Windows 11 system requirements https://www.microsoft.com/en-us/windows/windows-11-specifications A note on evidence: the refresh statistics circulating in this field are unusually poorly sourced. Figures on failure rates and support costs for aging hardware typically trace back either to studies more than a decade old or to research funded by hardware manufacturers. This episode deliberately avoids quoting them. The Three Curves framework exists so you can measure your own environment instead of borrowing someone else's number. LISTENER CASE FILES Got a situation you'd like worked on air? Send it over — anonymized, sanitized, no company names. Real constraints, real politics, real budgets. operationalitam.com ABOUT THE SHOW Operational ITAM is a podcast about the unglamorous machinery of enterprise technology — hardware and software asset management, licensing, audit defense, SaaS governance, and the money quietly leaking out of all of them. Bill Van Nort has led IT asset management, end-user computing, IT operations, and workplace technology at large organizations across banking, mortgage, and automotive. He has reclaimed millions in software spend and survived audits from the biggest publishers on the planet. Consulting enquiries and listener case files: operationalitam.com