Audit your total change load before launching anything new

The play

1. List every initiative in flight that affects the team

   Not just the formal projects — the informal ones too. New CRM rollouts, sales-methodology shifts, performance-review redesigns, ERP migrations, hiring sprints, compliance projects, security audits, leadership transitions. The full list is usually longer than executive memory.

2. For each initiative, mark its stage and remaining staff load

   Pre-launch / in-progress / wrapping up. Hours per week of staff attention currently consumed. Manager time consumed. Most leaders are surprised by the cumulative number.

3. Identify the bottleneck people

   Some staff are touched by every initiative — usually managers, ops leaders, IT/Security partners, HRBPs. Those are the people the AI rollout will require, and they're already at capacity.

4. Sequence honestly

   Three options. (a) Land AI rollout after the most-loaded initiative wraps. (b) Pause or stop a lower-priority initiative to make room. (c) Add AI rollout with eyes open and reduce scope on something else. The wrong move is to claim AI rollout will be "small" and stack it without trade-off.

5. Communicate the sequence visibly

   Staff already feel the change load. When leadership communicates the sequence — what's coming, what's deferred, what's been stopped — the relief is real. Gartner 2026 found organizations that adapt change plans based on employee feedback are 4x more likely to achieve change success; this audit is where that adaptation starts.

6. Run the same audit quarterly

   Change load is dynamic. Initiatives finish, new ones start, priorities shift. Quarterly audit prevents the next stack-up.

When this play applies

When is this play the right move?

Two signals. (1) The team's reaction to the AI announcement is muted-flat (not resistant, but not engaged). (2) Multiple unfinished initiatives are visible at the leadership level. If both are present, this play comes before the AI rollout — full stop.

What if leadership won't deprioritize anything?

Then the rollout will likely fail, and the audit will be the documentation of why. Sometimes that's worth doing — the audit becomes the evidence that forces a re-prioritization conversation later. The honest move is to surface the conflict before, not after.

Doesn't this just delay things?

It delays the start, often substantially. But it dramatically reduces the chance of a stalled rollout. The math usually works out — a 6-week delay before launch beats a 6-month delay during launch by a wide margin.

Who runs the audit?

Best done by HR or Operations leadership, not the AI rollout owner. The AI rollout owner has incentive to underweight the change load; an outside-the-rollout owner is more honest. We typically run this jointly with HR for clients.

What about urgent regulator deadlines?

Different math. NAIC IGD-H1, HIPAA, Section 1557 — those timelines aren't negotiable, so the audit becomes about which other initiatives to defer to make room. The audit still applies; the conclusion just gets forced.

Sources

• 73% of HR leaders report their employees are fatigued from change — Gartner Survey Finds Leader and Manager Development Tops HR Leaders' List of 2025 Priorities for Third Consecutive Year, Gartner, 2024
• 74% of HR leaders say their managers are not equipped to lead change — Gartner Survey Finds Leader and Manager Development Tops HR Leaders' List of 2025 Priorities for Third Consecutive Year, Gartner, 2024
• Organizations that continuously or regularly adapt change plans based on employee responses are 4x more likely to achieve change success — Gartner Identifies the Top Change Management Trends for CHROs in the Age of AI, Gartner, 2026
• Employees may 'perform' change outwardly without genuinely adopting it — Gartner Identifies the Top Change Management Trends for CHROs in the Age of AI, Gartner, 2026