Engineering Leadership: Mario Harik on Metrics, AI & People — The Knowledge Project

**SPEAKER_1** (0:01)
When systems, people, and data meet, a company either hums or stumbles. Today we're diving into a fascinating conversation Shane Parrish had with Mario Harik, the engineer-turned-CEO who runs one of the largest less-than-truckload carriers in the world. And what makes Mario's approach so compelling is how he frames leadership as applied engineering. He literally treats it like a technical problem: identify the issue, collect data, define requirements, design a solution, and test for outcomes. Right, but he doesn't stop at the analytical side. He adds this crucial human layer, saying that talent and trust must translate the framework into real performance. It's discipline and rational thinking meeting people skills. So how does he think about the CEO's actual work? What's the day-to-day focus? He breaks it down into three parts. First, decide how to create shareholder value—that's your strategy.
Second, translate that strategy into the KPIs you watch daily. Third, build action plans that move each KPI from point A to point B. And he's really explicit about measurement. Listen to this quote: "We obsess over them. I mean, every single day, there's approximately 10 KPIs that we monitor."
He's tracking both first and second derivatives—basically asking, are the levers accelerating in the direction you want? That's intense. What about the people side? How does he think about hiring and team building? He uses a refreshingly simple rubric: are they good at what they do, are they serious about the work, and are they collegial? But here's the key—he insists great teams aren't about consensus. They're about respectful disagreement and the ability to land on data-informed decisions together. I love his definition of ego too. He says, "ego is when you think you're so good at something that you stop learning."
That humility—learning from better programmers at MIT and from mentors like Brad Jacobs—keeps him open to continuous improvement. Speaking of Brad Jacobs, Mario credits him with two massive lessons. First, think big, because small goals produce small results.
Second, manage team dynamics and feedback loops relentlessly. How did he make that feedback concrete in practice? He changed compensation to reward service improvements and introduced systems to track damages and accountability down to the person level. That mix of carrot and coaching actually changed behavior on the dock and elevated service quality. And the technology infrastructure supporting all this is remarkable.
Every pallet moved generates data. Drivers and dock workers see productivity and damage dials on handhelds, and supervisors can track performance across shifts. That transparency creates coaching opportunities rather than just punishment. And now they're layering AI on top. Mario describes using photos and AI to evaluate trailer loading quality and provide near-real-time feedback so teams can fix issues before trailers even hit the road.
Even his meetings are engineered. Materials go out in advance, attendees submit takeaways and questions, and the group ranks them.
He makes leaders speak last to avoid anchoring junior perspectives. What about identifying talent? How does he spot the rising stars? Beyond interviews that really drill into execution details, he uses repeated touchpoints, leadership discussions, and daily feedback.
He applies the A, B, C player framework as an emotional litmus test: losing an A player gives you a pit in your stomach; losing a C player might be relief. That clarity really drives retention priorities. And his capital allocation follows the same analytical rigor. When Yellow filed for bankruptcy, Mario mapped capacity gaps and bought 28 terminals where data showed the largest return. Nearly a billion dollars later, those sites expanded capacity and margin. But that decision required disciplined FP&A tracking—each project has a launch plan, assumptions, and measurable outcomes. When results deviate, they course- correct. His daily routine is interesting too. He includes a quiet planning window where he literally plays decision trees in his head. He reads widely, distills signals from patterns, and uses that synthesis to prioritize the few things that matter.
He treats time as a scarce resource. He spends it where action plans are faltering, in the field with drivers and dock workers, and with customers to keep the voice of the market front and center.
And family time is high quality—no phones, meaningful projects, real presence. What's his take on robotics and AI for the future? He's cautious and pragmatic. Purpose-built robots will continue adding value in warehouses and terminals. But humanoid robotics is harder to predict because perception, dexterity, and emotional context remain challenging. Across everything—operations, culture, capital allocation—Mario consistently returns to one theme: belief in people. He says, "When you show someone that you believe in them, that you truly believe in their ability to be great, they have a much, much higher chance of actually being great." It's a blueprint for leaders who want rigor without rigidity:
measure the right things, create feedback loops, back people with coaching, and deploy capital where returns are provable. Do all that, and scale becomes repeatable. As Mario puts it, success is people realizing their full potential, with emotional fulfillment intact. That blends engineering, heart, and humility into a leadership model built for modern complexity. Big goals, disciplined measurement, and belief in people aren't exclusive—they're the operating system that converts ideas into lasting companies. Thanks for exploring this conversation with us today.