A sales coordinator at a mid-sized service business spent forty five minutes every morning on a process that kept five teams moving. She knew whose plate was full and whose wasn’t. She knew things that weren’t written down anywhere.

Then the process got automated. Forty five minutes down to zero. Score one for the machine.

She was still there. Still showing up. But something had changed that no dashboard was going to capture. It wasn’t her skills. It wasn’t her commitment. What changed was her sense of what she was there for.

No implementation plan addresses this. No training module resolves it. And it doesn’t stay contained to her. It ripples outward. To her co-workers. To the clients she serves. Even to the firm that came in and changed things. And likely to the cultures of both companies as the work and results evolve.

This is the part of AI transformation that doesn’t have a dedicated owner yet. And it’s where most of the value is quietly leaking out.

Some leaders I’m working with are being asked to communicate a mandate they’re still absorbing themselves, support people who are struggling with something that has no playbook, and hold a performance line while also holding space for the very human disorientation their teams are feeling.

Leading people through hard change is part of the job. What’s different now is the scale, the speed, and that nobody has been through exactly this before. There’s no precedent to draw on. No senior colleague who navigated the same thing ten years ago. They’re figuring it out in real time while also delivering on everything else they’re already accountable for.

Even with the right HR support and training in place, the manager still has to be the one in the room. Nobody can have that conversation for them.

Every organization going through this has a version of the coordinator. The person whose competence just got automated. Whose morning ritual disappeared. Whose sense of value was quietly attached to the thing that no longer needs her in the same way.

Some of these people are excited. Some are struggling and want to get there but don’t know how. Some have quietly decided they’d rather leave than adapt. And some are so lit up by what the tools can do that they’re not sleeping, which sounds like enthusiasm right up until it becomes something else entirely.

Each situation calls for a different response. The person who’s struggling needs support and a real path forward. The person who’s decided not to move needs an honest conversation and eventually a clear choice. The person who’s burning out needs someone to pump the brakes before they flame out.

Most leaders know this. What they’re missing is the time, the preparation, and sometimes just the permission to have those conversations. And many of them are navigating their own place on that continuum at the same time, which brings its own ambivalence to everything they’re being asked to do. Nobody’s telling them this is part of the implementation. But it is.The coordinator’s still serving the people she’s always served. But she’s carrying something she wasn’t carrying before. And the people on the other end of those interactions feel it, even if they can’t name it.

Adoption rates? Check. Time saved? Check. Process efficiency? Check. What those numbers can’t catch is the slow erosion that happens when a team is technically compliant but emotionally checked out. That doesn’t show up in the metrics until it shows up in the business. And by then it’s a lot harder to trace back to where it started.

What I keep wondering is what the client experience looks like when the employee side gets taken care of too. Not as an add-on. Not as a training module. As a real and ongoing part of what it means to help people through something this significant. The people who feel well supported through a hard transition tell a different story afterward. Not just about what was built but about how it felt to go through it.

Hospitality figured this out a long time ago. The employee experience and the customer experience aren’t separate things. They’re the same moment, felt differently by the people on each side of it. A team that feels uncertain creates customers who sense something is wrong but can’t name it. A team that feels seen creates customers who just feel taken care of.

It took a few hard conversations, some honest reckoning about what she actually brought to the work beyond the process, and a manager who was willing to sit in the discomfort of not having easy answers.

The time the coordinator used to spend on the process she no longer owns is now spent on something she didn’t expect. Conversations that matter. Problems that need judgment. Work that’s harder to automate precisely because it requires knowing the people involved. She’s better at her job than she was before. Not because the tools made her better. Because someone helped her figure out what she was really good at.

There’s a principle in hospitality that the best guest and employee experiences often come from a problem that got handled well. The coordinator’s story is that. The disruption was real. What made the difference was what happened after.

Something else is happening inside these organizations that’s worth naming, because it’s easy to misread. People are building. Constantly. Enthusiastically. Often brilliantly. The tools make it possible to create things in hours that used to take weeks. That’s genuinely exciting.

But building has also become one of the primary ways people prove their value in this new era. And when proving value becomes the goal, the question of what should actually be built tends to get lost.

Solutions are being built for problems that weren’t really the problem. And there’s a growing pressure to keep up with what everyone else is building, not because the company needs it but because standing still now feels like falling behind. It’s the agentic version of keeping up with the Joneses. Just as exhausting. Just as hard to opt out of.

When the tools are this powerful and this fun, the discipline of asking whether something should be built can be harder than the act of building it. Right now the people best positioned to ask are often too caught up in the momentum to stop and check in. And the humans inside all of it are doing what humans do: adapting, struggling, burning out, and occasionally finding something they didn’t expect on the other side of the change.

The coordinator found it. Not because the transformation was perfect. Because somebody decided this part of the work mattered.