"We've been told to go through our managers," Celeste replied.
"For ordinary work, that's sensible," Margaret said. "For a blocked issue those managers have already failed to resolve, it can become a way to hide it. We're changing that, and you have every reason to hold us to the promise."
The conversation lasted less than ten minutes, but Margaret carried it into the afternoon meeting with unusual care. She had spent years reviewing excellent presentations about employee engagement without asking why basic repairs moved so slowly. Now she understood that a system could look orderly at the executive level precisely because employees had learned to stop escalating questions. Restoring those questions would make senior management's life less comfortable, which was one reason it had to be done.
Isaiah spent the afternoon meeting with Meridian's technology, client service, and finance teams in separate sessions. He asked each group to name one problem it had stopped reporting because management never addressed it. At first the answers were cautious and broad; people described communication gaps and alignment issues in the language they had been trained to use. Then an older systems engineer named Ruth Calder asked whether Isaiah wanted the polite version or the version that might get somebody in trouble.
"The accurate version," he answered. "If someone retaliates against you for giving it, we need to know that, too."
Ruth described a reporting tool that routinely produced different portfolio summaries depending on which department generated them. The discrepancies were reconciled manually before distribution, but the work required hundreds of hours each quarter and created avoidable risk. Her team had proposed a repair at a cost lower than the executive hospitality budget for a single major weekend. The request had been rejected three times because the project would not produce a marketable feature.
Isaiah asked whether the problem affected the accuracy of client-facing reports. Ruth answered that controls usually caught the differences before publication, but the margin for error was narrowing as experienced staff left. Victoria requested immediate involvement from the firm's risk and compliance functions, and Margaret approved the start of a properly scoped remediation plan. For the first time Ruth could remember, the executive response to her warning began with an investigation of the system rather than an investigation of her attitude.
The discovery did not make Isaiah proud. It made him conscious of how easily a buyer could be impressed by revenue figures while overlooking the work required to keep those figures dependable. Meridian's purchase price had reflected identified risks, but some operational weaknesses were more urgent than the general categories in the valuation models suggested. He told Victoria to update the integration budget and to explain the changes clearly to the investment committee, even if doing so reduced the projected first-year return.
"They'll ask why we're spending more than planned," she said.
"Then we'll answer with the facts," Isaiah replied. "We bought the company, including its obligations. Pretending they're smaller doesn't make them cheaper."