The Agentic Age

The board packet reminded Maren of a sentence she had changed three years ago. The two cases were not connected, but they were the same shape, and the shape was one she had learned to recognize: a real finding made smaller until it could be agreed to. She sat at the kitchen table with her laptop open and Gerald’s board packet beside it, working the preliminary finding into a form she could send, and the earlier case came back to her because it was useful, the way a prior example is useful when you are trying to name what is wrong with the one in front of you.

On the screen was the sentence she had written that afternoon in the office.

She read the second sentence again.

She opened the old case file, the one from three years ago, and found the document she wanted. Forty-seven files inside. Current State Findings. Stakeholder Themes. Governance Recommendations. Executive Readout. Final. Final_v2. Final_Client. There it was: FINAL_Client_APPROVED.

She opened the document. The first seven pages didn’t matter. They were all competent, and that was the problem with competent documents. They could carry one sentence past a hundred people without anyone noticing that it had been made smaller.

She went to page eight and found the section. Operational Risk. The final sentence read:

Maren looked at it for a long time. Then she opened an earlier draft. The sentence there read:

She put both sentences side by side. On the left, the finding as it was first written. On the right, the finding as it shipped. The same case had produced both, and only one of them had survived the room.

· · ·

Three years earlier, Maren had not been independent. She had an office she rarely used, a team she didn’t choose, and a title long enough that people assumed she had more authority than she actually did. The client was a national services company implementing a workforce management platform across more than 200 locations. Scheduling, attendance, leave, exceptions, all the ordinary administrative machinery that becomes consequential the moment it gets something wrong.

The project was late, and the client relationship was important. She remembered that the account partner had used the word important the way other people used the word dangerous. Maren had been brought in after the pilot because managers were overriding the new system too often. That was how the problem was described: managers are not following the standardized process.

She had interviewed them. They were following it, and that was the first problem. They were also fixing it. That was the second.

The platform applied the same attendance rules everywhere. Local managers had previously known which absences had approved context attached to them and which did not. They knew who was waiting on a leave determination, who had an accommodation under review, who had been told by one department that documentation was complete while another system still showed it as missing. The new process centralized the rules. The local managers kept intervening. The implementation team referred to the interventions as workarounds. Maren called them exception handling. At least, she did in the first draft.

Her evidence was not dramatic, just sixteen interviews and nine examples. Three managers who had kept their own spreadsheets because they did not trust the centralized queue to resolve pending exceptions before attendance actions triggered. No major consequences documented. Just nine cases that had gone wrong and been caught because someone local knew enough to stop the process.

The account partner read her draft in a conference room that was bathed in sunlight. He was not a bad man. This mattered to her even now. He read the whole thing, made notes, asked good questions. Then he tapped the sentence.

"Material risk of preventable employee harm."

Maren looked at him. "Yes."

"Walk me through the word harm."

"Nine people were about to be marked absent against approved leave. The managers caught it."

"So, the managers caught it."

"Because they still could. The design is removing the point where they can."

He nodded, a small, economical nod, already past the point where her answer might change anything. "Here is my difficulty. Nine cases, nine catches, no one harmed. You want me to put a sentence in front of the client that describes harm none of them can point to."

"The harm is what happens when the catch is gone."

"Which hasn't happened."

"Not yet."

"Not yet isn't a finding. Not yet is a forecast." He leaned back. “The recommendation is to strengthen the exception process.”

“The finding is that the current design removes the judgment that catches the exceptions.”

“That is a stronger statement.”

“It is also what happened.”

He nodded. He had not told her she was wrong, not directly. That was what she remembered: not the disagreement, the absence of one.

“We need to separate the finding from the implication,” he said.

“I have.”

“I don’t think you have.”

Maren waited. He turned the page toward her. “The client is twelve weeks from full deployment. They have executive approval. Labor planning is built around this. The relationship is bigger than this engagement.”

“I know.”

“I know you know.” He said it kindly. That had made it harder. “We should be precise,” he continued. “You can say the exception pathway needs strengthening. You can say local leaders need clearer escalation rights. You can recommend additional monitoring.”

“And the risk?”

“What has happened?”

“The nine cases.”

“Nine cases were corrected. Because managers did what the new process says not to do. And that's useful information.”

Maren looked at the sentence and said nothing, letting the silence sit. The account partner let it sit longer. He was good at waiting, too.

Finally, he said, “I'm not asking you to hide anything.”

“I didn’t think you were.”

“I'm asking whether we want to state as fact a consequence that hasn't occurred.”

Maren looked again at the sentence. Material risk of preventable employee harm. The word material was the problem. Then risk. Then harm. She could see them being challenged one by one. No quantified probability. No demonstrated impact. No loss. No claim. No harmed person. Not yet.

“What would you write?” she asked.

He did not answer immediately. That should have been the warning.

· · ·

Maren found the email. She had remembered the exchange. She had not expected it to still be sitting there, three years later, with her reply attached. The subject line was RE: Final Readout Language. The account partner had written:

Underneath, Maren had replied: Agreed. One word. She had seen the exchange for what it was even then, and had agreed anyway, because the case for agreeing was reasonable and the case against it was a forecast.

She closed the email and opened Gerald’s board packet. Modernized Operations: Scaling the Model. The draft recommendation was three pages. The first page described the success, the second the opportunity, the third the expansion. Her name did not appear. Her practice did with the role, external validation referenced twice.

Maren had seen documents like this all her professional life. No one had done anything improper. She had been hired to assess whether the model could scale. Gerald had asked for her honest read. The recommendation had been drafted before her assessment was complete, as organizations often draft materials before decisions are finalized. Preparation was not conspiracy. Confidence was not corruption. The numbers were not false. That was what made every part of it difficult.

She closed the laptop. The old report would still be there in the morning, and so would the new one. The question the account partner had put to her three years ago was the same one Gerald was putting to her now, and she had a better answer for it than she used to.

· · ·

Maren was at her desk by eight the next morning when the calendar reminder surfaced. Scale Readiness Meeting, 8:30. Attached materials updated.

Maren opened the updated deck. A slide had been added since the version she had seen the day before.

QUALITY CONSIDERATIONS

Recent external feedback indicates an opportunity to strengthen context-sensitive review protocols as the model scales.

She read it twice. An opportunity to strengthen. It landed the way the old sentence had landed the night before, and for the same reason. Consider strengthening local exception pathways. Three years apart, and the softening had found the same words.

At 8:26, Gerald was standing near the screen when Maren entered the conference room. Ruth was already seated. Daniel had three versions of the same deck open across two monitors. Tomas was reading the packet. Desmond was not there. Priya wasn’t either. Of course they weren’t, Maren reasoned. This was a scale-readiness meeting.

Gerald saw Maren and smiled. "Morning. Glad you're here."

"Morning."

"I wanted your read in the room today. Not the polished version. The one you'd give me if it were just the two of us."

"That, I can promise."

"Good. Then this may run longer than the calendar says."

She put her notebook on the table. The QUALITY CONSIDERATIONS slide was already on the screen. Gerald noticed her looking. “I tried to reflect yesterday’s conversation.” Maren nodded. “Not as a conclusion,” he added. “As something we need to address.”

Ruth looked from the screen to Maren. Daniel stopped typing. Gerald took his seat. “We aren't approving expansion today,” he said to the room. “I want that clear. We are deciding what would need to be true before I'm comfortable recommending it.” He looked at Maren. “That includes what we learned yesterday.”

Learned. The word was generous.

Maren opened her notebook. Gerald continued. “We have one public case that exposed a weakness in context handling. We have evidence that human review fell as confidence in the agent increased. We have a question about whether our quality measures are seeing the same thing our operating measures are seeing.”

Ruth said, “They aren't.” The room turned toward her. She did not look up from the packet. “The answer to the last one. They aren't measuring the same thing.”

Gerald nodded. “Fair.” He looked at Maren. “What would you change on the slide?”

Maren read it again. Recent external feedback indicates an opportunity to strengthen context-sensitive review protocols as the model scales. The sentence was not false. That was almost funny. She looked at Daniel. “Who wrote it?”

Daniel lifted one hand slightly. “I did.”

“From what?”

“My notes from Gerald,” Daniel said.

Gerald said, “From our conversation.”

Maren looked at the screen. “Would you use the word failure?”

No one moved. Gerald leaned back. “On the slide?”

“Anywhere.”

His expression changed slightly. Not defensiveness, attention. “I'd use it if that's your finding.”

“Is that what you heard yesterday?”

“I heard that one case failed a human standard our current measures don't capture.” Maren waited. “I also heard that we don’t yet know the scale.”

“That’s true.”

“And that we shouldn't invent one.”

“Also, true.”

“Then I'm trying to hold both.” He said it without challenge. Maren looked down at her notebook. She had not written anything yet. Gerald said, “Is the slide too soft?”

There it was. A clean question, a direct question, the kind the account partner had put to her three years ago in different words.

Maren looked at the screen. “Yes.”

Daniel glanced toward Gerald. Gerald kept his eyes on Maren. "All right," he said. "How would you write it?"

Maren picked up her pen. She did not use it. “The current model can classify a case as successful even when the service has failed the person.”

The room went quiet. Daniel looked at the slide. Tomas stopped turning pages. Ruth watched Gerald. Gerald continued looking at Maren.

“Can you support that?”

Immediately, Maren saw the sentence on a page. Can we support that? Maren heard herself answer as she had three years earlier, and decided to make a firmer choice this time.

She looked at him. “Yes.”

“You can support it?”

“Marcus Bell.”

“One case.”

“That establishes possibility.”

“It establishes occurrence.”

“All right.”

“It happened.”

“I'm not disputing that.”

“No.” She heard the sharpness in her own voice. Gerald heard it too. He lowered his voice. “What am I missing?”

Maren looked at the slide. “You asked how I'd write it,” she said. “That is how I'd write it.”

Gerald nodded slowly. “Then let’s put that on the slide.” Daniel’s hands moved toward the keyboard. Maren should have felt relief. She did not, because she knew what came next.

Daniel typed.

The sentence looked larger on the screen than it had sounded in the room. Gerald read it. Then he said, “What do we do about it?”

Maren did not have an answer, not yet. And the whole room could see that.

· · ·

The meeting ended at 10:17. The slide stayed. She should have felt something like relief, but mostly, she felt the question Gerald had left her with.

Her phone buzzed twice. She did not look. She could still hear Gerald. What do we do about it? The finding was the easy part. The finding followed by a course of action was the part that had given way three years ago, and it was giving way in the same place now.

Maren went back to her borrowed office and closed the door. She sat down and opened the old report again.

Three years ago, the softening had happened in a sentence, one line edited in a room. The managers were catching something the new design could not, and the rollout would remove the thing that kept the cases safe. That much she could name. What she had not been able to name was the rest of it: how many local decisions to preserve, which exceptions to formalize, how to keep manager discretion from drifting back into inconsistency, how to hold the value of standardization without automating over the exact knowledge that made the exceptions visible.

That was where the sentence had lost. Her finding had been stronger than her solution, and a finding without a solution is the easiest thing in the room to soften. The account partner had not needed to overrule her. He had only needed to offer language for the half she could defend and let the half she could not go quiet.

· · ·

Priya was eating yogurt at her desk when Maren found her. Priya looked up with a slight smile. “You look terrible.”

Maren returned the smile. “Thanks.”

“Sit. What’s happened?”

Maren pulled a chair over. “Do you remember the first time you raised your concern?”

Priya did not ask what it was. “About the agent?”

“The feeling you got about it.”

Priya looked at her for a moment. “Yes.”

“What did you say?”

“I don’t remember my exact words.”

“Approximately.”

Priya leaned back. "There was a retirement."

Maren waited.

"A real one," Priya said. "Nothing went wrong. The sequence was fine. The person was fine. The case was fine."

"But."

"But I read it afterward, and I'd have called first. Before the sequence went out."

"Why?"

"Something in the manager note. The way it was worded. She'd been there long enough that the automated version was going to read as the firm being glad to see the back of her." Priya turned the yogurt lid over. "It would have been a two-minute call. Nothing in the case required it. I just knew the message was going to land wrong, and I couldn't have told you how I knew, and I could not have told you it was worth stopping the queue for."

"Did you stop it?"

"That one, no. It was fine. It was probably fine." She looked at Maren. "That is the part I can't get out. I don't know if I read something real or if I'm a person who has spent nineteen years finding reasons to touch things."

“Hmm, that's difficult to present as an answer.”

Maren let that sit. Priya folded the yogurt lid in half. “I mentioned it in a check-in,” she said.

“To whom?”

“One of the implementation leads. Not Daniel. Before him.”

“What did you say?”

“I said the cases were going out without anyone shaping them for the person on the other end.”

Maren looked up. Priya laughed once. “Exactly.”

“What did they say?”

“They asked whether I was seeing errors.”

“And?”

“I said no.”

“Then they asked about complaints and rework?”

“Yep, and I said no.”

“How’d you leave it?”

“They wrote down that I was adjusting to the new workflow.”

Maren closed her eyes briefly. “I was adjusting to the new workflow,” Priya said. “That is the irritating part.”

“Both things can be true.”

“True.”

Priya looked toward the transition floor. “That is what I keep wondering about.”

“What?”

“Whether I really knew a case like Marcus was coming.” Maren said nothing. “Everyone keeps talking like I warned them,” Priya continued. “Desmond thinks I did. You think I did.”

“You raised it.”

“I said the cases were going out without anyone modifying them for the person on the other end.”

“What it sounds like you’re saying is, you were watching the cases lose the small adjustments. The change of tone, the different sequence, and the call instead of the message are the things a person did because they could tell what a specific case needed. None of that was a tracked step. So, when it went missing, there was nothing to point to. It came out as the cases felt off, and off isn't a finding.”

“Was it?”

Maren watched her. Priya’s voice changed. “Or did I just not like that the work could happen without me?”

That was a question worth considering. Maren had heard versions of it from experienced people in every transformation she had ever touched. Was my concern real? Or did I just miss being necessary? Usually someone else asked it for them. Priya had done the more difficult thing. She had asked it of herself.

“You liked the agent?” Maren said.

“I did. Still do. It took work off my plate.”

“You mentioned earlier that you wanted it expanded.”

“At first.”

“Based on what you’ve said, I don’t think you were protecting the old process. Because you weren't the only thing that disappeared.” Priya’s expression changed. Maren continued. “The manual touches fell. The catches fell. The review moved to flagged cases. And then a case the system didn't know to flag went through.”

“That doesn't prove I knew.”

“No, it doesn’t.” Priya looked away. Maren suddenly understood why that answer seemed to hurt. Not because Priya wanted to be right. Because being right too late was not the comfort people imagined.

“Maybe you didn’t know a case was coming,” Maren said. Priya looked back at her. “Maybe you felt it before there was any way to prove it.”

“That sounds nicer.”

“I mean the system required you to know before it would listen.” Priya was quiet. “And the thing you weren't noticing was the loss of how people found out,” Maren said. “You couldn't prove the consequence before the work that prevented the consequence was gone.”

· · ·

On her way back, Maren passed the training area. A young associate was walking two newer hires through a case on the wall screen, and her voice carried through the open door. “This one is a good example. The sequence handled it end to end, it closed two days early, and the satisfaction score came back green, so I flagged it as a model case for the training library.”

Maren slowed without meaning to. The case on the screen looked the way every case looked now. Closed, green, surveyed. Nothing on the screen could say whether it was a case that had needed nothing or a case that had needed Priya.

The associate advanced to the next slide.

At 12:46, Maren sat in her office and reopened the old report. She went to the tracked changes. The software still remembered every decision.

She clicked the change. A comment appeared in the margin.

Too strong given current evidence. It was a reasonable note. The finding was one she believed and could not fully prove, and against a client twelve weeks from deployment, a thing you believe but cannot prove is the thing that loses.

The softened version shipped, and the rollout scaled, and the thing she had named, cases going wrong because the people who used to catch them had been moved out of the path, stopped being a risk on a page and became a pattern in the field, enough of them across enough locations that such things get names and case numbers. So, she knew this shape. She had watched it once before and watched what it cost.

But three years ago the softening had needed a room. It had taken a partner, a conversation, a tracked change a person made and a person approved, a sentence somebody chose to make smaller and could, in principle, have chosen not to. There had been a place to argue, even if the argument lost. What she was looking at now had no such place. The agent did not soften findings in a meeting. It closed the cases before a finding existed, at a scale no room could review, and there was no sentence anywhere for anyone to change. The old failure had at least required people to look away from it. This one did not even give them the chance.

· · ·

At 1:20, her phone rang. Gerald. She picked up on the second ring.

“Hi, Gerald.”

“Do you have a minute?”

“Sure.”

“I wanted to check in after this morning.”

“That was a good meeting. A hard one, but a good one.”

“It was. I asked you a question you didn't have an answer to, and you didn't pretend to have one. I've sat through a lot of meetings where people did the opposite.”

“I can imagine.”

“For what it's worth, not having the answer yet is the honest place to be.”

“I appreciate that.”

“Do you?”

She almost laughed. “Sometimes.”

“I left the sentence on the slide.”

“I saw.”

“Daniel wants to turn it into three workstreams.”

“That sounds like Daniel.”

“I told him not yet.”

Maren looked at the old report on her screen. “Why?”

“Because I think you're going to tell me we're still describing the wrong problem.” She leaned back. Gerald said, “Am I wrong?”

“No.”

“All right.” He waited. Maren looked at the old report still open on her screen. “I need more time.”

“How much?”

“Not much.”

“For what?”

“To find out whether Marcus was the failure.” Gerald was quiet. “Or?”

“Whether Marcus was the first failure we can see.”

Another silence. When Gerald spoke again, his voice was careful. “That is a different finding.”

“Yes.”

“And if it's true?”

Maren looked at the sentence she had changed three years ago. “I'll tell you.”

Gerald did not answer immediately. Then: “Good.” The call ended.

Three years ago, she had lacked the standing to make a caution matter. This time she had it. Gerald had hired her to tell him the truth, had put her sentence on the slide over the softer one, and had said he would act on her recommendation. And the thing she was being asked to weigh was larger than it had been back then, not smaller. Three years ago, the system still had people in it, operators who could catch a case if someone let them. The agent had removed even that. The gap she had watched open then was wider now, and she was the one being asked whether to widen it further.

· · ·

Maren opened a new document. She typed Scale Recommendation. Then: Proceed with expansion subject to enhanced context-review controls. She stopped. The sentence looked reasonable. It was reasonable. She added: Recommended actions include refining exception criteria, reinstating targeted human review, and expanding quality monitoring beyond current operational measures. Also reasonable.

She read the paragraph. It was excellent consulting. Clear, balanced, actionable. No one could accuse it of alarmism. No one could say it ignored the savings. Gerald could take it to the board. Daniel could build workstreams. Ruth could cost the controls. Tomas could map the process. Everyone would have something to do.

Maren looked at the old report beside it. Consider strengthening local exception pathways during the next phase of implementation. Her hands came off the keyboard. She stood, walked to the window, came back, read the new paragraph again. The words were different. The sentence was the same.

She deleted it. Then she typed:

She stared at the line. Her pulse moved once in her throat. She added:

She stopped. The document was not a recommendation yet. It was not complete. It could not go to Gerald. It could not go anywhere. But for the first time all day, it reflected what she believed.

Maren saved it. The filename was Working Finding. No final. No version number.

· · ·

Desmond was not at his desk. Maren waited. At 4:38 she was still waiting. At 4:51, Tomas walked past and looked at her.

“He is in the corner room on four. The one with the bad blinds.”

“Thanks.”

Tomas kept walking.

She found him on the fourth floor, in a glass-walled room at the end with the blinds half down. Two laptops were open in front of him, and a folder of printed pages sat beside them. He looked up when Maren came in. Then he watched her close the door behind her, and something in his face adjusted. He set the pages down.

“I need everything you kept.”

Desmond looked at the spread of work in front of him, two things open that had nothing to do with any of this, and the third that did.

“I’ve been re-reading my own memos since Tuesday,” he said. “In between everything else, trying to work out whether I actually saw this coming or whether I’ve spent four days deciding I did.” He tapped one page. “Since the video, everyone in this building has settled on the story that I’m the man who warned them. And I’d like to know whether that’s true before I let anyone tell it to me.”

Maren said nothing.

“And now you close the door.” He almost smiled. “You’re going to tell me it was true. Which is the one thing I was trying to decide for myself.”

“I didn’t come to tell you that you were right.”

“No?”

“I came because I think we’re looking at Marcus as the point of failure.”

Desmond's expression did not change, but he leaned back in his chair.

“Is he not?”

“I don’t know.” She stayed by the door. “I think the failure might be that he’s the first one we can see.”

He looked at her for a long moment. Then he closed the two documents, one and then the other.

“Then you’re going to want what I kept,” he said. “Not the version that went into the project system. The version I held onto when I could see the rest wasn’t going to survive closeout.”

He stood.

“Give me a minute. It’s not something I keep on the shared drive.”

He came back with a slim folder, set it between them, and opened it the rest of the way. Printed decks with his handwriting in the margins, a memo stapled to the reply it drew, and beside them on the screen a directory of survey exports, screenshots, and email chains, page after page of things that had once existed between noticing and knowing.

“How much did you keep?” Maren asked.

“Enough that people stopped inviting me to meetings.”

She almost smiled. “Good.”

Maren took off her coat. Desmond looked at the time on his laptop.

“This’ll take a while.”

“I know.”

“You have somewhere else to be?”

Maren thought of the old report open on her laptop. The sentence before. The sentence after. “No.” She pulled out a chair.

She cleared the table first. Desmond watched her do it, then helped, both wanting to see the whole of it, hoping to finally uncover the real issue.

“We are building two lists,” Maren said. She took a sheet of paper. “The first is every place a human being used to look at a case before the first message went out. Formal or informal. Sanctioned or not. If a specialist held cases in a personal queue until she had read them, that counts.”

“That was most of them.”

“Then it will be a long list.”

“And the second?”

“Every signal those places produced. What a person saw, said, or logged when they caught something. Where it went. What received it.”

Desmond looked at the cleared table for a moment. “You’re rebuilding the baseline.”

“There wasn’t one that I could find.”

“That isn't usually the consultant’s job.”

“No,” Maren said. “It wasn’t anybody’s. That is how we got here.”

They worked. Desmond narrated where narration helped and stayed quiet where it didn’t. The material gave itself up out of order, and Maren sorted as she read, one pile for review points, one for signals, one for things that were neither but might matter anyway.

By 8:00, they had the first list down to eleven. Eleven places a case used to meet a person before the first message went out. Four of them appeared in no process document. The best of them, the one that had caught Denise Harmon, had lived entirely inside one specialist’s habit of reading the day’s queue before the floor filled.

“There's no revision history for a habit,” Desmond said, looking at the list. “That is the part I could never make land. Half of this was never designed. It grew. So, when the design changed, nobody decided to remove it. It just stopped growing.”

Maren held up one of his shadowing notes. “The third memo. When you softened it. What would you have needed to send the first version instead?”

Desmond did not look up. “A number.”

“Which number?”

“Any number. Cases caught. Judgment applied per hundred closures. Something with a denominator.” He set the page down. “I had a falling line and a feeling. You can't walk a feeling into a steering meeting. They ask what it costs, and you say you'll know when it's too late to matter, and then somebody thanks you for the input.”

“And nobody was counting the catches.”

“There was no such thing as a catch. There was a specialist doing her job slowly.”

Maren looked at the two lists taking shape between them. Three years ago there had been nine cases and nine corrections and a sentence she believed, and it had given way exactly here, at the line between what she had seen and what she could defend. The sentence had nothing under it because the counting that would have held it up did not exist, and no one, including her, had treated building that counting as part of the job.

The survey exports were all theme reports, tidy and monthly: resistance low, sentiment positive, comments synthesized into training reinforcement and template refinement. The verbatims behind the themes, the actual words people had typed into the only box available to them, were nowhere in the folder or on the screen.

“Where do the raw comments live?” Maren asked.

Desmond was quiet for a moment. “They lived in the survey platform.”

“Lived.”

“Retention ran with the implementation license.” He looked at her across the table. “The license closed with the project.”

The raw comments had died with the license, which meant the one place employees had spoken in their own words was gone, closed on a schedule nobody had chosen for that reason. It was the same lesson the two lists were teaching all night. The thing that would have caught this had never been anyone’s to build, and so it had not been built.

It was nearly ten when she finally stood to stretch, and the table was covered in pages. Eleven review points, most of them undesigned. Two dozen signals with no receiver. A layer of actual words sitting behind a closed license with a date on it. None of it was a finding yet. It was the beginning of the thing she had needed three years ago and had never once thought of as hers to build.