In 1915, Winston Churchill had a genuinely brilliant idea. The Dardanelles. It was WW1, the Western Front was a stalemate, millions of men dying in trenches for yards of mud. Churchill's concept was simple and bold: bypass the whole thing. Use British naval mobility to force the Dardanelles, knock the Ottoman Empire out of the war, open a supply route to Russia, and collapse Germany's southern flank. On paper, it could have shortened the war by years.
250,000 casualties later, Britain evacuated Gallipoli with nothing to show for it. Zero strategic gain. A perfect withdrawal back to where they started.
The idea wasn't the problem. The idea was a 9 out of 10. What killed it was everything that came after. History is filled with these lessons and in hindsight we can learn from and utilize in our own businesses, situations, and life.
Derek Sivers Got It Right But Missed a Portion
Derek Sivers has a framework I've always liked: "Ideas are just a multiplier of execution." He lays it out simply that a brilliant idea with no execution is worth $20. A brilliant idea with brilliant execution is worth $20 million. The math is clean and the point is clear: stop being precious about your ideas and start doing something with them. But also, the underlying point is you have to limit the ideas you choose and execute on them to be successful and for the idea to have the best potential outcome.
He's right. But I think there's a missing layer.
After years of consulting work and reading enough history, business, and military books to see the patterns, my version of the formula looks more like this:
(Idea + Strategy) × Execution = Result
The idea and the strategy are bundled together. The idea is the "what", the bold concept, the vision. The strategy is the throttle. It takes the raw idea and converts it into something digestible and executable. Without that throttle, you have a team staring at a whiteboard asking "so... what do we actually do Monday morning?"
Execution is the multiplier. It determines whether the whole package becomes real or stays theoretical or even worse the idea fails and never starts. And this is where Gallipoli and most strategies I've seen fall apart.
Bold Plans Need Great Execution
Listening to Niall Ferguson describe the Gallipoli campaign in The Empire, my gut reaction wasn't that the concept had flaws. It was bold, and any bold plan needs great execution. What I questioned immediately was implementation.
How do you get everyone on the same page? How do you share resources and praise so that people work toward the mission instead of competing for glory or control over their own fiefdom? How do you weave strategies together instead of running parallel operations that never connect?
Once the campaign was set in motion, you could see exactly how it would fail. There wasn't enough buy-in. The strategies weren't jointly woven; they were disjointed with competing purposes.
The War Council was divided. Kitchener was protecting his troop reserves. Fisher was protecting his ships. Churchill was protecting his reputation as well as his idea. Each man optimizes for his own scorecard instead of the collective mission. The army and navy had no joint doctrine; they were fighting separate wars in the same geography. Ships that could have suppressed defensive fire stayed back because they were "too valuable to risk." Troops landed under withering fire with no naval support.
And that all occurred before the telegraphing of the plan ruined the surprise and opportunity. Britain bombarded the Dardanelles in February, failed a naval assault in March, then didn't actually land troops until late April. Weeks of signaling exactly what was coming. Mustafa Kemal used every day of that warning to prepare the defenses that slaughtered the ANZACs on the beaches.
Miyamoto Musashi wrote in The Book of Water: "In all forms of strategy, it is necessary to maintain the combat stance in everyday life and to make your everyday stance your combat stance." You must force the enemy into your rhythm so that they are unsettled, and attack when they are entirely unprepared.
Britain did the opposite. They told the Ottomans exactly where, when, and how then wondered why it didn't work.
The Strategy Layer Was Missing
Here's where my formula matters. Gallipoli had the idea to attack the soft underbelly (which Churchill again tried to do in WW2 in Italy). But the strategy layer, the throttle that converts a bold concept into coordinated, bite-sized execution barely existed.
No unified command. No integrated doctrine between services. No supply chain pre-positioned before the landing. No intelligence from the actual terrain. Planning done from maps in London, disconnected from the ground truth at Gallipoli.
The math:
- ▸Idea: 9/10 genuinely could have changed the war
- ▸Strategy: 3/10 divided command, no unified plan, competing priorities
- ▸(Idea + Strategy): Maybe a 6/10
- ▸Execution: 2/10 limited to no coordination, logistics, & a telegraphed attack
- ▸Result: 5 × 2 = Catastrophe
250,000 casualties. Nothing gained. The beaches of Gallipoli are the proof.
Same Country, 25 Years Later
If Gallipoli proves how execution fails, the Battle of Britain proves it works when done right.
Summer 1940. France has fallen. Britain is alone. The Luftwaffe has more aircraft, more pilots, more of everything. By every measure, Britain should lose.
They won. And the reason is worth examining and comparing against.
First and I think this is critical Britain was on its home turf. German bombers were overhead. Families were in basements. The "why are we fighting" question answered itself. At Gallipoli, nobody could articulate what they were dying for or for that matter striving towards in one sentence. In the Battle of Britain, a child could: survival.
That proximity to consequences unified everyone in a way that an offensive expedition thousands of miles from home never could. The RAF was one group with one mission. Not competing services with competing agendas, a single integrated system with a unified purpose.
Second, radar. A technological advantage the Germans didn't fully understand. Chain Home stations detecting raids 100 miles out, giving Fighter Command 15-20 minutes of warning to coordinate and pool their limited resources. Information advantage in a battle measured by minutes. This was the one area where Britain maintained innovation through the 1930s cuts and it saved them.
Third, the command and control system was extraordinary. Radar operators detected. Plotters tracked on map tables. Controllers directed squadrons. Pilots intercepted. Ground crews rearmed and refueled for rapid turnaround. Information flowed seamlessly from detection to action in minutes. Everyone understood their role and how it connected to the mission.
And fourth production. Lord Beaverbrook simplified fighter production, cut bureaucracy, prioritized ruthlessly. Britain, under bombardment, out-produced Germany in fighters. 500 per month to Germany's 200. While being bombed, they grew stronger.
The math:
- ▸Idea: 7/10 defend the island with air superiority
- ▸Strategy: 9/10 integrated air defense doctrine, clear command structure
- ▸(Idea + Strategy): Solid 8
- ▸Execution: 9/10 radar, coordination, production, shared purpose
- ▸Result: 8 × 9 = Victory against odds
Same country. Same people. Same industrial base. Different formula, different result.
But here's the nuance people miss even though the Battle of Britain almost didn't happen. The 1930s defense cuts nearly made it impossible. Radar barely made it in time. The Spitfire was almost delayed another year. Britain got the execution right in the moment, but they nearly didn't have the tools to execute because of a decade of neglect. It wasn't a clean success story. It was a last-minute rescue.
Churchill himself is the symbol of this. The same man who championed Gallipoli and failed on execution became the leader whose speeches and morale unified a nation 25 years later. Same strategic mind, different execution environment. His redemption arc is the Battle of Britain's redemption arc.
I've Seen This Pattern in Every Business
This isn't just military history. I see the Gallipoli pattern constantly in business.
Competition for resources and glory. Complacency in key areas. Leaders optimize for their bonus scorecard or incentive structure instead of the company's mission. Strategies that aren't jointly woven but disjointed with competing purposes.
I worked on a project where we wanted to restructure countertop pricing across product levels to create a bell-shaped curve that would entice buyers to upgrade. We'd take a hit on margin percentage, dropping from our target, but the math showed it would net significantly more cash in the door. Classic case of sacrificing a metric to improve the actual outcome.
It was nixed. The key decision maker was hyperfocused on margin percentage because that's how his bonus was calculated. The incentive structure was working against the strategy. He wasn't wrong to care about margin; the system made him care about margin. But the system was the obstacle.
We did it anyway. Quietly. The program was a massive success, and he ended up being praised for the results.
That's Gallipoli in a conference room. The strategy was sound. The execution was blocked by competing incentives. We had to go around the system to prove the system was broken.
I've also watched companies telegraph their strategy the way Britain telegraphed Gallipoli. Unless you have a moat that entrenches you, being unpredictable and bold in taking action opens up new decision points and opportunities to allow for growth and success. Announce your plans and competitors can prepare to force you off your game.
One company I observed telegraphed their business model openly while trying to white label it. Someone took the white label concept, built on it, marketed better, and is now the leader in the space. The original company is out of business. They handed their competitive advantage to someone who executed the marketing better.
Musashi again: force the enemy into YOUR rhythm. Don't announce your rhythm and hope they don't adapt.
Ideas Are Like Motivation
Here's what I've come to believe after years of building, consulting, and reading enough history to see patterns repeat.
Ideas are like motivation; they come easier than being disciplined and committed to see them through to the end. In the era of AI, ideas have never been cheaper. ChatGPT can generate a hundred business concepts in a minute. The bottleneck was always execution, and it's only becoming more obvious.
Jocko Willink says discipline equals freedom. I think that applies directly here. You need to be able to commit to an idea and stay within the box or framework you create. Not chase the next shiny concept. Not pivot every time something gets hard. Stay in the box. Execute.
But before you execute, you need the strategy layer. Ted Turner said it plainly: "Early to bed, early to rise, work like hell and advertise." That's the whole formula in one sentence. But between "work like hell" and results, there's a filter.
People have many ideas. You need to filter out the noise and choose the best ones so you can focus time to execute them aggressively and efficiently. You need to focus on the tasks that matter. You need a sound plan, no crazy document, one page is fine, something that defines what you're doing and why. Then go after it intensely until an inflection point determines: is this worth continuing, or are we done?
That's the throttle. That's the strategy layer Gallipoli didn't have and the Battle of Britain did.
The Formula
Derek Sivers says Ideas × Execution = Result. I think it's closer to:
(Idea + Strategy) × Execution = Result
The idea is the spark. The strategy is the throttle: it sharpens the idea into something digestible, breaks it into bite-sized tasks, defines the vision and purpose in clear enough terms that everyone from pilots to plotters to factory workers knows what they're doing and why.
Execution is the multiplier. Without it, even a brilliant idea with a perfect strategy is worth nothing. With it, even a decent idea with a solid strategy can produce extraordinary results.
Gallipoli had the idea. It didn't have the strategy layer or the execution. 250,000 casualties, zero gain. An additional front that was a stalemate.
The Battle of Britain had a simpler idea but a superb strategy layer and near-perfect execution. Victory against 3:1 odds.
The beaches of Gallipoli and the skies over England prove the same thing from opposite directions: ideas are necessary but insufficient. Strategy sharpens them. Execution makes them real.
The question isn't "do you have a great idea?" Everyone has ideas. The question is: can you throttle it into a strategy, break it into tasks, and execute relentlessly until the inflection point tells you what's next?
That's the formula. Gallipoli is the proof.
Concept adapted from Derek Sivers' "Ideas are just a multiplier of execution" (sive.rs/multiply).
Historical analysis drawn from Niall Ferguson's The Empire and the author's research into imperial patterns.
%2520%25C3%2597%2520Execution.png%3Fprefix%3Dmedia&w=3840&q=75)
