The pattern I've been seeing across the consulting work this summer is that AI adoption at mid-sized companies stalls at almost exactly the same point every time, and the point of failure is almost never where the leadership team expects. The actual block is upstream of the tooling and the training budget. Nobody has done the operational mapping that would tell them where to point AI first.
I've been doing one-hour sessions with operators who are trying to figure this out. The question they walk in with is almost always some version of "we need to adopt AI, where do we start." The question I ask back is "where is the operational slack in the business right now." Those two questions produce completely different conversations.
The failure point isn't the tools
Companies with the budget to adopt AI have access to the same tools everyone else does, so the procurement question is usually already handled. The real struggle is figuring out which of their internal processes are structured well enough to benefit from automation and which ones would just produce more garbage faster, and most of them haven't done that audit.
Leadership often misreads this as a technical skill gap on the team, when the actual gap is about direction. The team doesn't know which workflows to point the tools at, which is a different problem than them not being able to use the tools. The fix for a skill gap is training. The fix for a direction gap is an outside perspective that can read the business as a whole and tell you where the leverage actually lives.
The map is the deliverable
The output I've been building in these sessions is a map. Not a vision deck or a transformation roadmap. A ranked list of five or six places in the business where AI would produce real leverage, with concrete first steps for each one, written in the client's own terminology so their team can actually act on it.
The map is also the thing that gets internal buy-in moving, because it gives the leadership team something specific to point at when they're explaining to the rest of the organization why AI matters for their business. "We're adopting AI" is a sentence that doesn't commit anyone to anything. "We're starting with these three workflows in operations because they're bleeding time and the tooling is mature" is a sentence that gets people on board.
The adoption problem isn't really about strategy theater at the top, which is a related but different issue. It's about the absence of a concrete first move that the whole organization can see and get behind.
An hour is enough to get there
The thing that surprised me about this format is that an hour is actually enough. You don't need a four-week engagement to produce a credible map, you need the right questions structured well, with somebody on the other side of the table who's been doing this work across enough different industries to recognize the patterns. The clients who have been getting the most out of this show up with their messy operational reality, not a polished version of it.
If AI adoption has stalled somewhere in your organization and you want an outside read on where it's actually stuck, that's one of the sessions I'm running most of right now. One hour, thousand dollars, playbook in your inbox the next day. You can book one through the contact section of this site.
