There is a photograph that doesn't exist but that the story keeps drawing anyway: an army of twenty thousand lounging on a beach in August sunshine, as if on a bank holiday, while four miles inland an empty ridge sits undefended — the ridge that would have won the campaign, ended the stalemate, and possibly changed the course of the First World War.
Nobody was cowardly. Nobody disobeyed. The Turks defending the route numbered a handful. The army simply did not move, because no one in the chain of command had said clearly enough that it should.
This is Robert Greene's central failure case for Strategy 5, the Command-and-Control Strategy — and its lesson is that a perfectly good plan executed by perfectly willing men fails anyway if the chain carrying the orders is broken.1
By the end of 1914, the Western Front had locked into stalemate and Germany was beating Russia badly in the east. Britain needed a new idea, and the one that emerged — backed by Winston Churchill, then First Lord of the Admiralty — was an attack on Gallipoli, the peninsula controlling Turkey's Dardanelles Strait.1
The strategic logic was genuinely excellent. Turkey was Germany's ally, and the Dardanelles was the gateway to Constantinople. Take Gallipoli and Constantinople follows; Turkey leaves the war; the Allies gain bases from which to attack Germany from the southeast, splitting its armies. They would also open a clear supply line to Russia. Victory here would change the shape of the whole war.1
General Sir Ian Hamilton, sixty-two, an able strategist and experienced commander, was given the campaign in March 1915. Churchill's orders were one line — take Constantinople — with the details left to the general.
The initial landings on April 27 went wrong in nearly every possible way. The maps were inaccurate. Troops landed in the wrong places. The beaches were far narrower than expected. Worst of all, the Turks fought back with unexpected ferocity and skill.1
By the end of the first day most of the 70,000 Allied troops were ashore and none of them could get off the beaches. The Turks pinned them there for weeks. Gallipoli had become the very thing it was designed to break: a stalemate.
In June, Churchill got the government to send more troops, and Hamilton designed a genuinely good second plan.
He would land 20,000 men at Suvla Bay, twenty miles north. Suvla was vulnerable in exactly the right ways — a large harbor, low-lying and easy terrain, and a defending force of only a handful of Turks. A landing there would force the Turks to divide, freeing the Allied armies pinned to the south. The stalemate breaks, and Gallipoli falls.1
Then the command appointments were made, and the campaign was effectively lost before a man landed.
Hamilton was forced to accept the most senior Englishman available: Lieutenant General Sir Frederick Stopford, sixty-one, a military teacher who had never led troops in war, who believed artillery bombardment was the only way to win a battle, and who was in poor health.1
Under him, Major General Frederick Hammersley would lead the Eleventh Division. Hammersley had suffered a nervous breakdown the previous year.
Neither was Hamilton's choice. Both were, in the specific way that would matter, terrified of risk.
Hamilton's leadership style was to tell officers the purpose of a battle and leave the execution to them. He was a gentleman — never blunt, never forceful.1
He had one crucial request. Once the Turks learned of the Suvla landings they would rush reinforcements, so the Allies had to move immediately inland to a range of hills called Tekke Tepe, four miles away, and hold them before the Turks arrived. From Tekke Tepe they would dominate the peninsula.
The order was simple. Hamilton, not wanting to offend a subordinate, expressed it in the most general possible terms — and specified no time frame at all.1
Watch what happens to a vague order as it travels down a chain staffed by frightened men.
Hamilton meant as soon as possible. Stopford, filtering it through his own risk-aversion, understood if possible — a goal to aim for once the beaches were secure. That's the order he passed to Hammersley. Hammersley, already nervous about the entire campaign, passed it to his colonels less urgently and vaguer still.1
By the time it reached the men who would actually have to walk up the hill, Hamilton's decisive strategic objective had become an optional suggestion.
The landings began in the early morning and immediately fouled — Stopford's own changes to the landing plan made a mess of the disembarkation. Officers came ashore arguing, unsure of their positions and objectives. They sent runners asking what to do next. Advance? Consolidate? Hammersley had no answers.1
Stopford had positioned himself on a boat offshore, from which he intended to control the battlefield — and from which he was impossible to reach quickly enough to get a prompt decision. Hamilton was on an island still further away. The entire day dissolved into argument and the relaying of messages.
The next morning, reconnaissance aircraft told Hamilton the flat land around Suvla was essentially empty and the route to Tekke Tepe was open. The troops needed only to march. They were not marching.1
He went to see for himself. Reaching Stopford's boat that afternoon, he found the general in a self-congratulatory mood: all 20,000 men were ashore. No, he had not ordered the advance — without artillery he feared a Turkish counterattack, and he wanted the day to consolidate and land supplies.
Hamilton, who had learned an hour earlier that Turkish reinforcements were already hurrying toward Suvla, said the hills had to be taken that evening. Stopford objected to a night march. Too dangerous. Hamilton kept his temper, excused himself politely, and left.1
Near panic, Hamilton went to find Hammersley at Suvla, and found the army lounging on the beach "as if it were a bank holiday." Hammersley himself was at the far end of the bay, busy supervising construction of his temporary headquarters.1
Asked why the hills weren't taken, Hammersley explained that he'd sent brigades for the purpose, they'd met Turkish artillery, and his colonels had said they couldn't advance without more instructions. Messages between Hammersley, Stopford and the field were taking forever, and when Stopford was finally reached he'd sent back word to proceed cautiously, rest the men, and advance the next day.
A handful of Turks with a few guns were holding up twenty thousand men from marching four miles. Hamilton finally lost his composure and ordered a brigade sent to Tekke Tepe immediately, that night.
At sunrise Hamilton watched through binoculars as his troops retreated headlong back to Suvla. A large Turkish force had reached Tekke Tepe thirty minutes ahead of them.1
Within days the Turks retook the flats and pinned the army on the beach. Four months later the Allies abandoned Gallipoli entirely.
Greene's reading is precise, and its value is in what it refuses to blame.
Hamilton thought of nearly everything. He understood the need for surprise and deceived the Turks about the landing site. He mastered the logistics of a complex amphibious assault. He correctly identified Tekke Tepe as the key point and built a good strategy for taking it. He even planned for contingencies.1
What he ignored was the thing closest to him — the chain of command itself, and the circuit through which orders, information and decisions would have to travel. He was entirely dependent on that circuit, and he never examined it.
The first links were Stopford and Hammersley, both terrified of risk, and Hamilton failed to adapt his style to that specific weakness. His order was polite, civilized and unforceful, so both men interpreted it through their fear. The next links were colonels with no contact with Hamilton on his island or Stopford on his boat, led by a man too overwhelmed to lead, terrified of ruining a plan they'd never understood. Below them, soldiers with no leadership at all, wandering a beach.1
Vagueness at the top turned into confusion and lethargy at the bottom.1
You've asked a team to prioritize something you consider urgent, and you asked politely, because they're competent adults and you didn't want to seem heavy-handed. Two weeks later it hasn't moved, and other work has quietly absorbed the time.
Before you conclude the team has a motivation problem, run Hamilton's autopsy on yourself. Did you give a deadline, or did you communicate urgency through tone and assume it carried? Tone doesn't survive transmission. It degrades at every handoff, exactly the way "as soon as possible" became "if possible" between one general and the next.
Then look at who's carrying it. Hamilton's real error wasn't vagueness in the abstract — it was vagueness delivered to two specific people whose defining trait was fear of risk. The same words to a bolder subordinate might have been enough. Adapt the form of the instruction to the person receiving it, not to your own preferred style of speaking.
And check the return path. Hamilton had no way of learning what was happening at Suvla until he physically went there and looked. If the only way you'd find out that your priority has stalled is by accidentally noticing in a month, you don't have a chain — you have a hope.
Gallipoli is exhaustively documented military history, and the Suvla Bay failure in particular has been studied continuously for over a century. Greene's account tracks the standard record closely. [POPULAR SOURCE] for his framing and emphasis.
Open tension: Greene's reading puts nearly all the weight on Hamilton's leadership style, which makes for a clean lesson but understates two things the historical record carries. First, Hamilton did not choose Stopford or Hammersley — he was forced to accept them by a seniority system he had no power to override, which makes this at least as much an institutional failure as a personal one. Second, the campaign was already a disaster before Suvla; the April landings had failed for reasons (bad maps, wrong beaches, underestimated Turkish resistance) that had nothing to do with the chain of command.
Greene's chapter needs Gallipoli to be a chain-of-command story, so it becomes one. The fuller account is that a broken chain finished off a campaign that a dozen other failures had already crippled.
Set this beside Marshall and Remote Control, the same chapter's positive case. Hamilton and Marshall faced structurally identical problems: a large organization, subordinates they hadn't chosen and mostly couldn't trust, and a need to move faster than their opponents.
Hamilton adapted his style to nobody and hoped politeness would carry. Marshall systematically replaced the people in the chain with protégés he'd personally trained, then communicated through them. The pairing sharpens what the strategy is actually asking for: not louder orders, but ownership of the chain itself as a designed object. Hamilton treated his chain as a given he had to work through. Marshall treated his as the primary thing to be worked on — and only then started giving orders.
Business → The Priority That Nobody Killed. Every organization past a certain size accumulates initiatives that were announced with real intent, never formally cancelled, and quietly received no resources — the exact shape of Hamilton's Tekke Tepe order.
The insight the pairing produces: these are almost never traced back to the announcement itself, because the announcement felt clear to the person who made it. The failure is invisible from the top by construction, since the only person who knows what was actually meant is the one person who never hears how it was received. Hamilton needed an aircraft and a personal boat trip to discover the gap; most executives never discover it at all.
Psychology → Ambiguity Resolved Toward Existing Fear. When people receive an ambiguous instruction, they don't resolve the ambiguity randomly — they resolve it in the direction of their existing anxieties and incentives. Stopford didn't misread "as soon as possible" through carelessness; he read it through a career-long conviction that unsupported infantry advances were how generals got destroyed.
The insight: vagueness isn't neutral. It is systematically converted into whatever the receiver was already inclined to do, which means a vague order to a risk-averse person is functionally an order to do nothing — and it will be executed faithfully as such.
The campaign was not lost by cowards or incompetents. It was lost by a chain of reasonable men each doing what they honestly believed had been asked of them, in a system where nobody's honest interpretation matched the man who gave the order. That failure mode does not announce itself. Everyone in it feels like they're doing their job.