The Playbook

How I'd do this at your organization

The companion to the case study - that document is what happened. This one is what I believe, what I do, and what I'd do at yours.

What I believe

Two things, walking into every room: everyone deserves respect - not earned regard, baseline regard - and everyone genuinely wants to be successful. Hold those premises and a hard conclusion follows: when people aren't adopting, the explanation is never indifference. It's fear, or it's access. Both are fixable. That's the whole diagnosis, and it's why I couldn't write anyone off at my last engagement.

The diagnosis

At every level of an organization there is unspoken fear about AI - ambient. It doesn't answer surveys, which is why readiness assessments measure the wrong layer. It taxes exactly the executive function that adoption requires. Except for the handful who've quietly realized they're going to be okay - your existing early adopters - some meaningful part of enablement is listening for this fear and managing for it, without ever asking anyone to confess it.

The stance

Kindness and clarity, held together - kindness alone patronizes, clarity alone terrifies. Held flat: the entry-level analyst and the CITO get the same directness and the same respect. And curiosity leads, because this is not about me. It's about your people becoming the best they can be with tools I can hand them.

What I actually do

I never ask "are you worried?" - that forces a lie or a confession, and both entrench the fear. I lead with my stories, my experience, not argument: how this technology worked for me, how it makes my thinking sharper and my skill set broader. I widen the circle - what it can do for society, then for this organization, then for the person in front of me. And I reframe the dream: everyone already knows how to play what-if-I-won-the-lottery. Jensen Huang asks a version of the same question - with infinite resources, what would you do? People are practiced at this kind of dreaming.

The method, first weeks at yours

Audit access before assuming reluctance - hidden doors and baroque seat-request processes suppress more adoption than fear does, and I find them by walking the path your newest user would walk. Survey as outreach, not measurement: every respondent gets a personal follow-up, and what they report becomes the curriculum. Befriend the keyholder - the admin who controls seats and settings - because unblocking runs through relationship. Every first session ends in a working win on the person's own accounts: plumbing first, magic scheduled last, so the first hour closes in capability instead of homework. Seed one shared, self-serve knowledge project and let departments request their own - pull scales, push doesn't. Instrument everything: a pipeline of every contact, so nobody who raises a hand is dropped. Lastly, run it like an internal sales job - opt-in adoption is a series of closed deals.

The sequence that makes it stick

Runbook, then agent, then work - in that order, because you can't hand work to a machine you've never described to yourself. First make the work legible: what fills your day, what's systematizable, what requires judgment. Then agenticize, with the person doing the cognitive work of specification before anything is built. Then the step most rollouts skip, and the reason savings usually evaporate: the person who did the work authors what the freed time is for. That last step is also where the fear finally resolves - not with reassurance, but with authorship.

Now that the boring parts are automated: what cool things do you get to do?

The graduation signal

When they stop calling, it's usually a good sign. I check in a week and a half later anyway - and the ones who've graduated don't ask questions, they show off what they built. Before I leave, the momentum gets a home that isn't me: builder communities, lunch-and-learns, an org-specific hackathon - because systems transfer to named owners, but momentum only transfers to community.

The goal

Stated to HR in my first week at my last engagement, in writing: my goal is that you no longer need to pay me. Everything above is engineered toward my own unnecessariness - which is the only honest definition of enablement.

The conviction

Fearlessness is a qualification in this work - you cannot treat a fear you share, and a steady person in the room is the first evidence that the other side exists. I build relationships by being authentic, because the fear detects performance instantly. And beneath all of it: respect, curiosity, and a real belief that this technology, rolled out with deliberation and democracy - thinking before building, nobody compelled, everyone asked, each person authoring what their freed time is for - will change our world for the better.

The system - the three movements this method runs on, with the instruments named - is here: Fieldwork.

The case study - a regulated-industry engagement, with figures - is available on request: kathleen@prodigalparadigm.com.

The longer argument - about what counts as work, who gets to author the margin, and why counting is protection - is an essay: What Counts.