Latest / The Operator's Manual with Fexingo: Daily Decisions, Tactical Wins, and Business Execution / How One Shipping Line Cut Fuel Use 15 Percent by Slowing Down
Transcript
- Lucas: Luna, I want to start with a number that sounded wrong to me the first time I heard it. One major ocean carrier cut fuel consumption by fifteen percent just by slowing its ships down by three knots. No new engines, no wind-assist sails, no alternative fuel. Just a change in the schedule. Luna: Three knots? That's like going from a highway cruise to a city street. And it cut fuel by fifteen percent? That seems too good to be true. Lucas: It is true, and the physics behind it is actually pretty brutal. The fuel consumption of a ship isn't linear with speed — it scales with the cube of the speed. So if you drop from twenty-four knots to twenty-one, that's a twelve and a half percent reduction in speed, but the fuel burn drops by roughly a third. The carrier in question didn't see a full thirty percent because of real-world factors — currents, weather, hull fouling — but fifteen percent is what they actually banked. Luna: So the relationship between speed and fuel is like the relationship between weight and damage in a car crash. Small changes, big effects. Lucas: Exactly. And this is not a new idea — slow steaming has been around since the 2008 financial crisis, when freight rates collapsed and carriers started burning less fuel just to survive. But what's interesting now is that it's become a permanent, strategic tool, not just a panic button. This particular carrier embedded it into how they plan their entire network. Luna: But slowing down ships means longer transit times. How do they keep customers happy when your container takes an extra day or two to arrive? Lucas: That's the real operational challenge, and it's where the tactical wins come in. The carrier didn't just slow everything down uniformly. They analyzed each route, each port pair, and figured out where the schedule had slack. Some routes could absorb an extra day without breaking customer commitments. Others couldn't — they kept the speed up. But for the ones that could, they adjusted the schedule, communicated the new arrival windows, and in many cases, customers were fine with it because the rate was lower. Luna: So it's a segmentation play — not a blanket policy. That's smart. Lucas: Right. And the savings are not trivial. Fuel is typically the biggest operating cost for a container ship — sometimes forty to fifty percent of the total. So a fifteen percent cut in fuel consumption on a vessel that burns, say, a hundred tons of fuel a day at sea is real money. We're talking millions of dollars a year across a fleet of dozens of ships. Luna: And I'm guessing the emissions reduction is a nice side benefit, especially with all the pressure on shipping to decarbonize. Lucas: Absolutely. The International Maritime Organization has targets to cut greenhouse gas emissions by fifty percent from 2008 levels by 2050. Slow steaming is one of the cheapest ways to make a dent right now. This carrier reported a significant drop in their carbon intensity per container-mile, which is a metric that charterers and cargo owners are starting to care about. Luna: So it's a win win win: lower costs, lower emissions, and a more predictable schedule. What's the catch? Lucas: The catch is that it changes the calculus for everything else in the supply chain. If a ship takes two extra days to get from Shanghai to Los Angeles, the importer needs to hold more inventory, or the warehouse needs to adjust its unloading windows, or the trucking company needs to be ready on a different day. It ripples through the entire logistics chain. And that's why the carrier had to work closely with its customers to make it work. Luna: So it's not just a captain's decision — it's a supply chain coordination effort. That's the kind of operational detail that doesn't make the headlines. Lucas: Exactly. And that's what I love about this story. It's not a flashy technology or a huge capital investment. It's a smart, data-driven decision about pace. And that's a lesson that applies beyond shipping. Luna: Before we go further, I want to say something about how we bring you these stories. We don't run ads on this show, which is a choice we made early on. If you've gotten something useful out of these episodes — even just one idea that saved you a headache — and you want to support that ad-free choice, the link is buy me a coffee dot com slash fexingo. Lucas: Yeah, and it genuinely helps us keep doing this. No strings, no perks, just knowing that people who listen find it valuable. Alright, back to the ship. Lucas: So beyond the shipping lines, this same logic is popping up in other industries. Trucking fleets have been experimenting with speed governors that cap trucks at sixty-five miles per hour instead of seventy-five. The fuel savings are similar — around ten to fifteen percent — because aerodynamic drag scales with the square of speed. And in data centers, you have something analogous: servers running at lower utilization are less efficient, so operators are consolidating workloads onto fewer machines and letting the others idle. It's the same principle of not running everything at maximum all the time. Luna: So the underlying theme is that full throttle isn't always optimal. Sometimes you get better results by easing off. Lucas: Right. And the key is to measure the actual relationship between speed and cost in your own operation. For the shipping line, they had to look at their fuel burn data, their schedule constraints, and their customer commitments. It wasn't a one-size-fits-all number. They had to find the sweet spot for each route. Luna: How did they actually convince the operations team? I imagine the captain and the port agents were used to running at a certain pace. Change is hard. Lucas: That's a great question. In this case, the fuel savings were so large that it made the business case for itself. They ran a pilot on one vessel, tracked the fuel consumption and the schedule impact, and when the numbers came in, it was a no-brainer. But they also had to retrain the crew to operate differently — not to push the engines to compensate for delays, and to communicate more proactively with the shore side. Luna: So it wasn't just a policy change — it was a behavior change. And that's often the hardest part. Lucas: Exactly. And that's why the operational details matter. They didn't just say 'slow down.' They changed the incentives. The bonus structure for the crew was tied to fuel efficiency, not just arrival time. That aligned everyone's interests. Luna: That's a critical point — if you want people to change their behavior, you have to change what you reward. So in this case, the captain was rewarded for saving fuel, not for being early. Lucas: Precisely. And the results were sustainable. After the pilot, they rolled it out across the fleet, and the fifteen percent fuel saving held up. They also found that the more predictable schedule actually reduced the need for expensive 'sail fast, wait at port' patterns, which had been wasting fuel for years. Luna: So they were burning fuel to rush to the port and then sit idle at anchor. That's the kind of inefficiency that's hiding in plain sight. Lucas: Absolutely. And that's a lesson that translates to any operation. What are you doing at full speed that you don't actually need to do? Is there a way to smooth out the demand, to level the load, to reduce the peaks? Sometimes the answer is to slow down. Luna: I'm thinking about my own workflow. I tend to answer emails immediately, but maybe I could batch them and respond in the afternoon. It wouldn't save fuel, but it might save my sanity. Lucas: That's not a bad analogy. The point is to question the default pace. In shipping, the default was 'go as fast as possible to get there on time.' But when they actually looked at the data, they found that slowing down by a few knots didn't hurt their on-time arrival percentage as much as they feared — because the schedule had built-in slack that was being wasted on speed. Luna: So the slack was there all along — they just didn't know it until they tested it. That's a great example of the 'one change' philosophy we talk about a lot on this show. What was the one change this time? Lucas: The one change was to the vessel schedule — specifically, the planned speed between ports. They didn't change the routes, the ports, or the ships. They just changed the speed setting in the voyage plan. And that one change cascaded into lower fuel costs, lower emissions, and a more predictable schedule. Luna: And the result was fifteen percent. That's a number I'll remember. Thanks, Lucas. Lucas: Thanks, Luna. And if you're thinking about your own operation, maybe ask: what's your version of slowing down by three knots? It might be worth a pilot.