Ariadne's String: The Path Between Adaptability and Efficiency
The great modern philosopher Mike Tyson once said, "Everybody's got a plan until they get punched in the face." Future historians will no doubt develop many theories about the initial impetus behind this profound insight, but Tyson might as well have been referring to the main predicament of complex systems: operating and surviving more or less intact in the maze of unpredictability. Any system can develop the perfect and highly optimized operation plan, with just-in-time this and agile that, but all beautiful flowcharts can, and usually do, crumble under the onslaught of reality. The drama of all systems, both simple and complex, is in the precarious balance between maintaining operational efficiency and adapting to unforeseen challenges that punch you in the face.
To begin with, surviving amidst flux over a long period demands constant transformation from all systems. However, a continuous and dynamic tension exists between a system's adaptability, efficiency, and overall stability. Even for simple systems, too much adaptability sacrifices efficiency, and too much efficiency sacrifices adaptability. For example, an organization could optimize its supply chain for maximum just-in-time efficiency and shareholder value, only to have it crumble under a sudden and unpredictable change in geopolitics halfway across the globe. Who knows, an obscure rebel group might start sinking container ships. True story. It gets worse, though; this tension is far more challenging for complex systems due to their being, well, the opposite of simple.
Complex systems are composed of multiple distinct elements - for example, consider a modern army with its infantry, artillery, mechanized units, drones, air force, and so on. The interactions between these disparate components lead to results we cannot predict by simply analyzing each system element's properties in isolation. For instance, examining a tank's capabilities in isolation offers no clear insight into its operational effectiveness when supported by infantry, artillery, drone reconnaissance, and aviation.
When combined, these additional components of the larger system radically alter the tank's capabilities and fundamentally change the nature of its engagement envelope and effectiveness on the battlefield. The introduction of aerial surveillance provides real-time data, artillery offers long-range support firepower, infantry occupies proximal space, and aviation brings a vertical dimension, together creating a system whose potential actions are vastly different and more complex than that of any single component.
In other words, each unique element allows a system to add complexity at that scale, interface with reality differently, and engage in unique and complex behaviors. The more complexity at different system scales, the more adaptable a system is in interfacing with reality at those scales. That said, if a system gets a punch to the face and is not adaptable to deal with its effects, it quickly experiences a cascading reduction of complexity and collapses.
All systems get punched in the face sooner or later. What happens with a system after the punch is where the fun begins; the system still has to maintain internal coherence and operational efficiency while simultaneously pivoting its operations to adapt to the novel external conditions. As Mike Tyson aptly pointed out, the old plan is invalid after the punch because reality has violently imposed itself on the system's assumptions.
Let's explore a principle of systemic efficiency and adaptability that accounts for the punches and what comes after them. I call it Ariadne's string principle after the ancient Greek myth of Theseus and the Minotaur.
Ariadne’s gift
The great Daedalus, legendary builder and craftsman of the ancient world, was tasked by King Minos of Crete to construct a labyrinth so complex that escape would be impossible. Once in, you were never supposed to be able to leave. On top of that, this labyrinth was to be built as a prison for the Minotaur, a creature with a man's body and a bull's head. Daedalus built the unique maze, the Minotaur was locked inside it, and the king put it to grim use, imposing a tribute on defeated Athens: the sacrifice of seven young men and seven young women every seven years to the Minotaur.
When the tribute was due again, Theseus, the prince of Athens, volunteered to be one of the seven young men destined for the labyrinth, pledging to slay the monster. However, our valiant hero was not alone. The daughter of King Minos - Ariadne - who, as it happens in myths, was in love with brave Theseus, approached Daedalus, pleading with the maze builder to help the hero escape. Moved, Daedalus asked Ariadne to give our hero a ball of string. Yes.
The myth does not mention Ariadne's initial reaction to that solution, but one can imagine it. In any case, Daedalus explained that this string was to be tied to the entrance of the labyrinth and unrolled as Theseus ventured deeper into it. As it turned out, this hack allowed our hero to navigate the maze, slay the Minotaur, and trace his steps back to freedom. Ariadne's string is the key to this myth, so let's unpack its role further.
Between Adaptability and Efficiency
On the face of it, the string is an absurd way of finding your way around in a labyrinth. Why not use a map? Or, absent a map, a series of "take the first right, walk straight 20 paces and turn left" instructions? All Theseus would have to do is trace his movements according to the plan and never stray from it. After all, Daedalus was the maze builder and presumably remembered its construction plan. One would expect a legendary techno-craftsman to produce some intricate contraption showing the way to Theseus. So, why the crude and simple string?
Simply put, because Theseus was about to be punched in the face.
Knowing that, Daedalus could not have given him a plan of the maze or a complicated contraption. What if Theseus loses the map, forgets the detailed instructions or the intricate contraption gets broken in his fight with the Minotaur? Ariadne's string exemplifies the optimal balance between maximum adaptability and simple efficiency for a given system's scale. The string doesn't show the way forward or the maze's layout. The string is dumb. Worse, it has nothing to do with the maze at all! It simply adapts to and interfaces with every twist and turn of the labyrinth while being highly efficient in showing Theseus only one simple thing - the path he took.
You see, adaptability is a function of a system's ability to perform many possible simple actions more or less independently of each other. Ariadne's string is an adaptability hack for the complexity of the labyrinth - it could interface with all possible permutations of that space. Multiple possible actions at the smallest of scales.
Efficiency, however, is a function of the ability of various system parts to work together to perform tasks at the largest possible scale. Ariadne's string was expected to perform only one task at the scale of Theseus traversing an impossible maze, fighting a monster inside it, and getting out. The simplest of tasks at the largest of scales.
Designing a system for efficiency and adaptability is far trickier than it appears at first. Imagine a city's transportation system designed for maximum efficiency: a network of trains and buses running on a tight schedule, minimal wait times, and optimized passenger carrying capacity. As is usually the case, such a system would be given as an example of optimal efficiency due to its just-in-time predictability and low operational costs. However, the system's rigidity becomes apparent when a sudden, unexpected week of heavy downpours disrupts its operations.
Recommended by LinkedIn
While optimal under normal conditions, its efficiency doesn't allow for quick adaptation to the new challenges posed by the heavy downpours. The transportation system, optimized for specific operational conditions, struggles to provide alternative routes or modes of transport that accommodate the change, leading to delays, congestion, and chaos. In other words, the system is optimized for a well-defined operational envelope, but that very optimization deprives it of the resources to quickly adapt to a dramatic change in the envelope.
Notice that if the system had a spare fleet of otherwise redundant minibuses, it could adjust to the sudden change in conditions much better. However, that same redundant fleet of minibuses - representing adaptability - will present extra costs and additional and unnecessary complexity in all ordinary conditions. There is a lesson here.
Alternatively, consider a modern tank battalion advancing in enemy territory with infantry support, acting according to doctrine as an efficient complex system. With more than a century of deployment history, tanks are shockingly efficient in interfacing with most questions the typical enemy can ask of them. Their interactions are usually short and have great finality in execution.
However, this particular enemy has deployed a swarm of dirt-cheap first-person view (FPV) drones, each armed with an armor-piercing warhead. As the swarm maneuvers at speeds exceeding 100 kilometers per hour, slamming into and destroying tank after tank, the advancing complex system has no way of interfacing with the drones. A punch to the face and a knockout. True story. What is the lesson here?
A system's effectiveness is contingent on its ability to provide a distinct response to each environmental possibility it may encounter.
If a system cannot interface with the changing conditions in its environment, it will fail to be effective and, absent a transformation, will ultimately collapse. However, we have to remember that as long as the system keeps operating under the conditions for which it is optimized, it will be within its maximum effectiveness envelope. This is why so many highly fragile systems seem to operate just fine when viewed from the outside. This is also why the easiest way to derail a highly efficient system is to change the scale of its operational envelope. Even a slight shift in external conditions would often completely derail a highly optimized and efficient system.
The problem is that highly efficient systems lack the flexibility to adapt to new challenges. Like the transportation system discussed above, to become highly efficient, they need to remove all unnecessary complexity and redundancies, streamlining processes for optimal performance conditions. The very optimization that makes a system highly efficient prevents it from quickly adapting to change. Any highly efficient system is also highly fragile.
That is because, as I already mentioned, adaptability is a function of a system's ability to perform multiple distinct actions at small scales. In other words, adaptability emerges when a system can interface with reality in multiple, often rare, non-optimal conditions. That fleet of minibuses is a small-scale redundancy, increasing the complexity and costs of the transportation system but allowing the system to adapt to the rare occurrence of a week-long downpour or other sudden disruptions. Similarly, installing radio frequency jammers on each armored vehicle is a small-scale redundancy, increasing the complexity and cost of a tank battalion but allowing the system to at least partially adapt to the sudden occurrence of an FPV drone swarm attack.
Highly adaptable systems, on the other hand, can interface with multiple environmental challenges but struggle with scaling up. As they grow, the costs of maintaining their complex adaptability increase to a threshold beyond which they cannot perform their actions efficiently at a given scale. In other words, past that scale threshold, the highly adaptable system has no other option but to optimize its processes for efficiency. Either that or the rising complexity costs at larger scales bring the whole system down.
Therefore, to be highly adaptable, a system has to either stay below a specific scale of operations or keep its adaptable elements small while growing in scale with a much more efficient structure and output. We will explore this dynamic further.
The time and scale trade-offs
If you think through this dynamic, you will notice that adaptability adds costly complexity here and now but may save a system in the future, while efficiency lowers costly complexity today but will doom a system in the future. This is why most systems will naturally drift towards increased efficiency at the cost of lowered adaptability. Optimizing for efficiency saves system resources here and now while optimizing for adaptability does not generate immediate effects for most systems.
If you find value in my insights, subscribe to my substack, click the like button, leave a comment, and share this content. Your engagement and feedback are the main indicators of the impact and relevance of my work. I appreciate your support!
