Blue Sage Data Systems
A play we run when AI rollouts stall in Lincoln

Lead with the people narrative before the technology roadmap

When adoption stalls, the fix isn't a louder rollout. It's answering the question employees are actually asking — what changes for me, what stays the same, what does my role look like in twelve months — before introducing one more tool.

Omaha companies asking the same? See the Omaha view →

Text Rosey · Schedule a call →

The pattern

The pattern is consistent across stalled rollouts: leadership announces an AI initiative, frames it as productivity or cost savings, gives staff access to a tool, sets up a usage metric, and waits. Adoption flatlines. Leadership concludes the staff is resistant. Staff conclude leadership has lost the plot.

What's actually happening: employees are reading the productivity-and-cost-savings framing as layoff preparation. Gartner's 2024 research found 73% of HR leaders report employees experiencing change fatigue, and 74% say managers aren't equipped to lead change. In Lincoln especially, where Nelnet, Ameritas, Bryan Health, and the State of Nebraska have all rolled out tooling changes in the last 18 months, layering AI on top without rebuilding the narrative is the fastest way to lose the room.

The fix is changing what you communicate first. The technology roadmap is a poor opening move. The people narrative — what changes for me, what stays the same, what does my role look like in twelve months — is the right opening move.

The play

  1. Audit the change load before adding anything

    List every initiative in flight that affects your team. AI rollout layered on top of three half-finished initiatives is what the research calls "change fatigue." Sequence the AI rollout to land after — or in place of — something else.

  2. Write the people narrative for each affected role

    For each role touched by the rollout, write a one-page document. What changes (specific tasks). What stays the same. What the role looks like in twelve months. Real specifics — not "AI will help you focus on higher-value work."

  3. Equip managers before staff

    Gartner — 74% of managers aren't equipped to lead change. Before staff hear about the rollout, managers need rehearsals, scripts, and the FAQ they'll get. Manager-led adoption is dramatically more durable than top-down mandate.

  4. Replace activity metrics with outcome metrics

    Token spend, login frequency, "used AI today" counts get gamed within a week. Use cycle time, error rate, customer outcomes, employee capacity.

  5. Build a feedback loop and use what it tells you

    Gartner's 2026 CHRO research found organizations that adapt change plans based on employee feedback are 4x more likely to achieve change success. Run a structured 2-week pulse, then adjust the rollout visibly.

  6. Address the replacement narrative directly, not implicitly

    If you're not going to lay people off, say so specifically. If you can't say that with confidence, don't pretend. Employees can tell when leadership is hedging.

What changes at 30 / 60 / 90 days

30 days

Change-load audit complete. Managers have role-specific scripts. Staff hear the people narrative before the tool. Activity metrics replaced with outcome metrics.

60 days

Feedback loop has produced two visible adjustments to the rollout. Manager-staff conversations are happening (not avoided). Adoption pattern shifts from 'compliance' to 'use.'

90 days

Outcome metrics show real change in cycle time or error rate. Manager confidence is measurably higher. The rollout has stabilized.

When this play applies

When is this play the right move?
When adoption is flat or going backwards, when you've heard 'they're just resistant' from leadership, when usage metrics look fine but the work isn't changing, or when manager engagement is low.
How long before we see results?
Most of the work happens in the first 30 days — the change-load audit, the people narrative, the manager enablement. Behavior shift becomes visible at 60 days. Outcome metrics catch up at 90.
Do we have to halt the rollout to run this play?
Usually not. Most teams can run this in parallel with continued tool access — but with the metrics, narrative, and manager preparation realigned.
What if the people narrative is genuinely 'we're trying to reduce headcount'?
Then the rollout is going to fail no matter what you do, because the staff already knows. The honest move is to separate the AI rollout from the headcount conversation.
Does this play work for AI specifically, or any change effort?
It works for any change effort. It's especially load-bearing for AI rollouts because the replacement narrative is unusually loud in the broader culture.

Sources

Related

Playbook
rebuilding the rollout around the team
Concern
passive resistance to AI
Concern
what AI rollout means for headcount in Lincoln
Service
fixing stalled AI adoption
Service
running AI from strategy to cutover
Function
AI workflows for HR
→ 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