Blue Sage Data Systems
A play we run for Omaha mid-market companies

The 30/60/90 AI adoption plan

A concrete sequencing model for the first 90 days of AI work — what to ship at 30, what to ship at 60, what to have in production by 90. Backed by McKinsey 2025 and Deloitte Q4 2024 data on what separates the rollouts that scale from the ones that stall.

Lincoln companies asking the same? See the Lincoln view →

Text Rosey · Schedule a call →

The pattern

The 30/60/90 plan exists because two conflicting data points pull on mid-market AI rollouts. McKinsey's 2025 data shows nearly two-thirds of organizations haven't begun scaling AI — and the high performers (~6% of organizations attributing 5%+ EBIT impact) are nearly 3x more likely to have fundamentally redesigned workflows. Workflow redesign takes time. So does governance: Deloitte 2024 found 69% of organizations expect implementing governance to take more than a year.

But "longer than a year" rollouts that haven't shipped anything by month three are the ones that get cancelled. The 30/60/90 plan is the structure that ships compounding wins early, while doing the longer governance and workflow-redesign work in parallel.

The non-negotiable: at the end of 90 days, one workflow is in production with trained users, an AI use policy is signed, and an approved tool list is enforced. The optional: how broad the rollout reaches, which workflows come next, what enterprise-scaling looks like.

The play

  1. Day 1–30: Diagnose, choose the wedge, draft the policy

    Two weeks of role-mapping interviews and workflow diagnostics. Pick one wedge workflow with high payback, clear data, named owner. Start drafting the AI use policy with Legal in parallel — the policy doesn't ship at 30 days, but the work does start. Stand up the approved tool list in draft form. Express-Harris 2026 found only 36% of companies have an approved tool list at all — getting one in draft by day 30 puts you ahead of the average.

  2. Day 30–60: Build the wedge in real systems, train the managers

    Build inside your real systems (AMS, core, EHR, ERP) — not a sandbox. Pilot with a named small group at week 6. Iterate on actual usage. In parallel, train the managers who will lead adoption. Gartner research shows 74% of HR leaders say managers aren't equipped to lead change; that's the work to do at this phase, not after.

  3. Day 60–90: Cutover, attest, measure

    Staged rollout to broader staff, manager-led. The AI use policy ships, attestation is tracked. Outcome metrics replace activity metrics — cycle time, error rate, customer outcomes. Quarterly review cadence is set on the calendar. The wedge workflow runs in production with trained users; the foundation for the next 90 days is in place.

  4. Concurrent governance work

    Governance work runs in parallel through all 90 days, not after. Approved tool list, AI use policy, AIS Program documentation (insurers under NAIC IGD-H1), third-party AI vendor due diligence (banks under OCC 2023-17), BAA review (healthcare). Deloitte's 69%-takes-over-a-year governance number assumes governance starts late; running it in parallel from day 1 cuts the calendar materially.

  5. Concurrent role-evolution narrative

    For each role touched by the wedge, write a one-page narrative — what changes, what stays, what the role looks like in twelve months. Ship it before staff training, not after. The replacement-narrative anxiety needs to be addressed up front, not in week 12.

  6. Concurrent feedback loop

    Build a structured 2-week pulse from day 30 onward. What's working, what isn't, what's blocking. Adjust the rollout based on what comes back. Gartner 2026 CHRO research found organizations that adapt change plans based on employee feedback are 4x more likely to achieve change success.

What changes at 30 / 60 / 90 days

30 days

Wedge workflow chosen with named owner. AI use policy and approved tool list in draft. Manager training plan scheduled. Role-evolution narrative drafted for the first affected roles.

60 days

Wedge running in pilot with a named small group inside real systems. Managers have completed their training and have scripts for staff conversations. AI use policy circulated for Legal review. Approved tool list piloted with Security.

90 days

Wedge workflow in production with trained users. AI use policy signed; attestation tracked. Approved tool list enforced. Outcome metrics replacing activity metrics. Quarterly review cadence on the calendar. Next workflow identified.

When this play applies

Why exactly 90 days?
Three reasons. (1) It's short enough to maintain executive attention without a re-pitch. (2) It's long enough to actually ship one workflow in real systems with trained users (not a demo). (3) It maps cleanly onto the calendar — quarterly board cycles, quarterly governance review cadence, quarterly business reviews.
Can we do this faster than 90 days?
Sometimes, with a narrow wedge and clean systems. The constraint is rarely build speed — it's how long the diagnostic, manager prep, and cutover take with your team's actual schedule. Faster than 90 usually means cutting one of those, which is where stalls happen.
What if the wedge fails?
Better to find out at day 60 than day 270. Most failures at this scale are about workflow choice — the wedge looked promising but didn't actually have an AI-shaped problem at its core. The 30/60/90 plan is structured to surface that early. Pivot at day 60 if the data says so; don't pretend through to day 90.
How does this connect to enterprise scaling?
The first 30/60/90 ships one workflow. Enterprise scaling is the next 12–24 months — typically a sequence of additional 30/60/90 wedges, each one shipping one more workflow. Don't try to ship enterprise transformation in one cycle. McKinsey's 2025 data shows that pattern fails.
What about industries with hard regulator deadlines?
Different math. NAIC IGD-H1 in Nebraska (June 2024 effective), HIPAA Security Rule NPRM (when finalized), Section 1557 affirmative duty (effective May 1, 2025). For each of those, governance work has to land 90–120 days ahead of the productivity wedge — sometimes the 30/60/90 plan is governance-only for the first cycle.

Sources

Related

Playbook
the first 90 days of AI adoption
Service
running AI from strategy to cutover
Service
workflow-anchored AI training
Service
an AI use policy that holds up
Answer
AI implementation timing
Concern
why AI experiments don't scale
→ 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