Flow

Flow is a state of complete absorption in an activity, where you’re so focused that you lose track of time and stop thinking about yourself. The psychologist Mihaly Csikszentmihalyi identified that it happens in a specific zone: the task has to be challenging enough to demand your full attention, but not so hard that you get frustrated, and not so easy that you get bored. When the difficulty matches your skill level, your attention locks in completely, the activity feels almost effortless, and people often report it as one of the most satisfying states they experience — more so than relaxing or leisure.

Do not use flow as a synonym for “I liked doing this.” Use it as a calibration tool. When someone is anxious, ask whether the challenge is too large for their current skill or whether they need a clearer next step, tighter feedback, or more support. When someone is bored, ask whether the work has become too small for them and whether the next useful move is a harder problem, a wider scope, or a different arena.

The manager’s move is not to chase flow everywhere. It is to know which work deserves protected attention and then defend the conditions around it. Clear goals. Fast feedback. Enough challenge. Fewer interruptions. If those conditions are missing, telling someone to “focus” is just managerial theater.

For a founder scaling from 10 to 100, flow gets harder to find and more important to understand. At 10 you probably lived in it — building, selling, solving problems directly. At 100, your job changes underneath you: deep work gets replaced by interruption-driven management, which is almost the perfect anti-flow environment, and a lot of founders quietly burn out here without naming why.

Flow is also what the top of the Dreyfus model feels like from the inside. The expert acts without deliberating, the monitoring mind goes quiet, and the work runs on its own. That is why flow shows up only once someone has real skill at the task: it is the felt signature of expertise, which is also why you can’t will it into being, you can only build the skill that lets it happen.

Use flow when the work is hard enough to be worth doing well and someone has the skill to rise to it — that’s the narrow band where it applies. Concretely: protect it for builders and individual contributors whose output depends on deep, uninterrupted focus, and design for it when you’re assigning stretch projects to people who are ready to grow. But don’t over-apply it. Flow is a poor frame for genuinely tedious work, for someone who’s underwater and needs help rather than immersion, or for the coordination-heavy parts of your own job — management is mostly interruption by design, and trying to force flow there just makes you resent the role. The manager’s real move isn’t chasing flow everywhere; it’s knowing which work deserves protected, absorbed attention and clearing the path for it, while accepting that plenty of the job legitimately isn’t that.

Flow was developed by Mihaly Csikszentmihalyi, a Hungarian-American psychologist, who began studying it seriously in the 1970s and laid it out fully in his 1990 book Flow: The Psychology of Optimal Experience. The origin is worth knowing: as a boy in Europe during and after World War II, he was struck by how some adults stayed resilient and whole amid chaos and loss while others fell apart, which set him on a lifelong question about what actually makes life worth living. His method was distinctive — rather than just theorizing, he had people carry pagers and report what they were doing and feeling at random moments (the “experience sampling method”), which is how he pinned down that absorbed, self-forgetting state across artists, athletes, surgeons, and everyday workers. He became a founding figure in positive psychology, and his core finding — that engagement, not ease, is where people report being most fulfilled — has held up well even as the term “flow” has been stretched and oversold in business writing since.