The System Always Knows: Why Local Efficiency and System Performance Are Not the Same Problem
The System Always Knows: Why Local Efficiency and System Performance Are Not the Same Problem
系统总是知道：为什么局部效率与系统性能不是同一个问题
How local optimization in last‑mile delivery can quietly break the system 末端配送中的局部优化如何悄无声息地破坏整个系统
Arjun Kaarat | Jun 15, 2026 | 15 min read Arjun Kaarat | 2026年6月15日 | 15分钟阅读
As local optimization increases, efficiency keeps improving — but system reliability peaks early and quietly degrades. The divergence point is where the dashboard says “better” and the system says “worse.” (Illustrative art developed using AI diagramming tool — representative of general last-mile delivery dynamics.) 随着局部优化的增加，效率不断提升——但系统可靠性会在早期达到峰值，随后悄然下降。当仪表盘显示“变好”而系统实际表现“变差”时，分歧点便出现了。（插图由AI绘图工具生成，代表了末端配送的一般动态。）
In 1968, the mathematician Dietrich Braess described a result that still feels wrong the first time you hear it: adding a road to a traffic network can make everyone’s commute worse. The road does not have to fail. There does not need to be an accident, a construction delay, or a bad design. The road can work exactly as intended, and the system can still get worse. 1968年，数学家迪特里希·布雷斯（Dietrich Braess）描述了一个结论，初听时总让人觉得不可思议：在交通网络中增加一条道路，反而可能让所有人的通勤变得更糟。这条路本身并不需要出现故障，也不需要发生事故、施工延误或设计缺陷。即使道路完全按预期运作，整个系统依然可能变得更糟。
The reason is uncomfortable. Each driver chooses the route that looks best for them. That choice is individually rational. But when enough drivers make the same rational choice, the network can settle into a worse overall pattern. No single driver can easily improve their commute by changing routes alone, yet everyone is stuck in a poorer outcome than the one the system could have produced. 其原因令人不安。每位司机都会选择对自己而言最优的路线。这种选择在个体层面是理性的。但当足够多的司机都做出同样的理性选择时，整个网络可能会陷入一种更糟糕的整体模式。没有任何一位司机能仅凭改变路线就轻易改善自己的通勤状况，然而每个人都被困在比系统本可达到的最优状态更差的结果中。
In game theory, this is the useful distinction between equilibrium and optimality. A Nash equilibrium can be stable without being good. It only means that each actor is making the best move available given what others are doing. It does not mean the system has reached the best possible outcome. 在博弈论中，这是“均衡”与“最优”之间一个有用的区别。纳什均衡可以是稳定的，但不一定是好的。它仅意味着在他人行为既定的前提下，每个参与者都做出了自己能做的最佳选择。这并不意味着系统已经达到了可能的最优结果。
That distinction matters far beyond traffic. It shows up inside companies whenever teams optimize their own part of the business without seeing what their decisions do downstream. The cost dashboard improves. The service dashboard weakens. One function can show savings, while another function absorbs complaints. Everyone can be acting rationally according to their own metric, and the total system can still become worse. This is the optimization trap. 这种区别的意义远超交通领域。它出现在公司内部的各个角落：当团队只优化自己负责的业务环节，却忽视了其决策对下游的影响时，问题就产生了。成本仪表盘显示改善，服务仪表盘却在恶化。一个部门可能显示出成本节约，而另一个部门却在承受客户投诉。每个人都可能根据自己的指标做出了理性决策，但整个系统却可能因此变得更糟。这就是“优化陷阱”。
It is especially visible in last-mile logistics, where one of the most tempting goals is to increase batching density. 这种情况在末端物流中尤为明显，其中最诱人的目标之一就是提高拼单密度（batching density）。
The Metric That Looks Like Progress
看起来像进步的指标
Last-mile delivery has a simple cost structure at the trip level. A driver, a vehicle, fuel, dispatching, routing, and operational coordination all cost money whether the trip serves one customer or five. That makes the basic logic of batching very intuitive. If a delivery trip costs roughly $60 and serves one customer, the cost of that trip sits on one order. If the same trip serves three customers, the trip cost is spread across three orders. If it serves six customers, it is spread across six. 末端配送在单次行程层面的成本结构非常简单。无论行程是服务一位客户还是五位客户，司机、车辆、燃油、调度、路线规划和运营协调都需要成本。这使得拼单的基本逻辑非常直观。如果一次配送行程成本约为60美元且只服务一位客户，那么该行程的成本就由一个订单承担。如果同样的行程服务三位客户，成本则分摊到三个订单上。如果服务六位客户，则分摊到六个订单上。
This is why operations teams care about Cost per Delivery, or CPD. It is not an abstract metric. It is the operating math of the route translated into a number leadership can manage. 这就是运营团队关注“单均配送成本”（CPD）的原因。这不是一个抽象的指标，而是将路线的运营逻辑转化为管理层可以掌控的数字。
At first, improving CPD is not only rational. It is often genuinely good. A route with one delivery is usually underutilized. A route with two or three deliveries can use the driver and vehicle more efficiently while still staying within the promised delivery windows. The operation gets more productive without necessarily making the customer experience worse. 起初，改善CPD不仅是理性的，而且往往确实是有益的。只有一次配送的路线通常利用率不足。包含两到三次配送的路线可以更有效地利用司机和车辆，同时仍能保持在承诺的配送窗口内。运营效率提高了，且不一定会损害客户体验。
This is the part of optimization that feels clean. The model recommends higher batching. The routes carry more orders. Cost per delivery falls. The dashboard moves in the right direction. The problem starts when the organization forgets that CPD is only seeing one part of the operating system. The customer does not experience cost per delivery. The customer experiences whether the order arrives when it was promised. That is usually captured through On-Time Delivery, or OTD. And OTD does not always improve when CPD improves. Sometimes it moves the other way. 这是优化过程中感觉“清爽”的部分。模型建议增加拼单量，路线承载更多订单，单均配送成本下降，仪表盘指标向好。问题在于，当组织忘记CPD只是操作系统的一部分时，麻烦就开始了。客户感受到的不是单均配送成本，而是订单是否按承诺时间送达。这通常通过“准时送达率”（OTD）来衡量。而当CPD改善时，OTD并不总是随之改善，有时甚至会背道而驰。
Where the Curves Separate
曲线分叉之处
Imagine a grocery delivery route with several stops. At one stop, the trip is simple but expensive. At two or three stops, the system often improves. The driver is better utilized, the vehicle is better utilized, and there is still enough slack in the route to absorb normal friction. This is the useful zone. Cost improves, service holds, and the operation becomes more efficient without becoming fragile. 想象一条有多个停靠点的杂货配送路线。如果只有一个停靠点，行程简单但成本高昂。如果有两到三个停靠点，系统通常会改善：司机和车辆的利用率更高，且路线中仍有足够的缓冲空间来应对正常的摩擦。这是“有效区间”。成本改善，服务保持，运营在不变得脆弱的前提下变得更高效。
But as more stops are added, the route begins to carry something besides orders. It starts carrying accumulated delay. A slow elevator at the third stop. A missing gate code at the fourth. A parking problem at the fifth. A customer who takes longer than expected at the sixth. None of these issues looks dramatic in isolation. Each one may only add a few minutes. But the last customer on the route inherits all of them. 但随着停靠点增加，路线开始承载订单之外的东西——它开始承载“累积延误”。第三个停靠点的电梯缓慢，第四个停靠点缺少门禁密码，第五个停靠点停车困难，第六个停靠点的客户交接时间超出预期。单独来看，这些问题都不严重，每个可能只增加几分钟。但路线上的最后一位客户却要承担所有这些延误的总和。
That customer did not cause the slow elevator, the gate issue, the parking problem, or the longer handoff. But their delivery window absorbs the combined effect. From the dashboard, the route may still look efficient. From the customer’s side, the order is late. This is the point where the cost curve and the service curve begin to separate. 那位客户并没有造成电梯慢、门禁问题、停车难或交接时间长，但他们的配送窗口却承受了所有这些因素的叠加影响。从仪表盘上看，路线可能依然高效；但从客户角度看，订单已经迟到了。这就是成本曲线与服务曲线开始分叉的点。
CPD may continue to improve because more deliveries are being completed per trip. OTD may begin to degrade because later stops are exposed to more accumulated delay. The metric improves inside its boundary. The system absorbs the cost outside that boundary. That is the optimization trap in its simplest form. CPD可能会继续改善，因为单次行程完成的配送量增加了；而OTD可能开始下降，因为后续的停靠点暴露在更多的累积延误中。指标在其边界内得到了优化，而系统却在边界之外承担了代价。这就是“优化陷阱”最简单的形式。
A More Realistic View of the Tradeoff
对权衡更现实的看法
In practice, the shape of this tradeoff will vary by market. A dense urban zone with short travel distances behaves differently from a low-density suburban route. A two-hour delivery window behaves differently from a thirty-minute promise. Grocery behaves differently from parcel delivery. Driver experience, parking friction, apartment access, weather, and time of day all matter. But the pattern is common enough to be worth watching carefully. At very low batching levels, the operation is often too expensive. There is not enough density to make the route efficient. At moderate batching levels, cost improves and service can remain… 在实践中，这种权衡的形态因市场而异。高密度城市区域的短途配送与低密度郊区路线的表现截然不同。两小时的配送窗口与三十分钟的承诺表现也不同。杂货配送与包裹配送亦有区别。司机的经验、停车摩擦、公寓进入难度、天气和时间段都很重要。但这种模式非常普遍，值得密切关注。在拼单水平极低时，运营往往成本过高，因为密度不足以使路线高效；而在中等拼单水平下，成本改善且服务可以保持……