The Room

The Leadership Layer · Readiness

It was my first week, and the tool was already dead.

Someone had bought it. Someone had launched it. A whole team had been told this was the thing that would finally let them keep up with the work. By the time I arrived, it sat there unused, the way a treadmill sits unused. Not because anyone decided to stop. Because no one had ever really started.

I asked what happened. The answer came slowly, and then all at once.

The first thing I learned was that the people who were supposed to use the tool had never been in the room. Not when it was chosen. Not when someone decided how their work would change, where it would happen, which parts of their day would look different by Monday. The decisions about their jobs got made in a room they were never invited to. Then the finished thing was handed to them, and everyone acted surprised when they set it back down.

The second thing I learned was quieter, and worse.

The technical team had said, before launch, that they could not move the data the way the new system required. Not “we would rather not.” Could not. The old information lived in one place. The new tool expected it somewhere else, on rails that did not exist yet and that no one had been given time to build. They put it in writing. They said it in the flat, specific language of people who fix things for a living. And the people who could have slowed down to hear it had left no room in the plan to hear anything.

So the concern went into a document. The document went into a folder. The launch went ahead on schedule.

· · ·

Jeff Hiatt spent the back half of his career on a single, stubborn observation. Organizations do not change. People do.

It sounds like a slogan until you sit with it. A company cannot adopt anything. Only the individual people inside it can, one at a time, each on their own clock. What we call organizational change is just the sum of a few hundred private decisions to work differently than you did yesterday. Miss enough of those private decisions and the change you announced never actually happens, no matter how good the thing you bought.

Hiatt’s other contribution was to map what one of those private decisions actually requires. Before a person genuinely takes on a new way of working, they have to understand why it is happening. They have to want it, or at least not fight it. They have to know what to do differently. They have to be able to do it, with the time and the tools and the skill the change demands. And then it has to be reinforced, or they quietly drift back to the old way the first week things get busy. Skip any one of those and the person stalls. Enough stalled people is a dead tool on a shelf.

Read my first week back through that lens and the failure is almost embarrassing in its clarity.

The people expected to use the tool were never made to understand why. They were never asked whether they wanted it. They were never taught what to do. They were handed the finished thing at the very last step and expected to already be standing there. And the technical team had the skill but not the capacity. They were able in every sense except the one that mattered, which was time. Nobody reinforced anything, because nobody had built a way to hear that it was breaking.

Here is the part of Hiatt’s work that people tend to skip. His careful sequence only helps an organization that is actually willing to run it. Do it as a checklist inside a place that has already decided, quietly, that the date matters more than the truth, and all you produce is paperwork. A folder full of readiness that was never real. The plan assumed nothing would go wrong, which is the one assumption a plan is never allowed to make.

So the honest question was never whether the organization finished its readiness steps. It was whether the organization could tell itself the truth about what it was not ready for.

· · ·

Nobody in my first-week story lacked ambition. Nobody lacked budget. They had the tool, they had the plan, they had the date on the calendar. What they never did was take the inventory.

That is not a niche failure. Deloitte surveyed more than three thousand leaders across two dozen countries this year and found that access to sanctioned AI tools had climbed from under 40 percent of workers to around 60 in a single year. The readiness of the people expected to use those tools did not climb with it. Only about one in five leaders said their workforce was highly prepared. The appetite scaled overnight. The readiness stayed exactly where it was.

Willingness is a feeling. Readiness is an inventory.

They never asked the team what it could hold and what it would have to put down to make space for a new way of working. They never asked the technical people what could actually be built in the time that existed, on the systems that actually ran. They mistook the wanting for the being ready. In a planning meeting the two are identical. The week after launch they stop being identical.

I would like to tell you I learned that by watching other people fail. Mostly I learned it by doing it myself. I have stood in front of a team that wanted a change so badly I could feel it in the room, and I have called that readiness, and I have been wrong. Wanting is loud. It fills the space. It is very easy to mistake for the quieter thing, which is an honest account of what you can carry right now and what you have to set down first.

· · ·

The organization in that story did what organizations do. It blamed the tool. It started looking for a better one.

The next tool will be better. It usually is. That was never the question.