The Agentic Age

The lobby screen changed every eight seconds.

First, a photograph of two women seated across a table, one with a folder open between them, both leaning in as if the conversation mattered.

Then the line:

We make hard transitions human.

Then the numbers.

Average transition cycle time down 31 percent. Routine case handling capacity up 42 percent. Employee satisfaction holding at 4.7. Escalations down 18 percent.

The last slide showed a soft blue ribbon around a single word.

Modernized.

Maren Castellano stood in front of the screen with her visitor badge still warm from the printer. She watched the loop twice because the receptionist was on a call and because the screen had been placed exactly where a visitor had no choice but to look at it.

The numbers were good.

Good in the clean, defensible way executives liked, the kind of good that could be carried into a board meeting without apology or context.

The receptionist ended the call and smiled.

“Ms. Castellano? Gerald’s ready for you.”

Maren followed her through the glass doors and into the main floor.

It looked like every firm that had learned to make difficult work look calm, all low sound and neutral carpet and frosted glass, with small plants that had clearly been chosen by someone who understood that nothing in a place like this should look too alive or too dead.

At the far end of the floor, a cluster of people stood around another screen. Someone had brought pastries. Someone else had printed a one-page scorecard and taped it crookedly to the wall, which made the celebration feel less official and more sincere.

A woman in a navy cardigan stood a little apart from the group. She looked at the scorecard, then at the people around it, then down at the folder in her hand.

Only for a second.

Then she stepped away.

Maren watched her go, without quite deciding to. There was nothing to read into it, a person leaving a party a little early, and Maren had no reason to give it weight and did not. But her eye followed the woman anyway, the way it sometimes settled on the one still figure in a room full of motion.

The receptionist kept walking.

“Everyone’s been excited you’re here,” she said. “Gerald said this is the fun kind of consulting.”

Maren looked back once more, but the woman in the navy cardigan had already turned the corner.

“The fun kind,” Maren said.

The receptionist laughed because she thought Maren had made a joke.

· · ·

Gerald Voss met her outside the conference room with both hands extended, as if they had known each other longer than the email chain allowed.

“Maren. Good to meet you.”

He had the easy warmth of an executive who did not need to prove he belonged in the building. Late fifties, open collar, good eye contact, no wasted motion. A man practiced at making other people feel that whatever concern they brought him had already been welcomed and contained.

“Nice meeting you, Gerald,” she said.

“I've heard very good things.”

“That usually means someone wants something difficult made simple.”

“That's exactly what it means,” he said, and opened the conference room door.

Three people were already seated inside, and Maren knew all three from the coordination calls, the flat grid-of-faces version of knowing that turns strange the first time you are in a room together. Ruth from finance had her laptop open and two printed packets squared off in front of her. The transformation lead she had spoken with twice and had only met as a name and a slightly frozen video tile until now. The operations lead reached for the coffee and said something easy about the parking, more at ease in person than his quiet on the calls had suggested.

Gerald took the chair nearest the screen but did not sit right away.

“Before we get buried in slides,” he said, “I want to say plainly that this is a success story. We'ren't bringing you in to fix a failure.”

Maren removed her notebook from her bag.

“Good to know.”

“I mean that. The AI agent has done what we needed it to do. Better than we expected, honestly. It has been running the routine queue for the better part of a year now, and the numbers have held the whole way. The question now is how we reinforce the adoption, lock in the gains, and take the same discipline into the next function without losing momentum.”

He glanced at Ruth, who was already bringing up the deck.

“We handle sensitive workforce transitions for clients who can't afford to get them wrong,” Gerald said. “Reductions, exits, retirements, role changes. The work is high-volume, high-stakes, and expensive when everything has to be touched manually. The agent gave us breathing room.”

Ruth clicked once.

A chart appeared.

The line went the direction everyone wanted it to go.

“Our routine transition queue is moving faster,” she said. “The agent is handling the standard documentation sequence, deadline reminders, benefits continuation prompts, equipment return workflows, exit survey triggers, all the pieces that used to eat specialist hours. We'ren't replacing judgment. We're taking administration out of the way of judgment.”

It was the kind of sentence Maren had heard often enough to know it had probably been said in several rooms before this one. It was not necessarily false. The practiced quality only meant it had survived repetition.

Maren wrote:

Taking administration out of the way of judgment.

Gerald sat.

“That's the work we'd like you to validate.”

“Validate,” Maren said.

“And strengthen.”

“Those are different things.”

A small pause moved around the table.

Gerald smiled.

“That's why we brought in someone careful.” Gerald turned his coffee a quarter turn on the table. “We have a good internal team. They built this, and I'm proud of what they built. But they built it, which means they're the last people who can tell me whether it holds. And we're about to take the same model into three more functions, so before I put my name on that, I want someone who does adoption for a living, from outside, with nothing to protect, to tell me it's as solid as the numbers say. If it is, you strengthen it, and we scale it with confidence. If it isn't, I'd rather hear it from you now than from a client later.”

“You have twelve weeks,” he added. “I didn't want to give you a number so small it forced a shallow answer. Take the time to look. Talk to whoever you need to. If it holds, I want to be able to say it held under someone who tried to break it.”

Maren looked at the screen. The numbers were still good.

“Where do you want me to start?”

“Stakeholders,” Gerald said. “Ownership, operating rhythm, adoption health. Whatever you normally need to understand the change environment.”

That was the first easy thing anyone had said all morning.

Maren turned to a clean page.

· · ·

She always started with ownership.

People liked to start with readiness because readiness sounded generous. They liked to start with communications because communications produced visible artifacts. They liked to start with resistance because resistance made the problem feel locatable.

Maren started with ownership because every consequential change produced the same first question.

Who had the authority to decide what this was?

Not who approved the budget. Not who signed the vendor agreement. Not who sent the launch email. Those were useful names, but they were often not the answer.

The owner was the person who could say, this is the intended shape of the work now, and be believed.

So, she drew the first box at the top of the page.

Accountable owner

She left room under it.

“Gerald,” she said, “who owns the agent?”

He looked pleased to receive a question with an obvious answer.

“Operationally, I do.”

Maren wrote his name, then did not underline it.

“Operationally, meaning performance?”

“Performance, budget, productivity, the business case.”

“Who owns the design of the transition experience?”

“The experience itself sits with the transitions function.”

“Under you?”

“Yes.”

“Who owns the workflow logic?”

Gerald turned to the operations lead.

“That would be your team.”

The operations lead set his coffee down.

“We own the process maps,” he said. “The agent configuration is maintained with IT, but the maps are ours.”

Maren wrote:

Ops: process maps IT: configuration

“Who decides when the agent shouldn't handle a case?”

The operations lead blinked once.

“There are escalation rules.”

“Who owns the rules?”

“Initially? The implementation team built them from existing case types. Legal reviewed the language. Transitions reviewed the templates. IT configured them.”

“Currently?”

He looked at Gerald.

Gerald leaned forward.

“Currently, if something needs to change, operations would raise it and IT would update the configuration.”

Ruth added, “Depending on whether it affects controls.”

Maren wrote:

Controls: Ruth? Legal?

Ruth saw the question mark.

“Finance doesn't own controls,” she said. “We validate the savings and watch the performance case. Legal owns legal risk. Operations owns operational controls.”

The operations lead gave a small nod, as if he didn’t fully accept the transfer.

Maren kept writing.

“Who sponsored adoption with the specialists?”

The transformation lead answered this one.

“We supported enablement.”

“Supported.”

“We built the manager talking points, office hours, quick reference guides, adoption pulse. The functional leaders handled team reinforcement.”

“Who was accountable for whether the specialists changed how they worked?”

Another pause.

Not long.

Long enough.

Gerald said, “Their managers.”

The transformation lead said, “The function.”

The operations lead said, “We treated it as a workflow change, not a behavior change.”

Ruth did not say anything.

Maren looked at the first box again.

Gerald’s name sat there lightly, in ink she had not committed to.

· · ·

The celebration on the floor broke up around eleven.

Maren watched it through the glass while Ruth walked her through savings. Ruth was precise and not defensive, which Maren appreciated. Some finance people used numbers as a wall. Ruth used them as flooring. She expected you to stand on them without asking whether the ground existed.

“The labor capacity gain is real,” Ruth said. “I know that's often where consultants start poking.”

“Depends on the consultant.”

“I've had experience with the species.”

“Fair.”

Ruth allowed herself a small smile and returned to the spreadsheet.

“We took a conservative view. We didn't count every minute the system claimed to save. We backed into actual queue movement, specialist load, overtime reduction, cycle time. The savings hold.”

“I'm not challenging the savings.”

“Not yet.”

Maren looked up.

Ruth met her eyes.

There it was again, the look of someone who had heard a sound in another room and was waiting to see whether anyone else would mention it.

Maren wrote nothing.

Gerald came back in with fresh coffee and the practiced ease of a person who had not noticed the temperature change or had noticed and chosen warmth as the remedy.

“Ruth is our conscience on the numbers,” he said.

“She seems effective.”

“She is terrifying.”

“Only recreationally,” Ruth said.

Gerald laughed. Ruth did not, but she did look pleased.

The room relaxed.

That was what Gerald did well. Maren could see it already. He made pressure feel like a shared project rather than an accusation. He would have been easy to trust, and that made him harder to assess.

He leaned against the credenza.

“What are you seeing?”

“It's early.”

“That bad?”

“That early.”

He accepted the correction with a small lift of his hand.

“Fair.”

“I'm trying to understand the decision path.”

“The decision path.”

“For the agent.”

Gerald nodded as if the phrase made sense and waited.

“When did the firm decide that this was the new default for routine transitions?”

Ruth looked back at her laptop.

The operations lead, who had stayed for this part and had been pretending not to read email, stopped pretending.

Gerald took a sip of coffee.

“Well,” he said, “that makes it sound more dramatic than it was.”

Maren waited.

“It started as a capacity solution,” Gerald said. “We had volume pressure, the vendor had a workable agent, the process maps were mature, and the first use case was narrow. Standard documentation support. Nobody was putting sensitive judgment into the tool.”

“Narrow pilot.”

“Yes.”

“Who approved the pilot?”

“I did.”

Maren nodded.

“Who approved the move from pilot to default?”

Gerald looked at the operations lead.

The operations lead said, “There wasn't one move.”

Maren turned to him.

He seemed relieved to have the more accurate sentence in the room, then immediately less relieved to be responsible for it.

“We expanded by case type,” he said. “Clean retirements first. Then the standard exits. Then reductions under a certain complexity threshold. Each expansion had a review.”

“By whom?”

“Ops, IT, legal where language changed, finance where volume assumptions changed.”

“Transitions specialists?”

“They were in the pilot feedback sessions.”

“In the expansion decisions?”

He hesitated.

“Their managers were.”

Maren wrote that down.

Gerald came in gently.

“The specialists were using it, Maren. Enthusiastically. That was one of the reasons we kept going. There wasn't resistance to overcome.”

“I didn't ask about resistance.”

“No, I know. I'm saying the adoption was strong from the start.”

Ruth closed one tab and opened another.

The operations lead said, “People liked getting the routine work off their desks.”

“Of course,” Maren said.

She meant it.

That was what made the room difficult. Each answer had a local logic to it, and none of the people giving them sounded careless or vain. The agent had entered through the part of the work everyone agreed was waste, then stayed because it helped, then grew because the next adjacent use made sense, and by the time the firm had a new operating model, there had been no single moment large enough to name.

Maren looked at the first box again.

Accountable owner

Gerald’s name still sat there.

Not wrong.

Not enough.

She looked back over the page. Every box on it held a person or a team. Owner, operations, IT, legal, finance, the managers. It was a good map. It was the map she always drew, and it had never failed her.

Something about it sat wrong, and she could not yet say what. The page accounted for everyone who had decided things and everyone who ran them, every box a person who could be asked a question and answer for a choice. It was complete by every standard she trusted. That was the part that sat wrong, though she could not name it. The thing at the center of the whole rollout, the one that decided which message went to which person and when, had no box, because in eleven years of drawing these maps she had never once needed a box for something that was not a someone. She turned to a clean sheet and let it go, the way you let go of a word that will not come, believing that it will eventually come back.

· · ·

At lunch, Maren took her sandwich to a small table near the windows and opened the implementation archive.

The folder structure told a story before the documents did.

Pilot materials. Training. Templates. Controls review. Phase 2 expansion. Manager cascade. Metrics. Closeout.

There was no charter in the root folder.

She searched for one and found three documents with the word in the title, none of them the charter. One was a vendor onboarding checklist. One was a procurement file. One was a two-page summary created after the pilot had already been extended.

She opened the summary.

The language was clean and retrospective.

The pilot demonstrated meaningful queue relief. Specialist feedback indicates strong usability. Recommended path: expand use of the agent across additional routine transition profiles while monitoring quality, escalation rates, and satisfaction.

Maren read the sentence again.

Specialist feedback indicates strong usability.

Not support. Not readiness. Not a judgment that the work should move.

Usability.

She highlighted the sentence and added a note.

Then she opened the feedback appendix.

Most of it was positive, and nearly interchangeable.

The agent is easy to use. The agent saves me time. The workflow is clear. I understand when to escalate.

She scrolled.

There were comments.

Some were grateful. Some were minor complaints about field labels and duplicate reminders. One person wanted better filtering. Another asked whether the tone library could be expanded.

Near the bottom, one comment ran longer than the field seemed designed to hold.

Some cases look clean in the system but need a second read before the first message goes out. Not sure where that fits here because the agent is working as designed.

There was no name attached in the export. Only a team code.

Maren copied the comment into her notes.

A shadow fell across the table.

The woman in the navy cardigan stood beside her with a paper cup in one hand and a folder tucked under her arm. Up close, she was older than Maren had first guessed. Early fifties, maybe. Calm face. Tired eyes.

"Sorry," the woman said. "I usually get this corner to myself around now. I didn’t mean to sneak up on you."

"No worries."

The woman's eyes went to the screen. Not long enough to read the file. Long enough to recognize the folder structure.

"I can take one of the others," she said.

Maren smiled and leaned back to make room. "You don't have to."

A younger woman appeared behind her, carrying a laptop and looking at the hallway as if still learning which direction meant what.

“Priya,” the younger woman said, “do you've a second?”

Priya.

Maren wrote the name down.

Priya turned.

“What happened?”

“It's probably nothing. The agent queued a standard exit for Eastland. The employee asked about benefits, but the note says retirement packet, and I think that's because of the age field.”

Priya set the paper cup down.

“Did you send it?”

“No. I remembered you said to look further if the question doesn't match the packet.”

Something in Priya’s face changed so quickly that Maren might have missed it if she had not been watching.

“Good,” Priya said. “Show me.”

The younger woman opened the laptop on the table, then glanced at Maren.

Priya closed it halfway.

“Not here,” she said gently. “Come on.”

They left with the laptop between them, the younger woman already explaining as they walked and Priya listening without interrupting.

Maren looked back at the anonymous comment on her screen.

She wrote:

Priya?

Then she closed the appendix.

· · ·

By midafternoon, Maren had enough names to make the map ugly.

That was not unusual. Good stakeholder maps were ugly before they were useful. She knew from experience that the clean ones were usually political documents posing as diagnostics.

She had Gerald under business performance. Ruth under financial validation. Operations under process maps. IT under configuration. Legal under approved language. Transformation under enablement. Functional managers under reinforcement. Specialists under usage. The vendor sat off to the side in a box she had not connected yet because everyone described them as both central and finished.

She stared at the page.

It had many names.

It did not have an owner.

The distinction irritated her because she had made a career out of insisting on those distinctions and because this one should have been easy. The agent was already live. The firm had already celebrated the result. There were dashboards, guides, controls, savings, and enough governance artifacts to satisfy almost anyone trying to prove that governance had occurred.

Still, the first box would not fill.

She went back through her notes and tried again.

Who could change the operating premise?

Not IT. They could configure what they were asked to configure.

Not transformation. They had supported the rollout and moved on.

Not finance. Ruth could validate savings and challenge assumptions, but she could not say what the work was supposed to mean.

Not legal. Legal could approve language, not define care.

Not the managers. They had inherited the model as it became normal.

Gerald could stop it. Gerald could fund it. Gerald could defend it.

But Gerald had not quite decided it, not in the way Maren meant.

He had approved reasonable expansions, each one attached to a number that got better and a team that seemed relieved.

The decision had happened in pieces.

Maren looked at the wall clock.

Three fifteen.

Her first day on the engagement, and the most basic question still had no answer.

Who owned the agent?

No.

What sequence of reasonable approvals had allowed the firm to stop needing an owner?

The question sat wrong with her.

It was too early for that kind of question.

She wrote it anyway.

· · ·

Gerald found her in the borrowed office just after four.

The room was meant for visiting clients. It had a small table, a wall monitor, two chairs, and a framed photograph of a lighthouse that had almost certainly been purchased in bulk. Maren had spread her notes across the table and was standing over them with a pen in her hand.

Gerald knocked on the open door.

“I promised myself I'dn't hover,” he said.

“You made it almost six hours.”

“A personal best.”

She smiled as she capped the pen.

“Come in.”

He did, but he stayed near the door.

“How was the first day?”

“Useful.”

“That's one of those words consultants use when they've decided not to say good.”

“It was useful.”

He nodded toward the papers.

“Stakeholder map?”

“Yes.”

“How ugly is it?”

“Normal ugly.”

“That sounds survivable.”

Maren considered him.

Gerald looked genuinely amused. Genuinely curious. Not afraid. Not managing her, at least not more than any executive manages a person brought in to produce a finding.

She could have given him the easy version. It was day one. The easy version would not even have been dishonest.

Strong adoption. Clear business case. Mature metrics. Ownership model needs tightening before expansion.

That sentence would have carried them both safely into tomorrow.

Instead, she looked down at the page.

“I can map who touched it,” she said. “I can't yet map who decided what it became.”

Gerald’s smile did not leave his face, but it stopped moving.

“That may be a distinction without much practical difference.”

“It may be.”

“You sound like you don't think it is.”

“I think I don't know yet.”

He came farther into the room and looked at the papers without trying to read them.

“The decision wasn't careless, Maren.”

“I'm not assuming it was.”

“Good. Because I'd push back hard on that. The team did good work here.”

“I believe that.”

“The savings are real.”

“I believe that too.”

He studied her then, perhaps hearing what was not being challenged and disliking the shape of the space around it.

“So, what’s bothering you?”

Maren uncapped the pen again, not because she needed it but because her hand wanted something precise to do.

“When a change is this consequential, I expect to find a moment where the organization chose the new shape of the work. I haven't found that moment yet.”

Gerald took that in.

Outside the office, someone laughed near the elevators. The sound came through the glass, thin and bright.

“We chose it,” he said. “We just may not have chosen it in the form you're looking for.”

That was the best answer he could have given.

It was also the one that made the empty box harder to ignore.

Maren nodded.

“Maybe.”

Gerald tapped the doorframe once.

“Tomorrow, let’s get you closer to the teams. If there's texture we're missing, they will have it.”

“They usually do.”

He smiled again, this time with less ease.

“I still think this is the fun kind.”

Maren looked at the map.

“I hope you're right.”

· · ·

After he left, she stayed in the office until the floor thinned out.

The celebration scorecard had been removed from the wall, but a piece of tape remained behind, curled at one corner.

Someone shut down the lobby screen. The last blue light disappeared from the glass.

Maren packed slowly.

She put the savings packet in one folder and the feedback appendix in another. She took a photo of the stakeholder map, then looked at it on her phone because sometimes the distance of a screen made a pattern easier to see.

The first box was still empty.

Not because there had been no governance.

There had been plenty.

Not because no one cared.

Several people clearly did.

Not because the agent had failed.

By the measures she had been handed, it had succeeded.

Maren sat back down.

The phrase at the top of her original notes no longer fit.

Optimization assessment

She crossed it out.

Underneath, she wrote:

Ownership reconstruction

Then she stopped, pen still touching the paper.

This was not the engagement she had been told it was. She sat with that for a moment, and with the smaller, quieter fact underneath it, which was that some part of her had known it before lunch and had kept writing anyway.