Blue Sage Data Systems
A play we run before AI rollouts at Lincoln companies

Audit your total change load before launching anything new

Most stalled AI rollouts aren't stalled because of AI. They're stalled because they were stacked on top of three half-finished initiatives that already burned out the team.

Omaha companies asking the same? See the Omaha view →

Text Rosey · Schedule a call →

The pattern

The signal that this play applies: leadership announces an AI rollout, and the engagement reaction from staff is muted. Not resistant — flat. People nod, agree to participate, and quietly de-prioritize the work.

What's actually happening is rarely AI-specific. Gartner's 2024 research found 73% of HR leaders report employees experiencing change fatigue. Most mid-market companies have three to five other change initiatives in flight at any time. In Lincoln especially, where Nelnet, Ameritas, Bryan Health, and the State of Nebraska have all rolled out tooling changes in the last 18 months, the cumulative change load is real.

The audit happens before the AI rollout starts. It surfaces every initiative consuming employee attention, sequences them honestly, and either delays the AI rollout, replaces a lower-priority initiative, or makes a deliberate decision to add change load with eyes open.

The play

  1. List every initiative in flight that affects the team

    Not just formal projects — informal ones too. CRM rollouts, sales-methodology shifts, performance-review redesigns, ERP migrations, compliance projects, security audits.

  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.

  3. Identify the bottleneck people

    Some staff are touched by every initiative — usually managers, ops leaders, IT/Security partners, HRBPs.

  4. Sequence honestly

    (a) Land AI rollout after the most-loaded initiative wraps. (b) Pause or stop a lower-priority initiative. (c) Add AI rollout with eyes open and reduce scope on something else.

  5. Communicate the sequence visibly

    Staff already feel the change load. Communicating the sequence creates real relief. Gartner 2026 found organizations that adapt change plans based on employee feedback are 4x more likely to achieve change success.

  6. Run the same audit quarterly

    Change load is dynamic. Quarterly audit prevents the next stack-up.

What changes at 30 / 60 / 90 days

30 days

Full inventory of in-flight initiatives complete. Bottleneck people identified. Sequencing decision made and communicated.

60 days

If a deferral or stop happened, staff feel the relief. AI rollout has clear runway with manageable parallel load.

90 days

AI rollout in flight with manager bandwidth it actually requires. Quarterly cadence on the calendar.

When this play applies

When is this play the right move?
When the team's reaction to the AI announcement is muted-flat, and multiple unfinished initiatives are visible at the leadership level.
What if leadership won't deprioritize anything?
Then the rollout will likely fail, and the audit will be the documentation of why.
Doesn't this just delay things?
It delays the start, but dramatically reduces the chance of a stalled rollout.
Who runs the audit?
Best done by HR or Operations leadership, not the AI rollout owner.
What about urgent regulator deadlines?
NAIC IGD-H1, HIPAA, Section 1557 — those aren't negotiable, so the audit becomes about which other initiatives to defer.

Sources

Related

Playbook
the change-load audit play
Concern
when AI productivity becomes a floor
Concern
the quiet AI rollout failure
Playbook
the people-first AI rollout play
Service
when employees won't use AI tools
Service
fully managed AI rollout
→ Start here

Text Rosey to begin.

Rosey is our executive-assistant bot. Text the number below — she'll ask two questions, offer three calendar slots, and put a 30-minute call on Jim's calendar.

Text Rosey · Schedule a call →

or call 415 481 2629