Sounds like you

“We bought the tool and the workflow did not actually change.”

“People nod through the training, then go right back to the old way.”

“The license report says adoption is fine. Real usage says otherwise.”

“I need the rollout to actually stick, not spike and fade.”

The problem

You bought the tool. The workflow did not change.

The model is fine. The rollout is what stalled. People route around the new system, keep their old habits, and quietly decide it is not for them. Adoption is not a license-count problem or a training-video problem. It is a behavior problem, and it gets solved by designing around how people actually work, not how the org chart says they should.

Who it is for

COOs CHROs Heads of transformation Teams rolling AI into real workflows

What you get

Adoption designed from behavior, not from a mandate.

The handoff map. Where an agent owns a step, and where a human stays in the loop, made explicit instead of assumed.
Behavior-first rollout. Adoption designed from how people actually behave, so the new workflow fits the work they already do.
Friction removed at the source. The small, real reasons people route around the tool, found and fixed.
A change that holds. Enablement that survives after the launch email, not a spike that fades in a month.

The rare combination

Twenty-five years of UX research into how humans adopt tools, paired with hands-on AI delivery. The honest version: this is a developer-coaching and UX-adoption lens applied to AI rollout, not a packaged corporate-literacy bootcamp. I work the human side of adoption the same way I work the technical side, from evidence about real behavior.

How it works

Step 01

Watch the real work

A 30 minute call, then a look at how the workflow actually runs today, friction and all.

Step 02

Draw the handoffs

Decide, step by step, where the agent acts and where a human stays in the loop.

Step 03

Pilot with real people

Roll it into one team, designed around how they behave, and watch what sticks.

Step 04

Scale what holds

Widen the patterns that worked, on a standing cadence so adoption keeps climbing.

Questions

How is this engaged? +

As a monthly retainer. Adoption is not a one-off event; it needs a standing presence to design the rollout, watch behavior, and adjust.

Is this training, or something else? +

It is broader than training. Training is one lever. The work is deciding where agents own a step versus where humans stay in the loop, then designing the rollout from how people actually behave. If you specifically want hands-on sessions, see Workshops.

Do you build the AI too, or just the adoption? +

Both, and that is the point. I deliver AI hands-on and work the human side of adoption from the same evidence. If your system itself is stuck, that lives in AI Agents to Production.

Remote or on-site? +

Remote-first, based in Minneapolis, working across the United States. On-site when a rollout genuinely calls for it.

Tell me which rollout stalled.

A 30 minute call, no deck, no pitch. We look at why people are routing around the tool and whether I am the right person to fix it.

Book 30 min ↗ Or just email me