5.2.3: Case Study - Autonomous Haulers and Hidden Yields

Brockman Mining Corporation: The Savings Nobody Was Watching For

CFO Elena Marsh didn't bother with a preamble when she opened the Year 2 governance audit. She put one slide up: 84 million dollars promised in cumulative labor savings, 42 million actually realized. "We're at half," she said. "Not half of a stretch target. Half of the number this board approved a hundred and forty-five million dollars against." Program Director Tom Bracken, who'd run Project Vulcan's delivery two years earlier, leaned forward before anyone else could speak. "My team hit every metric we were given," he said. "Three weeks ahead of schedule, two and a half percent under budget. If the labor case doesn't hold, that's not a delivery failure, that's a business case that was wrong before we ever broke ground." Elena didn't disagree with him. "That's exactly the problem," she said. "Nobody's blaming your build. I'm telling you the thing we built the entire justification on isn't paying for itself." She walked the room through why. Eliminating a hundred and eighty drivers hadn't eliminated a hundred and eighty payroll lines, since running the autonomous fleet had required hiring sixty-five automation specialists, robotics technicians, and remote dispatchers at wages that ate straight through the driver-side savings. The proprietary guidance hardware, assumed to be serviceable in-house, had instead required third-party field engineering contracts running 6.8 million dollars a year that nobody had budgeted. And for the program's first nine months, the safety failsafes had triggered constant emergency stops whenever dust or tumbleweeds crossed the optical sensors, cutting pit output 12 percent before anyone fixed the calibration. "Run it forward at this rate," Elena said, "and payback stretches from under four years to almost eight. That's outside every risk threshold this company has for a technology investment." CEO Richard Halloway looked at the Phase 2 proposal sitting on the table, twenty more autonomous water carts and drill rigs waiting on a vote. "Then we're pausing it," he said. "I'm not authorizing more capital into a program that's already missed its own case by half." Priya Deshmukh, running the Portfolio Management Office, asked for one week before that vote went to the full board. "You're evaluating this against a labor number from a four-year-old business case," she said. "I want to look at what's actually happened across the whole asset, not just the line we originally decided to track." Richard wasn't enthusiastic. "One week," he said. "I'm not interested in a delay dressed up as due diligence." She came back with numbers that didn't just complicate the picture, they nearly inverted it. Tire lifespan on the autonomous trucks had climbed from 4,200 hours to 7,100, worth 14.2 million dollars a year, because the machines braked and pivoted with a uniformity no human driver ever managed. Fuel consumption was down 11.4 percent and engine overhaul intervals had stretched eighteen months, another 8.6 million. Because the trucks never stopped for lunch or fatigue rotations, fleet operating hours were up 2.6 hours per truck per day, adding 22.5 million in incremental ore throughput. Zero lost-time injuries in the autonomous zones had cut workers' compensation premiums 22 percent, worth another 3.8 million. "Add the labor line back in," Priya said, "and total realized value this year is 73.1 million dollars. Against an original plan of 42." The room went quiet for a second, and then didn't stay quiet. "How does nobody know this?" Richard asked, turning toward the Head of Fleet Maintenance, Liam O'Connell, who'd been sitting near the back of the room through the whole meeting. "Liam, your department runs the tire and drivetrain program. Did you know lifespan had nearly doubled?" Liam didn't flinch, exactly, but he took a second before answering. "Yes," he said. "We noticed it in the first six months. It went straight into our operating margin. Nobody ever asked me to report it anywhere, and I wasn't hiding a number nobody had assigned me to track." Elena, still working through her own recalculation, wasn't fully sold. "You're telling me the program that missed its headline number by half is actually beating its own business case by close to double," she said to Priya. "That's a hard thing to bring to the audit committee a week after I told them the opposite." Priya didn't back down. "The numbers were sitting in your own maintenance and safety systems the whole time," she said. "I didn't invent them to save the program. I found them because nobody had ever pointed the tracking at anything other than headcount." Rebecca Sinclair, the Pit Logistics Director, who would inherit ownership of the throughput numbers if the board accepted Priya's framing, asked the question that hadn't come up yet. "Say we accept all of this," she said. "Phase 2 is water carts and drill rigs, not haul trucks. I don't know that the tire and fuel story repeats on different equipment, and I don't think anyone in this room actually knows that either." Liam added his own concern on top of hers. "If you make me formally accountable for these numbers going forward instead of just quietly absorbing them," he said, "you've given me a reason to find savings that exist. I'd want someone else checking that I'm not finding savings that don't." Richard, still turning Priya's number over, said what had clearly been sitting under the whole meeting from the start. "We approved a hundred and forty-five million dollars on one line item because a headcount number was the easiest thing to put in front of this board two years ago," he said. "I'm having a hard time admitting that was the mistake, not the delivery, not the drivers, just the number we chose to believe in." He looked at the Phase 2 vote still sitting on the table in front of him, at Elena's shortfall number on one screen and Priya's 73.1 million on the other, and didn't call the vote yet.

Discussion Questions

This section is designed for you to pause and consider how these leadership concepts land in your own professional world. There are no right or wrong answers here. Instead, these questions are meant to help you audit your current approach and identify where you might want to pivot.

1. Liam O'Connell's team absorbed the tire and fuel efficiency gains into its own operating margins for two years without reporting them, not out of concealment but because no one had assigned him formal ownership of those benefits. Why is it common for operational departments to stay silent about efficiency gains realized from a project delivered by a different team, and how would a formal Benefits Transition Charter have changed his behavior from the start?
2. If Priya's audit had found nothing and the labor savings deficit had been the whole story, what stage-gate criteria should Richard's board have used to decide between decommissioning the autonomous fleet and spending additional capital to optimize it?
3. Elena's skepticism, that a program missing its target by half couldn't plausibly be beating it by nearly double, is a reasonable instinct. What would you actually need to verify before trusting Priya's 73.1 million dollar figure enough to approve Phase 2 on the strength of it?