He spent the next four days moving between facilities. He arrived early enough to see the first crews clock in, rode as a passenger on delivery routes with the appropriate authorization, and spent afternoons studying exception reports that seemed almost designed to conceal the exceptions. He made no sweeping changes and announced no reorganizations. The managers waiting for a new executive to prove his authority through firing found his restraint irritating.
By Friday Daniel had a notebook full of observations and a growing suspicion that the company's most celebrated software was rewarding the wrong behaviors. He also had three missed calls from Victoria asking for a progress update. When he finally spoke to her that afternoon, she sounded impatient.
"Have you found the problem?"
"Several problems. I haven't found the complete pattern."
"My board wants a plan."
"Then tell them I'm preparing one. I won't pretend a week of listening equals a finished solution."
There was a pause. Then Victoria said, "When will you have enough information to make a recommendation?"
"When the people doing the work agree that I've described their problems accurately. After that, we can start testing changes."
Victoria leaned back in her office chair as she listened. Her father had built Grant Logistics by visiting warehouses before there were executives whose job was to visit warehouses for him. She had spent the last six months reading reports that insisted everything could be solved by demanding more. Daniel Carter was the first person who had come to her with an argument for demanding something different: a truthful account of what was happening.
"All right," she said. "Keep going."
Daniel went home on time. Lily was waiting with a school worksheet she had found impossible and had refused to throw away. He took off his boots, washed his hands, and sat beside her at the kitchen table. Whatever his new title meant in the corporate building, here it meant he was still responsible for helping a nine-year-old understand fractions before bedtime.
The first month almost convinced Daniel he had made a mistake. The regional division was not merely disorganized. It had developed an entire culture around explaining why its disorganization was someone else's fault. When a route ran late, dispatch blamed the drivers.
When a driver arrived at the wrong receiving window, the customer service team blamed scheduling. When pallets waited overnight on a dock, warehouse managers blamed the transportation system, and senior executives blamed employees for failing to adapt to change.
Nobody seemed to ask whether the system itself made success unnecessarily difficult. Everyone produced reports to defend their department, and the reports had become more sophisticated as the actual work became less reliable. Daniel spent hours reconciling numbers that should have matched and discovering why they did not. The more he learned, the less he trusted the beautiful dashboards that managers displayed during meetings.