The next change was more consequential. Adrien replaced Daniel's weekly collaborative debrief with a hierarchical reporting model. Under the new system, team leads submitted individual reports to Adrien, who would review them and decide which issues required follow-up. Adrien called it a more data-driven process.
Daniel explained that the debrief worked precisely because people could compare observations before they were polished into formal reports. A team lead might mention a client had gone quiet, another might recognize the same pattern in a related project, and together they could identify a risk before it became visible in the numbers. Adrien thanked him for the perspective and said he preferred a model with clearer accountability. The change went forward.
Beverly came to Daniel's office the following afternoon and sat in the chair across from his desk. "He doesn't understand why the debrief works," she said. Daniel agreed that Adrien had not grasped the purpose of the meeting. Beverly explained that people said things in a shared room that they would never write in an individual report. The debrief allowed them to test assumptions and connect details across teams.
"Did you explain that to him?" Daniel asked. "I tried. He said it was an interesting perspective and that he preferred data-driven decision processes." Beverly looked at him with the directness of someone who had been around long enough to know when diplomacy was becoming a substitute for truth.
"He doesn't know what he doesn't know." Daniel nodded. "No, he doesn't." She asked whether that could be fixed. Daniel thought for a moment.
"People learn if they're willing to," he said. Beverly held his gaze. "And if they're not?" Daniel had no answer that would make either of them feel better.
The problems did not arrive as one spectacular failure. They accumulated in small decisions that each looked defensible in isolation. Adrien changed the escalation process so that urgent issues had to be summarized for the next weekly review instead of being raised directly with a decision-maker. He asked teams to prioritize visible growth targets over the quieter work of retaining existing clients.
He began measuring managers by the number of initiatives they proposed rather than the number of risks they resolved. When Daniel warned that the Callaway Systems integration had a narrow window for correcting a technical complication, Adrien told him to let the new reporting process work. When Daniel explained that the Hartfield Group needed a direct conversation with its COO before a routine renewal review, Adrien said he would handle the introduction himself. Each time, Daniel documented his recommendation and the response.
After three months, he had recorded forty-one separate instances in which Adrien had overridden a recommendation without a meaningful discussion of the evidence. Daniel was not keeping the record as a weapon. He kept it because the division's trajectory was changing and he needed to distinguish between a temporary adjustment period and a pattern of decisions that increased risk. The team's behavior changed along with it.
People continued to complete their work, but they stopped volunteering the small observations that had once helped the division catch trouble early. They no longer offered a tentative warning unless it could be supported by a formal metric. They became more careful about speaking in meetings, less willing to challenge an assumption, and more likely to let a problem pass upward without the context needed to solve it.
Daniel tried to intervene three more times. He brought data, client feedback, and concrete examples. He suggested adjustments to the escalation process, asked for a review of the reporting model, and warned that the division's best people were beginning to disengage. The third time, Adrien leaned back and said, "Daniel, I think there's a dynamic we need to address.
I get the sense you're having a hard time adjusting to the new structure. I understand you were used to operating with a lot of independence, but the way you keep bringing me these concerns reads as resistance. That's not a good look for you or for the team you're supposed to be leading."
Daniel kept his voice level. "I bring you concerns because it is my professional responsibility to make sure the person in charge has accurate information about risk." Adrien nodded as though he were being patient with a difficult employee. "I appreciate that, but I need you to trust my judgment."
Daniel answered without raising his voice. "I will trust your judgment when I have seen it produce results. Right now, I've seen decisions that contradict the data we have and the relationships we've spent years building." Adrien's smile tightened.
He leaned forward. "You built something good here. Nobody is taking that away from you. But sometimes the people who build something aren't the people who can take it to the next level.
They're too attached to the old way. My aunt brought me in because she wants this company to grow beyond its comfort zone. I need to know you're on board with that vision. If you're not, we should probably talk about what your future here looks like."
Daniel listened until Adrien finished. He thought about Gerald Marsh in the Chicago conference room, about the first debrief with Beverly, about the people who had trusted him enough to tell him what was broken. He thought about the morning routine at home and Emma's note tucked beneath her sandwich. He did not answer with anger.
"I hear you," he said. He picked up his folder, thanked Adrien for the meeting, and left the room. That afternoon, he drove to school pickup. Emma climbed into the car, dropped her backpack, and announced that Mia had done something unfair and she needed to tell him the entire story.
Daniel turned off the radio and faced her. "Tell me everything, Bug." She talked for twenty minutes, and he listened to every word.