Case Study – CVS Enterprise PC Refresh
Overview
In February 2022, CVS Health engaged an outside program manager to lead their annual PC refresh cycle – a recurring enterprise initiative to replace end-of-life hardware across all three business units: CVS Retail, Aetna Healthcare, and Caremark Prescription Benefit Management. The program ran through August 2022.
The delivery target was 18,000 devices. The deadline was end of year.
The program closed at 106% of target in July – five months ahead of schedule.
Context
The Program
CVS runs a PC refresh cycle every year. The eligible device population is determined annually against a set of criteria – hardware age, installed RAM, CPU generation, operating system status – that typically surfaces roughly 20% of the enterprise device footprint for replacement. Those devices are catalogued, a target is set at a practical 100% threshold, and a program is stood up to execute against it.
The 2022 cycle targeted 18,000 devices across the full enterprise, with approximately 20,000 available as a stretch goal. Six projects ran in parallel: a Refresh project and a Growth project (covering organic headcount expansion) for each of the three business units, each with its own IT organization, its own desktop support structure, and its own operational context.
The Structural Challenge
CVS runs this program every year. It almost never retains the same program manager twice.
The downstream consequence is a standing knowledge debt. Each incoming program manager begins from approximately zero – rediscovering undocumented institutional knowledge, re-establishing relationships with the same teams, and rebuilding a program framework that should have been preserved and improved year over year. It is an organizational inefficiency that compounds the startup cost of every cycle.
That context is worth naming because it shaped the initial weeks of the engagement: a significant portion of early effort went into knowledge acquisition that a mature program management practice would have made unnecessary. The program succeeded despite this pattern, not because of it.
Program Structure
The Team
The program operated across three business unit IT organizations, each structured with a desktop manager, area leads across major office locations, and distributed desktop technician teams. In total, approximately 100 people touched the program across its lifecycle – though not simultaneously.
Execution was deliberately staged. Rather than activating the full team at once, cities and office locations were sequenced: a cohort would be activated, the refresh work completed, and that cohort would stand down before the next was brought online. At any given time, the active working group consisted of the three business unit desktop managers, approximately five area leads, and twenty technicians. This approach kept coordination overhead manageable and allowed focus and accountability to concentrate on the active geography.
The desktop managers were the primary day-to-day interface. Daily standups with that group kept deployment on track and surfaced issues before they became schedule risks. Weekly team-wide meetings ensured leads and active technicians maintained situational awareness across the program.
Procurement and Logistics
The procurement pipeline – working with Dell's account team and CVS's internal procurement lead – was already established when the program began. The program management role was to oversee it: ensuring devices were ordered to match the deployment schedule, shipped to the correct locations at the correct times, and available for technicians when each geographic cohort activated. Timing mismatches between procurement and deployment would have created idle time or schedule compression; neither occurred.
Imaging and local deployment were handled by the business unit technicians and their leads, who carried the operational knowledge of their end users and locations. The program manager role was coordination and sequencing, not hands-on technical execution.
Execution
Cost Accounting and Executive Reporting
The most demanding ongoing responsibility was financial – specifically, resource utilization forecasting and program cost accounting across six parallel projects. Weekly status reports went to VP-level leadership, one level below the CTO. A monthly roundtable required a formal presentation summarizing program health, deployment progress, financial actuals versus forecast, and forward projections.
Keeping six parallel workstreams financially visible and accurately forecast – while deployment geography shifted week to week – required a discipline around the numbers that did not allow for estimation lag. Executives making resource decisions needed accurate data, not approximations. That standard was maintained throughout.
Program Documentation and Visibility
The full documentation suite – RAID log, stakeholder register, deployment dashboards – was maintained as living documents rather than static snapshots. The intent was to keep information actionable: leadership could pull current status at any point without waiting for a scheduled update, and the team leads had a shared source of truth for deployment priorities and sequencing decisions.
Parallel Workstream Coordination
Six projects running in parallel across three organizational structures introduced coordination surface that a single-project program does not have. Dependencies between the Refresh and Growth projects within each business unit required ongoing alignment – a device procured for a Growth deployment could not be reallocated to a Refresh without cascading effects on both project plans. Maintaining that discipline across the full program, at the pace the delivery schedule required, was the primary coordination challenge.
Adjacent Work
Beyond the core refresh, the program contributed to a parallel initiative: updating CVS's device decommission process, including automating the removal of retired machines from Active Directory. This was not the primary program objective, but proximity to the refresh cycle made the collaboration natural, and the process improvement had downstream value for future cycles.
Outcomes
The 18,000-device target – the defined 100% threshold – was reached in July 2022, five months ahead of the December deadline. By contract end in August, the program had deployed 106% of the primary target and contributed to stretch goal progress across the business unit Growth projects.
The program closed on budget. No devices were delayed past their scheduled activation window. Executive reporting was current and accurate throughout.
The contract was not renewed – because the work was done.
What This Engagement Demonstrated
This was not a complex program. It is worth saying that directly, because inflating a clean execution into something it was not would undermine the credibility of the case studies that deserve more analytical weight.
What CVS demonstrated is different, and in its own way equally important: when the job is delivery, the delivery happens. On time, on budget, at quality, at scale – without drama, without heroics, and without the kind of fire-fighting that indicates a program being managed reactively rather than proactively.
Large programs run smoothly when they are structured correctly from the start. The staging model kept coordination overhead manageable. The financial discipline kept leadership confident and informed. The documentation kept the team aligned without requiring constant escalation. None of these are complicated ideas. Executing all of them simultaneously, across six parallel projects and a distributed team of approximately 100 people, for eight months, is the demonstration.
The program also surfaced a genuine institutional recommendation that CVS did not act on: retaining program continuity year over year. The startup cost of a rotating program manager is real, it is measurable in early-cycle inefficiency, and it is entirely avoidable. That observation was made. What CVS chose to do with it was their decision.
Engagement period: February–August 2022. Client: CVS Health (via contracting agency).