He would not argue with it or attempt to manage her response. Margaret was quiet. "Sixty days," she said. "And if I don't see what I need to see, I will make the right decision for my company."
Daniel thanked her. "Don't thank me," she replied. "Earn it." He told her that was exactly what he intended to do.
He also spoke with Frank, who had watched the situation develop from a distance and was not inclined to pretend that the return would be easy. Frank asked how Daniel felt. Daniel thought about it. "Ready," he said. "Some nerves, but the right kind."
Frank told him that the right kind of nerves meant he cared about what he was walking into. Then he offered one final piece of advice: this time, Daniel should make sure someone kept a record of the work he did, not to turn his contribution into a performance, but so that no one could later pretend the results had appeared by themselves. Daniel smiled. He had spent years believing that good work should speak for itself. He was beginning to understand that good work also needed a reliable record.
Daniel walked back into Meridian Technologies on a Monday morning. He arrived at 7:08, as he had for nine years, but the feeling in the elevator was different. He was not braced for impact. He was not preparing to absorb a new demand from above while protecting the people below him. He was simply ready to do the work.
Lou was at the garage entrance and looked genuinely pleased to see him. "Heard you were coming back," Lou said. "Things got a little rough while you were gone." Daniel nodded.
"I heard." Lou shook his head. "Glad you're back." Daniel asked about the knee, and Lou gave the same answer he always gave: it complained when it rained.
"Probably always will," Daniel said. "Probably," Lou replied. "But I've made my peace with it." Daniel carried that sentence with him to the elevator.
The team was already assembled in the large conference room. Patricia had organized the meeting before Daniel asked her to, which was exactly what he expected. Beverly stood when he entered, not as a formal gesture but because her body reacted before she thought about it. Chris Alvarez sat with a thick notebook open in front of him. Six other team members were there, some who had worked with Daniel for years and some who had joined more recently.
They looked tired, wary, and hopeful in equal measure. Daniel did not make a speech about coming home or rebuilding trust. He pulled out a chair, sat down, looked around the table, and asked the same question he had asked nine years earlier. "Tell me what's broken, and tell me what we need to fix it."
For two seconds, the room was quiet. Then Beverly laughed, a real laugh that came from recognition rather than amusement. Chris joined her, and the tension in the room loosened by a fraction. People began talking. They described the accounts that had drifted, the decisions that had been delayed, the ways the new reporting process had made them hesitate before raising concerns.
Daniel listened without defending his own earlier decisions or asking anyone to prove that they had suffered. He wrote down what he heard, asked clarifying questions, and made a list of immediate actions. He also told them something important: they did not need to pretend the last four months had been fine in order to move forward. They needed to understand what had happened and build a better structure from the lessons.
The weekly debrief returned in the first week. The first session was awkward. People were careful, testing whether the old freedom to speak honestly had really returned or whether the room would slowly become another place where the safest answer was the least useful one. Daniel did not force anyone to speak.
He asked about current risks, gave people time to think, and responded to concerns without treating them as criticism. By the third debrief, Beverly raised a warning about a mid-tier client account that was not yet showing obvious problems in the numbers. She had noticed that requests were taking longer to arrive and that the client's project manager had begun copying additional people on routine emails. It was a small pattern, but Beverly had seen enough accounts drift to recognize the shape of trouble before it became visible.
Daniel asked three questions, assigned a follow-up, and arranged a direct call with the client. The concern proved accurate. The client had been reconsidering the scope of its next phase and had begun testing whether Meridian was still attentive to its needs. Because the team acted early, they had six weeks to repair the relationship before it became a formal issue.
After the debrief, Chris stopped by Daniel's office. "That's what it was supposed to look like," he said. He admitted that he had tried to raise similar concerns under the previous system, but they had disappeared into reports and weekly reviews. Daniel told him that he had done good work inside a bad system.
The fact that the system failed did not mean Chris had failed. Chris looked relieved, though not entirely convinced. Daniel promised to review the Callaway file with him and rebuild the account together.
The Callaway recovery began with a phone call on Daniel's second day back. He called Robert Alcott himself and did not prepare a presentation. He explained exactly where the project stood, what had gone wrong, and what Meridian could realistically deliver. He acknowledged that the last four months had not been handled well. He did not blame Adrien, the reporting structure, or the people who had followed it.
He took responsibility for the company he represented now and explained how the escalation process had changed. Alcott listened. When Daniel finished, he said, "How long have you been back?" Daniel told him it was his second day.
Alcott gave a short laugh. "That's a hell of a second day." Then his voice became serious. He admitted that he had been preparing alternatives because the previous conversations had made him question whether anyone at Meridian understood the actual state of the project.