Core problem identification is the analytical practice of isolating the single decision, person, or structural point whose change cascades to everything else. It's the opposite of symptom-treatment. Instead of solving visible problems across the system, you identify the one lever that, if moved, makes all the symptoms irrelevant. At Issus, the core problem is not "the Persian army is larger" (symptom). The core problem is "Darius holds the army together through presence alone" (core). Solve that, and the symptoms disappear.
This method assumes one thing: that the system has a center of gravity. Not all problems do.
At Issus, Alexander is vastly outnumbered. The Persian army is larger, better positioned, and the battle is going badly. His left and center flanks are collapsing. Parmenion sends messengers warning Alexander that the day is lost — they need to retreat, reposition, try again another day. By any rational assessment of the battle itself, the Macedonians are losing.
But Alexander sees something Parmenion doesn't. He refuses to accept the premise that winning the battle means outfighting the Persian army. He asks a different question: What is the core problem I actually need to solve?
And he identifies it precisely: the core problem is not the Persian army. The core problem is Darius.
The Persian army appears unified and powerful. But it's held together by a single thing: the presence and authority of Darius, the king. Persian subjects and troops follow Darius because he is the embodiment of Persian power and divine authority. There is no command structure; there is only loyalty to the king.
If Darius falls or flees, the army doesn't reposition or consolidate — it collapses. The soldiers don't switch commanders or fight without Darius; they lose their reason to fight entirely.
This is the core problem. Not "defeat the Persian army" (which might be impossible), but "make Darius choose to flee" (which might be possible).
Alexander does something that looks insane from the perspective of conventional battle strategy. He identifies where Darius stands in the Persian formation — not at the front with the troops, but in the center where he can observe. Then Alexander takes his best cavalry, his companions, and he charges away from the main fighting, straight at the back of the Persian center, directly at Darius.
He's ignoring the collapse on his left and center flanks. He's not trying to shore up those positions. He's not engaging the main body of the Persian army. He's isolating the core problem and overwhelming it with concentrated elite force.
When Darius sees Alexander coming, he flees. And the moment Darius leaves, the Persian army's will collapses instantly. The soldiers don't try to fight without him; they don't reorganize; they simply scatter.1
Alexander has solved the core problem, which means the entire battle is solved.
The clarity-of-vision method works by identifying the core problem — the decision, the person, the structural point that, if changed, cascades to everything else. Once you see the core, you can ignore all the surface complexity and concentrate all available force on it.
This is radically different from trying to win the battle by outfighting the Persian army. That would require overcoming their numerical advantage directly, which might be impossible. But winning the battle by making Darius flee requires only that you identify where Darius is and get there with enough force to make him see that staying is death.
The method depends on ruthless simplification. Strip away all the complexity of the larger situation. Ask: what one thing, if changed, makes everything else follow? Then bet everything on that one thing.
At Issus, it works because Alexander is right: Darius is the core. The army does collapse when he flees. The core-problem identification is accurate, and the concentrated application of force succeeds.
The historical record from Arrian, our primary source, documents that Darius's presence was indeed the organizing principle of the Persian army. Arrian notes that once Darius fled, the Persian formations dissolved — not gradually, but instantly. There was no attempt at secondary leadership or rearguard action. The army simply ceased to function.
This is consistent across historical accounts: Persian forces at Issus were not a unified command structure but a coalition held together by loyalty to the king. The army was not trained to function without Darius; it was structured to collapse without him.
However, this raises a question: Was this breakdown unique to Issus, or was Alexander simply right in all three major battles (Granicus, Issus, Gaugamela) that Darius was the core? Wilson argues that Alexander's consistency in identifying and executing this pattern suggests it was a genuine insight, not luck. But some historians note that later Persian armies under weaker kings (Artaxerxes II) showed more distributed command structures, suggesting that the Persian collapse might be more about the specific composition of Darius's army than a universal principle.
The core assumption — that systems have a single center of gravity — is not always true. Some systems are genuinely distributed. At Tyre, there is no Darius. The island's strength is structural (geographic separation) not personal (dependent on one decision-maker). Alexander's success at Issus trains him to look for Darius-like cores everywhere. This blindness costs him seven months at Tyre.
Additionally: The core-problem method assumes you can correctly identify the core. Alexander is right at Issus and Gaugamela. But what if he'd been wrong? What if the Persian army had multiple power centers and Darius's death had triggered a succession rather than collapse? The concentrated charge would have been catastrophic. Core-problem thinking works brilliantly when the diagnosis is accurate and fails spectacularly when it's wrong.
If the principle is real, how would a modern strategist apply it?
The Recognition Phase:
The Execution Phase:
The Risk:
Wilson documents this explicitly as Alexander's signature move: identify the core, concentrate force, execute. This is the clarity-of-vision method in its purest form. No subtlety, no political maneuvering, no attempts at compromise or persuasion. Just: see the center, charge it, win.
The tension between Issus and Tyre (which Wilson also documents) is the tension between problems with cores and problems without them. Issus has a perfect core (Darius). Tyre doesn't (it's geographically separated from the mainland, and no amount of force on any single point changes that fact). Alexander's success at Issus blinds him to the possibility that some problems have no core. This matters for understanding his later transition to grinding mode at Tyre.
In business and organizational contexts, the core-problem method shows up as "identify the single variable that changes everything." If you can find the real bottleneck, you can make disproportionate progress by concentrating resources on it rather than spreading effort across the entire system.
A startup might realize that their core problem is not "build a better product" but "prove product-market fit to investors" — a much narrower problem with a clearer solution path. A turnaround CEO might identify that the core problem is not "fix every operational failure" but "stop the bleeding on the cash-burn rate" — one thing that, if changed, buys time to fix everything else.
The handshake insight: Clarity-of-vision problem-solving requires the ability to distinguish between core problems (whose solution cascades) and symptoms (which are numerous but secondary). Most people try to solve symptoms, distributing effort thinly across many issues. Alexander solves cores, concentrating elite force on the highest-leverage point.
This creates a massive asymmetry when it works: Alexander's force concentrates on Darius while Persian force is distributed across the entire battlefield. But it creates catastrophic failure when the core problem identification is wrong. If Darius's presence doesn't actually hold the army together, the charge fails and Alexander is trapped in the enemy formation.
Identifying the core problem requires confidence to ignore everything else. Parmenion sees the collapsing flanks and wants to reinforce them, manage the deteriorating situation across the battlefield, cut losses. This is the mentality of someone trying to control overall system performance.
Alexander sees a single point and commits everything to it. This requires the psychological capacity to accept that other parts of the system are failing, to tolerate the discomfort of watching your left flank collapse while you charge away from it, and to trust that solving the core will make everything else irrelevant.
Wilson hints at this when he discusses Alexander's "restless aggression" — the need to move, to attack, to commit forward. This personality trait is perfectly suited to core-problem thinking: he doesn't have the patience for incremental improvement across the system, so he looks for the one thing he can hit that will change everything.
The handshake insight: Core-problem identification is a learned capability, but it requires personality traits that make it possible: confidence, aggression, willingness to concentrate force and accept collateral risk. Not everyone can do this, which is why it becomes Alexander's signature advantage.
The Sharpest Implication:
If winning requires identifying the correct core problem, then being wrong about what the core problem is doesn't just lead to failure — it leads to concentrated failure. At Gaugamela and Issus, Alexander is right: Darius is the core. But at Tyre, there is no core. Alexander charges at siege towers and causeway weak points. Nothing collapses because there's nothing to collapse — it's a distributed problem with no center of gravity.
This suggests that the clarity-of-vision method works until it doesn't. And when it stops working, it fails spectacularly because you've committed everything to a point that doesn't matter.
Generative Questions: