He also learned the names of people who rarely appeared in those meetings. Tanya Lewis knew which loading lanes jammed when it rained because she worked there when it rained. A driver named Carlos Benton knew that a hospital customer would not accept a shipment before six in the morning, no matter what the route-planning software predicted. An inventory clerk named Priya Nair could identify half a dozen common scanning errors by the particular sequence of beeps they produced. None had been asked to help design the latest process improvements.
At home, the transition was not effortless. Daniel began leaving before Lily woke on some mornings, and he hated the first time she asked why he was no longer there to make pancakes. Megan helped with breakfast and school transportation, but Daniel knew that a reasonable backup arrangement was not the same as a child's preferred routine. He began leaving handwritten notes beside Lily's cereal bowl: questions about science class, silly sketches of forklifts, reminders that he would be home for dinner.
One Wednesday, Lily called while he was reviewing departure logs. She had forgotten her library book and was near tears because it was due that morning. Daniel told her how to find the librarian and explain what happened, then asked whether she wanted him to bring the book during lunch. There was a long pause at the other end of the line.
"No," she said. "I can do it. I just wanted to hear you."
He sat motionless after the call ended. Being back at work was right for their family, but right did not mean painless. He put a reminder on his calendar for a Friday school event and refused to move it when an executive meeting later landed on the same hour.
On his sixth day of touring facilities, he found Marcus Reed working at a dispatch console long after his shift should have ended. Marcus was fifty-two, had spent nearly twenty-five years in transportation scheduling, and looked tired in the unmistakable way of someone who knew exactly which problems tomorrow would contain. A cold cup of coffee stood beside his keyboard. The screen showed a map covered in brightly colored route lines.
"What isn't working?" Daniel asked.
Marcus did not turn. "How much time have you got?"
"Enough to start."
"Then stop looking at the green numbers." Marcus tapped the screen. "They aren't telling you what you think they're telling you."
Daniel pulled up a chair. Marcus explained that the routing software optimized routes primarily for geographic distance and nominal truck capacity. It treated customer delivery windows as flexible preferences instead of commitments. A truck could drive fewer miles and still arrive hours after a customer stopped receiving. The system then proposed overtime to correct delays its own schedule had created.
"I've reported it seventeen times," Marcus said. "Every time somebody tells me the system is working as designed."
"It probably is," Daniel replied.
Marcus looked at him sharply. "You saying the drivers are the problem?"