History
History

Lawrence and the Taking of Aqaba

History

Lawrence and the Taking of Aqaba

By 1917 the British and the Turks in the Middle East had arrived at a comfortable deadlock, and the comfort is the point.
developing·concept·1 source··Aug 8, 2026

Lawrence and the Taking of Aqaba

A Stalemate Both Sides Agreed On

By 1917 the British and the Turks in the Middle East had arrived at a comfortable deadlock, and the comfort is the point.

The Turks controlled a strategic eight-hundred-mile stretch of railway running from Syria south into the Hejaz. Due west of its central section sat Aqaba, on the Red Sea — a key position from which armies could be moved quickly north or south to protect the line.1

They had beaten the British at Gallipoli, which had done enormous things for their morale, and their commanders in the region felt secure.1

The British had tried to stir an Arab revolt in the Hejaz. The Arabs had managed a few raids and had fought more among themselves than against the Turks.1

Everyone wanted Aqaba. The British plotted to take it from the sea with their powerful navy — and behind the town rose a mountain wall cut by deep gorges that the Turks had converted into a fortress.

The British knew that even if their navy took Aqaba, they would be unable to advance inland, rendering the city's capture useless.1

And here is the sentence that explains the whole stalemate:

Both the British and the Turks saw the situation the same way, and the stalemate endured.1

Two enemies sharing a model of the problem is not a deadlock of forces. It is a deadlock of imagination.

The Officer Nobody Could Read

In June 1917 the Turkish commanders at Aqaba began receiving reports of strange enemy movements in the Syrian deserts to the north-east.

A twenty-nine-year-old British liaison officer named T. E. Lawrence had trekked hundreds of miles of desolate terrain to recruit an army among the Howeitat, a Syrian tribe renowned for fighting on camels.1

They knew a little about him. Unusually for a British officer he spoke Arabic, mixed well with local people, dressed in their style, and had befriended Sherif Feisal.1

Then word came that Lawrence had imprudently told an Arab chief — secretly in Turkish pay — that he was heading for Damascus to spread the revolt.1

This was the Turks' great fear, for a revolt in the more populated areas of the north would be unmanageable.1

His army could not have been more than 500 men, but the Howeitat were fierce and mobile. The Turks alerted Damascus and dispatched troops to hunt him down — a difficult job given Arab mobility and the vastness of the desert.1

The Loops

What followed was, from the Turkish side, incoherent.

In the next few weeks, the Englishman's movements were baffling, to say the least1

His troops moved not north toward Damascus but south toward the railway town of Ma'an, site of the storage depot supplying Aqaba forty miles away.1

No sooner had he appeared near Ma'an than he disappeared — reemerging over a hundred miles north to lead a series of raids on the railway between Amman and Damascus.1

Now doubly alarmed, the Turks sent 400 cavalry from Amman to find him.

For a few days there was no sign of Lawrence at all.1

The Uprising That Wasn't the Point

Then an uprising several miles south of Ma'an surprised them. An Arab tribe called the Dhumaniyeh had seized Abu el Lissal, directly on the route from Ma'an to Aqaba.

A Turkish battalion sent to retake the town found the blockhouse destroyed and the Arabs gone.1

And then, out of nowhere, Lawrence's Howeitat army emerged on the hill above them.

Distracted by the local uprising, the Turks had lost track of Lawrence.1

The Arabs rode along the hill at speed, goading the Turks into wasting ammunition by firing at them, while the midday heat worked on the riflemen. Having waited until the Turks were sufficiently tired, they charged down the hill.

The swift camel cavalry took them from flank and rear. Three hundred Turkish soldiers were killed and the rest taken prisoner.1

The Game, Visible Too Late

Now the commanders at Aqaba finally understood: Lawrence had cut them off from the railway line they depended on for supplies.1

And the effect compounded. Seeing the Howeitat's success, other Arab tribes around Aqaba joined, creating a growing army that began working its way through the narrow gorges toward the town.1

The Turks had never imagined an army coming from this direction; their fortifications faced the other way, toward the sea and the British.1

The Arabs had a reputation for ruthlessness with enemies who resisted. The commanders of the forts behind Aqaba began to surrender. The 300-man garrison sent out to stop the advance was quickly surrounded by the swelling Arab force.1

On 6 July the Turks surrendered, and their commanders watched Lawrence's ragtag army rush to the sea to take what had been thought an impregnable position.1

With this one blow, Lawrence had completely altered the balance of power in the Middle East.1

Attrition Against Maneuver, Side by Side

Greene's reading is the clearest statement of the distinction in the whole book, because it has both methods running in the same theatre against the same enemy.

The British were fighting by attrition. They had been directing the Arabs to capture key points along the railway.

This strategy had played into Turkish hands: the Turks had too few men to patrol the entire line, but once they saw the Arabs attacking at any one place, they could quickly move the men they had and use their superior firepower to either defend it or take it back.1

An attack at a fixed point tells a mobile defender exactly where to concentrate. The Arabs' raids were converting Turkish weakness — insufficient men — into Turkish strength.

Lawrence saw it immediately, and Greene notes the reason with some care: a man with no military background, but blessed with common sense.1

Around the railway line were thousands of square miles of desert unoccupied by the Turks.1

The Arabs had been masters of mobile warfare on camelback since the days of Mohammed. Vast space gave them infinite possibilities for maneuvers that would create threats everywhere, forcing the Turks to bunker themselves in their forts.

Frozen in place, the Turks would wither from lack of supplies and would be unable to defend the surrounding region.1

And the campaign logic that made Aqaba the target rather than the prize:

The key to the overall war was to spread the revolt north, toward Damascus, allowing the Arabs to threaten the entire railway line. But to spread the revolt north, they needed a base in the center. That base was Aqaba.1

Two Deliberate Deceptions

Both are worth separating because they do different jobs.

The loops. Tracing great loops in the vast desert spaces, Lawrence left the Turks bewildered as to his purpose.1 Not hidden — visible, and unreadable. Every appearance generated a new hypothesis and consumed Turkish attention.

The lie. Knowing the Turks feared an attack on Damascus, he deliberately spread the story that he was aiming for it, sending troops on a wild-goose chase north.1

Note where he planted it: with a chief secretly in Turkish pay, framed as an indiscretion. Information volunteered carelessly to an apparent friend is trusted in a way that intercepted intelligence is not.

Then the third element, which was not a deception at all:

exploiting their inability to imagine an Arab attack on Aqaba from the landward side (a failing they shared with his British countrymen), he caught them off guard.1

The parenthesis is the sharpest thing in the account. The Turks' blind spot was not Turkish. It was a shared assumption held by both sides in the war — which is why it was safe to attack through.

The Arithmetic

Greene puts the cost of the two methods side by side:

Lawrence's subsequent capture of Aqaba was a masterpiece of economy: only two men died, on his side.1

(Compare this to the unsuccessful British attempt to take Gaza from the Turks that same year in head-on battle, in which over three thousand British soldiers were killed.)1

Same year. Same enemy. Same theatre. Two dead against three thousand — and the maneuver campaign took an impregnable position while the attrition campaign failed.

The generalisation:

The greatest power you can have in any conflict is the ability to confuse your opponent about your intentions. Confused opponents do not know how or where to defend themselves.1

You get them to chase you in circles; you say the opposite of what you mean to do; you threaten one area while shooting for another. You create maximum disorder.1

And the precondition, which is the part that costs something:

But to pull this off, you need room to maneuver. If you crowd yourself with alliances that force your hand, if you take positions that box you into corners, if you commit yourself to defending one fixed position, you lose the power of maneuver. You become predictable.1

You are like the British and the Turks, moving in straight lines in defined areas, ignoring the vast desert around you.1

Implementation Workflow

You are stuck in a contest where both you and your opponent agree about what the problem is.

That agreement is the thing to attack first, and it is nearly invisible because it feels like realism. The British and Turks both knew Aqaba could only be approached from the sea and both were wrong in the same way, which is exactly why the position was undefended from the land.

So ask what everybody in your situation takes as given. The channel that can't be bypassed. The approval that can't be skipped. The customer segment that doesn't buy this. The resource you'd obviously need. The assumption shared by both sides is the one nobody has tested, because testing it requires disagreeing with your own side too.

Then find your desert — the space around the contested points that nobody is occupying. Everyone is fighting over the railway; there are thousands of square miles beside it.

Then stop attacking fixed points, and understand why. A predictable attack lets a thin defender concentrate, which converts their weakness into strength. If your opponent is under-resourced and keeps beating you, check whether you are telling them where to be.

Then generate threats rather than attacks. Movement that could mean several things forces a defender to cover all of them at once, and the covering is what exhausts them. This costs you very little and costs them everything.

Then plant one lie, in the direction they already fear, through a channel they trust. Lawrence's Damascus story worked because the Turks were afraid of Damascus before he said anything, and because it reached them as a careless remark rather than as intelligence. A deception aimed at an existing fear needs no persuasion.

And protect the precondition, which is the part people give away cheaply. Every commitment — the alliance, the public position, the fixed thing you must defend — reduces your room. The Turks were not beaten by 500 camel riders. They were beaten by having eight hundred miles of railway they could not abandon.

Evidence, Tensions, Open Questions

The Aqaba operation of July 1917 is well documented and remains a genuinely celebrated example of irregular warfare: the overland approach, the recruitment of the Howeitat, the action at Abu el Lissal, and the fall of the town on 6 July are all record. [POPULAR SOURCE]

The casualty comparison is doing rhetorical work. "Only two men died, on his side" is accurate for the specific engagement and omits the roughly three hundred Turkish dead at Abu el Lissal, plus a documented massacre of prisoners there that Lawrence himself described. The Gaza comparison is fair as far as it goes, and the framing — a masterpiece of economy — is an accounting choice of exactly the kind this build has flagged repeatedly. The economy is real and it is measured in the attacker's own casualties.

Lawrence is his own principal source and was a self-conscious one. Most of what is known about Aqaba's planning, and all of the interiority — what he knew, intended and deduced — comes from Seven Pillars of Wisdom, written afterwards by a man who was simultaneously the operation's commander, its theorist and its publicist. The vault's T.E. Lawrence and the Arab Revolt page notes exactly this: he is the rare military figure who theorised what he was doing while doing it, which is a strength and a serious source problem at once.

And the Arab role is thin in Greene's telling. The operation was conceived with, and executed by, Auda abu Tayi and the Howeitat, whose knowledge of the terrain and whose fighting made it possible. In this account they are Lawrence's instrument — "his 500 men," "his Howeitat army." The revolt had its own leadership, aims and politics, and those aims were subsequently betrayed at Versailles in ways that shaped the region for a century. None of that is in view, because the chapter needs a strategist and has selected one.

Author Tensions & Convergences

Against T.E. Lawrence and the Arab Revolt, the vault's existing page covers the doctrine — the theory of irregular warfare Lawrence articulated from first principles. This page covers a single operation. Together they make a point neither states: the doctrine was derived from campaigns like this one and then published, which means Lawrence is both the practitioner and the author of the standard by which the practice is judged.

Against Gallipoli and the Broken Chain — which Greene references directly here — the connection is causal. The Turkish victory at Gallipoli produced the confidence that made the Aqaba commanders comfortable, and the same British institutional rigidity is visible in both: an amphibious plan pursued because it was the plan.

Against Strategy 11: The Nonengagement Strategy there is a close cousin — von Lettow-Vorbeck tying up a British army in East Africa by staying enticingly beyond reach, in the same war. Both are small mobile forces defeating large ones by refusing to be located. The difference: von Lettow-Vorbeck's campaign achieved nothing except denial, while Lawrence's produced a base. Evasion that isn't building toward a position is just survival, which is the criticism Strategy 11 never levels at itself.

Cross-Domain Handshakes

Business → The Shared Assumption Both Competitors Hold. The most valuable strategic openings are usually not gaps one side has missed but premises the whole industry shares — that a product must be sold this way, that a customer segment can't be served profitably, that a channel is required. Everyone competing inside that frame is fighting for the railway.

The insight the pairing produces: an assumption held by all competitors is structurally invisible, because it never comes up in competitive analysis — you analyse where you differ. The Turks had no plan for a landward attack on Aqaba, and neither did the British, which is precisely why it worked; if the British had considered it, the Turks would have heard. This makes shared premises the single most underexplored source of advantage and the hardest to find, since detecting one requires disagreeing with your own side's experts as much as with the competition. The practical probe is to ask what every serious person in your industry would say is obviously impossible, and then ask who last checked.

Behavioral Mechanics → The Deception That Rides an Existing Fear. Lawrence's Damascus story required no persuasion because the Turks already feared a northern revolt. He supplied a confirmation, not a claim.

The insight neither field gives alone: the cost of a deception is inversely proportional to how much the target already wants to believe it, which means effective deception is mostly a targeting problem rather than a construction problem. A well-built lie aimed at a neutral belief must overcome scrutiny; a crude one aimed at an existing anxiety is examined for confirmation rather than for truth. This also explains the delivery choice — planting it as an indiscretion with a chief on Turkish pay, so it arrived as acquired rather than told. The defensive version is uncomfortable and specific: the intelligence you are most likely to act on wrongly is the intelligence that confirms what you were already afraid of, and it will reach you through a channel that makes it feel like a discovery.

The Live Edge

Sharpest Implication

Aqaba was undefended from the land because the Turks and the British both knew it could only be attacked from the sea. The blind spot wasn't the enemy's — it was shared, which is why it was safe to walk through. Which means the most valuable thing to look for in any deadlock is not what your opponent has missed, but what you and your opponent are agreeing about without noticing.

Generative Questions

  • What do you and your competition both take as given? That agreement is where the undefended approach is, and it's invisible because you only analyse where you differ.
  • Are you attacking fixed points against a thinly-resourced opponent? If a weaker enemy keeps concentrating in time, you're telling them where to be.
  • What commitment currently forces your hand? The Turks lost because they had eight hundred miles of railway they couldn't abandon.

Connected Concepts

Footnotes

domainHistory
developing
sources1
complexity
createdAug 8, 2026
inbound links4
next in Robert Greene
Leo McCarey and *The Awful Truth*
Harry Cohn ran Columbia Pictures like Mussolini — he kept a picture of Il Duce in his office — and in early 1937 he had a crisis.