Finding Flow State: The Untapped Secret to Performance

I’ve spent the better part of a decade chasing flow state on rivers, mountains and oceans — the point where the noise drops away and performance stops feeling like effort. It shows up on a kayak run when the line through the rapid becomes obvious instead of calculated. It shows up on the boat, hours into a rowing shift, when the stroke stops being something you think about and just becomes something you do.

Flow gets talked about like it’s a stroke of luck — a good day that happens to you. It isn’t. It has conditions, and those conditions can be built deliberately.

The task has to sit at the edge of your ability

Flow doesn’t happen on tasks that are too easy — you get boredom instead. It doesn’t happen on tasks that are too hard either — you get anxiety. It happens right at the edge of what you can currently do, stretched but not overwhelmed. In a team context, that means matching people to challenges precisely, not generously — under-stretching is as costly as over-stretching.

Feedback has to be immediate

On the water, feedback is instant: the boat moves or it doesn’t, the line works or it doesn’t. Most workplaces bury feedback in quarterly reviews, which is far too slow for flow to take hold. Tightening the feedback loop — even informally, even just “that worked” or “try it differently” — does more for performance than almost any other single change.

Distraction is the real enemy, not difficulty

Hard work doesn’t break flow. Interruption does. The conditions that produce flow on an expedition — no phone, one clear task, a defined block of time — are exactly the conditions most workplaces are structured to prevent. Protecting blocks of undistracted time is a leadership decision, not a personal productivity hack.

Flow isn’t the reward for good performance. It’s the mechanism that produces it — which means it’s worth designing for, not waiting for.