What the Moment Actually Asks of Leaders

Legal teams grapple with a developing state-by-state patchwork of AI regulation, builders demonstrate what autonomous systems can do, and the demonstrations are impressive. People leaders ask who answers when those systems do something wrong, and the silence is instructive.

I spend a good amount of time interviewing practitioners, academics, i/o psychologists, compensation advisors, people chiefs. As these conversations veer in different directions, one thing becomes obvious. The distance between them has an organizational cost, and closing it is a leadership job nobody has formally been given.

The Pattern Under the Patterns

I find conferences to be a useful barometer of where things are in terms of both hype and reality. Vender expos pump hype with well rehearsed demos and details that aren't actually details, but sales team bullet points off a one sheeter worded differently depending on who you talk to.

In all, I reported more than a dozen stories that came out of four different conferences last quarter. Read the evidence in one sitting and a single structural fact emerges.

One AI governance vendor founder says her organization has catalogued roughly 1,600 AI risk categories, and uses mitigations for about 85% of them. That is the state of the art, and it still leaves hundreds of known risks without an answer.

Meanwhile, most enterprises are working from governance frameworks designed to review recommendations made by AI, not actions taken by it, even as they put agents to work.

Enterprise trust programs are maturing quickly on the vendor definition of trust, the kind that lives in security audits, while the concept of employee trust in AI in general seems less of a concern. Some are still concerned that using AI will be seen as cheating or an indictment of their intelligence, something that simply cannot be reconciled with mandates.

In rooms full of HR practitioners, conversations around who owns AI literacy in their organizations have been rampant. I'd love to say there's a signal of consistency, be it by industry, by the ever changing titles of C-suite leaders, by company size, something. Where studies and surveys provide neat data and smooth talking points, the conversation reality most leaders report is about as consistent as your average customer experience.

The recipe for that inconsistency though, has a common element. Brandon Hall Group found 65% of organizations are actively integrating AI into core workflows while fewer than 30% have redefined roles to reflect it.

In recruiting, the signal itself is collapsing, with some ATS platforms reporting 750 applicants per opening, review rates near 2%, and, by one AI recruiting platform founder's estimate, one in four applicants fraudulent.

And Saahil Jain of You.com offered the bluntest number I've heard. When his company automates a process for an enterprise customer, roughly 60% of the people doing that work are no longer required, about 12% can be reabsorbed supervising the AI, and the remaining 48% represent a transition problem most organizations have not solved and few even want to talk about.

The people carrying that risk are concentrated in the middle. Kyle Holm, who advises companies on compensation at Sequoia Consulting Group, described the shape AI-native companies are already taking with experienced operators at the top, highly capable junior talent underneath, and very little in between.

"These management organizational hierarchies, they're just gonna go away in a way that I don't think folks are necessarily ready for," he told me.

The middle of the org chart is where careers were built and coordination lived. It is thinning in real time while most readiness programs still treat the transition as an individual skills problem.

Each of these was reported as its own story, but they are all part of the same story. The builders have detailed frameworks for making systems reliable. The practitioners have detailed frameworks for making people adaptable.

Between them sits the organizational tissue that would connect the two. The runtime oversight, the watching of seams across the people stack, the redeployment architecture for the 48%, the named owner of what the agents did last quarter. In most companies that tissue does not exist, and building it is nobody's assigned job.

Committees are not tissue. Gartner finds 55% of organizations now have an AI board or oversight committee. In only 28%, per McKinsey, does the CEO take direct responsibility for AI governance, and 17% of boards have written it into their charters.

The governance committee is not present for the split-second decision someone makes at 2 a.m. The prescription from Vittoria Reimers at Juniper Squared was to spend ten times more on your people than on your committee. That ratio should sting. Reverse it and you have most companies' current budget.

What This Asks of You

Not another framework. The seven capabilities we've documented previously, empathy, presence, product thinking, courage, strategic patience, transparency, and systems thinking, describe how leaders show up under uncertainty. What the spring added is where they have to show up, in the connective layer.

It asks you to put some verbiage to it. A person, with budget and authority, accountable for what your organization's AI does to the people inside and outside it. Because "owned everywhere and accountable nowhere", the default Sean McIntire from Pebl described at Transform, is a legal strategy for defendants.

It asks the CHRO to take the seat rather than wait for it. AI implementation is a workforce event. The skills, the psychology, the learning architecture, the behavioral context that generic models will never carry, this is the people function's material.

This is why HR belongs on the AI council beside the CIO and CFO at the moment decisions get made, not downstream managing the fallout.

It asks you to answer for the 48% before you automate, not after. If you can name the process you intend to hand to agents, you can name the people in it. Whether they transition depends far less on their personal adaptability than on whether you built somewhere for them to go.

Oracle almost certainly had adaptable people. What it apparently lacked was a system for finding them and developing them at the speed the transition required, and that was a choice.

It asks you to decide what performance means before your systems decide it for you. Kamaria Scott, founder and CEO of Enetic, put the question that every evaluation process will soon face.

"How are you now going to evaluate my performance as a person for work I'm not even doing fully myself anymore?"

If your answer is a usage metric, you will get usage. You will not get judgment, and judgment is the thing you'll be paying for.

It asks you to know how work actually happens in your organization before you let a system redesign it. And it asks you to tell the truth in the meantime, separating what is certain (you are investing, some roles will change) from what is not (exactly which ones, and when).

Ambiguity is exhausting. Your people are drawing their own conclusions in the absence of structure and transparency.

None of this is beyond the organizations reading this. All of it is slower than shipping and invisible at the analyst call. That is precisely why it is the work. The builders told us the truth this spring. They will keep shipping, the models will keep improving, and the learning will keep happening in production.

The workflows of your company are reorganizing around these systems right now. The window in which accountability can still be designed in, rather than litigated in, remains open. It will not stay open because you convened a committee.

When capability is commoditized, and it will be, what differentiates an organization is the judgment and trust of its people, both of which are built or destroyed by how you handle this transition. The moment asks you to build the one thing the builders can't, an organization where the technology answers to somebody.