Why I Sail: Lessons From the Water That Apply to Business

Why I Sail: Lessons From the Water That Apply to Business

I've spent the better part of three decades navigating complex environments — Wall Street trading floors, courtrooms, boardrooms, early-stage startups burning through runway, and enterprise SaaS organizations managing nine-figure pipelines. But some of the most clarifying thinking I've done about leadership, risk, and decision-making hasn't happened in any of those places. It's happened on the water.

Sailing has been a constant in my life for as long as I can remember, and for years I treated it as a genuine escape — a hard boundary between professional intensity and personal restoration. What I've come to understand, though, is that the separation was always an illusion. The discipline that sailing demands, the instincts it sharpens, and the humility it enforces have shaped how I think about building companies in ways that are difficult to replicate any other way.

Reading Conditions in Real Time

The first thing sailing teaches you — and it teaches you fast — is that conditions are never static. Wind shifts. Currents run against your heading. A squall that looked like it would miss you by three miles is now bearing down at twenty knots. Your job as skipper isn't to execute the plan you made at the dock. Your job is to read what's in front of you right now and make the best decision with incomplete information.

That's not a metaphor for business. That is business.

When I was running revenue organizations in enterprise SaaS, one of the most common failure modes I watched play out — in my own teams and in competitors — was the stubborn adherence to a plan that conditions had already invalidated. A Q3 pipeline that looked healthy in May doesn't look the same after a macro shift in July. A product roadmap that made sense before a competitor launched a feature set that changed buyer expectations requires a different conversation with the market. The instinct to stay the course because "the plan is the plan" is exactly the same instinct that gets sailors into trouble.

Good sailors develop a nearly subconscious habit of constant environmental scanning. They're not paranoid — they're calibrated. They notice when something is shifting before the data makes it undeniable, and they begin adjusting early rather than reactively. I've tried to bring that same cadence into how I run teams. Early signals are real signals. Waiting for confirmation is often just delayed action dressed up as diligence.

The Discipline of Preparation Under Uncertainty

There's a tension at the center of sailing that I find genuinely instructive: you spend enormous energy preparing for conditions you cannot predict, and then you have to let go of the outcome. You check the weather, inspect the rigging, know your charts, brief your crew — and then the ocean does whatever it does.

Founders and executives who haven't internalized this distinction often fail in one of two directions. Either they over-plan and become brittle when reality diverges from the model — and it always diverges — or they under-prepare and dress up their lack of rigor as "staying agile." Neither works. The sailor's discipline is something different: rigorous preparation combined with genuine psychological flexibility about outcomes.

At HedgeNova, where we're building AI-powered tools for institutional investors, I think about this constantly. We operate in a domain — AI applied to financial markets — where the pace of change in both technology and regulation makes long-horizon planning genuinely difficult. What we can control is the quality of our preparation: the depth of our domain expertise, the rigor of our architecture decisions, the relationships we build before we need them. What we can't control is when the market is ready, what a competitor announces, or what a regulatory body decides. Sailing trained me to invest heavily in the former and hold the latter loosely.

Respecting the Water — And the Market

The most important lesson sailing has taught me is also the simplest, and it's the one that's hardest to maintain during a run of success: the water doesn't care about your plans, and neither do markets.

I've watched capable people — lawyers who became executives, bankers who became founders, operators who built one successful company and assumed the formula would transfer — get humbled by this reality. Success creates a narrative about why you succeeded, and that narrative tends to over-index on personal brilliance and under-index on timing, conditions, and luck. Sailing is a particularly efficient corrective to that kind of thinking, because the consequences of arrogance are both immediate and physical. The ocean has no interest in your track record.

"Overconfidence on the water doesn't cost you a deal or a quarter. It can cost you the boat — or more. That stakes-clarity has a way of resetting your priors about what you actually control."

In business, I've tried to carry that same respect for what I don't control. Markets are not adversaries you outthink — they're environments you navigate. The companies I've seen fail most spectacularly, particularly in fintech and AI where I've spent the most time, weren't outcompeted. They were humbled by conditions they refused to take seriously: a rate environment that made their model unworkable, a regulatory shift they'd dismissed as unlikely, a customer base that wasn't as locked in as their NPS scores suggested.

Crew, Communication, and Shared Situational Awareness

One thing that doesn't get discussed enough in sailing-as-leadership analogies is the crew dynamic. Sailing alone is meditative and instructive in its own way, but sailing with a crew surfaces an entirely different set of lessons. A skipper who hoards decision-making, fails to brief the crew on the plan, or dismisses crew observations about conditions they've noticed — that skipper is creating unnecessary risk at exactly the moments when clarity matters most.

I've found this maps directly onto how I try to build leadership teams. Shared situational awareness isn't just nice to have — it's a risk management function. When everyone on the team understands what we're navigating toward, what the known hazards are, and what decision authority they carry, the organization responds faster and more intelligently when conditions change. The alternative — a hierarchy where information flows up and decisions flow down — works fine in calm weather. It breaks down when things move fast.

Why I Keep Going Back

People sometimes ask whether I find sailing relaxing. The honest answer is: sometimes. But that's not really why I do it. I do it because the water imposes a kind of clarity that's hard to find anywhere else — a forced engagement with the present, a genuine respect for forces larger than yourself, and a continuous practice of making good decisions with incomplete information under real consequences.

• Read conditions early — don't wait for certainty that won't come
• Prepare rigorously, hold outcomes loosely — control what you can, release what you can't
• Stay humble about what you don't know — the water, and the market, will correct you
• Build crew situational awareness — shared context accelerates good decisions under pressure

Thirty years across industries and roles has given me a lot of frameworks for thinking about business. But some of the most durable ones came not from any MBA curriculum, not from any deal I closed or company I built, but from time on the water — learning to respect something that genuinely doesn't care whether I succeed.

That's the lesson I keep coming back to.