Christmas night, 1776. The Revolution was weeks from dissolving: enlistments expired December 31, and the army had spent the fall retreating. Washington’s plan to hit the Hessian garrison at Trenton had three columns crossing the icy Delaware, a watchword he wrote in his own hand, “Victory or Death,” and contingencies briefed down to the boats. Then a nor’easter hit the river. Two of the three columns never got across. Washington’s own column crossed four hours late, marched nine miles through sleet, and took Trenton in under two hours. The washington crossing the delaware leadership lesson is not that the plan worked. It is that the plan was built to survive not working.

The plan assumed pieces of it would die

Look at what Washington actually built. A Situation everyone understood: the army dissolves in six days. A Mission nobody could misread: cross tonight, take Trenton at dawn. Actions with times and owners. One commander. And contingencies asked out loud before the boats moved: what do we do if the ice stops the guns, if the crossing runs late, if a column cannot get over.

Then the storm answered: General Ewing’s 800 militia never attempted the crossing. Colonel Cadwalader got men over but not his artillery, and turned back. Washington was left with 2,400 of the planned force, hours behind schedule, with daylight burning.

And here is the part that matters: nobody had to convene a meeting in the middle of the river. The mission was unambiguous, command sat with one man, and the loss of two columns had already been imagined. So the column that could move, moved. Surprise held. The garrison fell in well under two hours, and roughly nine hundred Hessians were captured.

Washington crossing the Delaware leadership for your next launch

In the SEAL Teams we briefed contingencies until they were boring. What will we do if the helicopter goes down. What will we do if comms fail. What will we do if the weather turns. Not because we expected all of it, but because the middle of the mission is the most expensive place on earth to start thinking.

Most business plans are the opposite. They are forecasts wearing a plan’s clothing: a best-case sequence with no owner named and no “what if” asked, and the first contact with reality kills them. The launch slips a week and the whole initiative goes quiet, because the plan only existed for the version of events where nothing slipped.

This is what the planning process I run with teams, SMACCC, is built to prevent. Situation, Mission, Actions, Command, Contingencies, Communication. The two elements Washington’s night proves are the two most skipped: Command, one name on the decision, and Contingencies, the failures you imagine while they are still cheap. Ewing’s column failing on paper in a warm room costs nothing. Ewing’s column failing at 3am with no plan for it costs the war.

The measure of your plan is not whether it runs clean. It is whether the essential core still executes when the supporting pieces fall away. Washington lost two thirds of his force before the battle started and still won it, because the mission, the command, and the contingencies were built before the storm arrived.

Apply it this week

1. Write the mission in one sentence. Take your most important current initiative and write its mission the way Washington’s men could have repeated it: one sentence, no ambiguity. If your team would each write a different sentence, that is the first fix.
2. Ask “what will we do if” three times. Name the three most likely failures: the key person out, the deadline slipping, the budget cut in half. Write one decided response for each while it costs nothing. That is a contingency. Hope is not.
3. Put one name on command. For every action in the plan, one owner. If a decision would currently require a meeting, it does not have a commander yet. Fix that before the storm, not during it.

Take it to your team

Three questions to read out loud Monday morning. Let the room answer.

1. Question one. If two thirds of our current plan failed tonight, what is the essential third that must still execute, and would it?
2. Question two. Which failure have we all privately imagined but never said out loud and planned for? Say it now, while it is cheap.
3. Question three. Where in our plan would a setback trigger a meeting instead of a decision, and whose name should be on that decision instead?

Washington did not win at Trenton because everything went right. Almost nothing did. He won because the Situation was named, the Mission was unambiguous, command sat with one man, and the failures had been imagined in advance. That is washington crossing the delaware leadership, and it is the same process that works when your storm is a market instead of a river. This is Moment 04 of Leadership Moments in History. Last week: The Marshall Plan.

Keep your eyes on the target. — Errol