Sailing team building · San Francisco Bay
A journey of leadership through crisis, survival and success.
A day on San Francisco Bay inside the true story of the Endurance — built as a behavioral laboratory for how your executive team decides, communicates and leads under pressure. The sailing is the setting. The debrief is the intervention.
“Men wanted for hazardous journey. Small wages, bitter cold, long months of complete darkness, constant danger, safe return doubtful. Honor and recognition in case of success.”
Why Shackleton
In 1914 the Endurance sailed for Antarctica under Sir Ernest Shackleton. The ice took the ship; the goal became survival. Over the next twenty-two months Shackleton brought all twenty-eight men home — one of the most studied leadership stories ever told. You spend the day inside it, and work the five traits credited with that outcome:
Optimism
Held for the crew, without denying the facts.
Effective communication
Clear, early, and to everyone — not just the inner circle.
Flexibility
The objective survived; the plan was rewritten repeatedly.
Leading by example
The costs he asked others to bear, he bore first.
Attention to health & wellness
Morale and stamina treated as strategic assets, not afterthoughts.
Participants leave with a copy of Shackleton’s Way — the reference the day is built on — not a bag of swag.
Why a boat, of all things
Most team-building exercises are only superficially collaborative — you can divide the work, perform alone, and reunite at the end. A boat doesn’t allow that. One person’s work lands on everyone else: the helm sets direction, trim sets speed, a missed call compromises the maneuver. That’s why the team’s real operating system shows up fast — and why the metaphors aren’t metaphors.
Sales commits without operations; finance constrains without understanding delivery. On the water, disconnected functional behavior has an immediate, visible cost.
A maneuver needs what’s happening, who acts, when, and confirmation it landed. Ambiguity produces consequences you can see — the exact failure mode of executive handoffs.
In the office, bad teamwork surfaces weeks later and gets blamed on the market. On a boat, a late decision or a conflicting command shows up in seconds and can’t be rationalized away.
The best person to lead navigation isn’t the best to run a maneuver. Sailing exposes whether an executive can take the helm, hand it off, and follow a peer without friction.
Outside their technical competence, title and function stop deciding who leads. It shows whether someone can contribute without being the expert in the room.
No laptop to retreat behind, no side meeting, no delegating downward. Limited space makes interaction patterns visible almost immediately.
Grounded in the sail-training literature, which associates the maritime setting with teamwork, communication, adaptability and leadership development — and in the plain structural logic of a vessel that only moves when a crew coordinates.
What a day on the water surfaces
Does the crew agree on the objective — or keep executing an outdated plan while conditions have changed?
Are responsibilities explicit? Do two people fight for the same task while a critical one goes unowned?
Who actually decides, on what information, and how fast? Are decisions reopened without new evidence?
Is it clear, early and closed-loop — or does positional status decide who gets heard?
Who takes the helm, who enables others, who confuses contribution with command — and can they trade roles without friction?
When the plan fails, does the team blame, freeze, over-control, or update — while holding the objective and changing the method?
Where the value actually is
We’ll be honest about the research: there is no study proving that a team which sails outperforms one that did another well-designed intervention. What is well-evidenced is the mechanism underneath — across 46 studies, structured debriefs improved performance by roughly 20–25%.1 So the sailing exists to produce something worth debriefing, and the day is built as a loop.
1 Tannenbaum & Cerasoli (2013), Human Factors — debrief meta-analysis (d = 0.67), across simulated and real settings.
Ways to sail it
A day on San Francisco Bay inside the true story of the Endurance and her 28 sailors — a historic schooner, a proven leadership model, and a debrief that ties what happened on the water to how your team leads through change.
Teams of four to six learn to sail, then race. Because every executive rotates through the helm and the lines, it produces the most usable one-day design: brief, sail, debrief, rotate, sail again, compare, transfer.
A single-vessel passage — SF Bay, the BVI, the San Juans or the Chesapeake — for whole-team interdependence, shared leadership under fatigue, and the relationship depth a three-hour sail can’t reach.
Sailing is a legitimate executive-development setting, not a novelty: Wharton’s McNulty Leadership Program runs an eight-day tall-ship venture for its MBA and Executive MBA students. Our version pairs decades of on-the-water expertise with the facilitation that makes the day change how you work — no prior sailing experience required.
Where we’re honest
You’ll find sailing vendors claiming a day on the water lifts motivation 91%, raises job satisfaction 85%, or returns four dollars for every one spent. There is no traceable study behind those numbers, so we won’t repeat them. We also won’t claim that sailing “automatically builds trust,” that winning a regatta identifies your strongest team, or that a three-hour sail changes behavior on its own.
Here’s what’s true: sailing is an unusually good environment for making executive behavior visible, and structured debriefing reliably turns that into change. The boat is the laboratory. The design, the debrief and the follow-through are the reason it works — which is exactly how we build it.
Straight answers
No — and if that’s what you want, there are cheaper ways to get it. The sail is a behavioral laboratory: a coupled system where strategy, communication, role clarity and leadership have immediate, visible consequences. The development happens in the structured debrief and in the operating agreements you take back to work. Without those, it’s a nice day on the water and nothing changes.
No experience required — and some of the sharpest breakthroughs come from people new to it. That’s part of the point: sailing puts most executives outside their technical competence, which temporarily levels title and function and shows whether someone can contribute without being the expert in the room. Professional skippers and instructors handle safety and seamanship throughout.
San Francisco Bay is home water for the Shackleton Adventure — a historic schooner and smaller vessels, with the city and the Golden Gate as the backdrop. Longer expeditions run from the port that fits the outcome: the BVI, the San Juan Islands or the Chesapeake among them.
Everyone wears a personal flotation device; swimming is not required. Weather is part of the lesson, not a threat to it — the same way business throws adversity at a team; we plan for it and adapt, which is usually the more instructive version of the day.
Not by whether people enjoyed it. We agree the behavioral targets before you sail — decision speed, role clarity, cross-functional communication, CEO dependency — observe them on the water, and convert them into explicit operating agreements. Then at 30 and 60 days we look at whether decisions got faster, fewer got reopened, risks surfaced earlier, and direct reports actually saw different behavior.
Most corporate sailing is an activity with a debrief bolted on. Ours is a diagnosed intervention that happens to use a boat: we start from a real executive-team problem, engineer the day around it, observe how the team actually operates, and follow through afterward. The Bay is the setting. The method is the reason it works.
“Life is either a daring adventure, or nothing.”— Helen Keller
Tell us the problem you’re trying to solve and where you’re based. We’ll tell you whether a day on the water is the right instrument — and if it isn’t, what is.