Flow state: Why fragmented thinking is worse than any interruption
Nick Moore set out to write about protecting developer flow state from Slack messages and meetings, then read over a dozen research papers on the topic and changed his mind about what the real threat is. Mihaly Csikszentmihalyi coined “flow state” in the 1970s to describe painters who cared more about the act of painting than the finished work; the term later spread to athletes (Jimmy Johnson credited it for the Dallas Cowboys’ 1993 Super Bowl win) and eventually to developers, where it got flattened into a synonym for focus.
His core finding: external interruptions get all the attention, but internal fragmentation, developers interrupting their own flow with rote tasks like writing commit messages, does more damage. A 2018 study found 81% of participants predicted internal interruptions would be less disruptive than external ones, and were wrong.
Fichamento#
- Flow requires a specific alignment of skill and challenge, not just uninterrupted time. Work that’s emotionally hard but low-skill produces alertness, not flow; work that’s high-skill but low-challenge produces confidence, not flow.
- A 2023 study grouped flow barriers into three categories: situational (interruptions, distractions), personal (work too easy or too hard), and interpersonal (poor management, poor team dynamics).
- A 2018 study on interruption type: self-interruptions are more disruptive than external ones because they extend the suspension period and increase nested interruptions, even though 81% of the study’s participants predicted the opposite.
- Rote development tasks (writing a commit message right after finishing a coding section, for example) can break flow just as thoroughly as a Slack ping, without registering as an “interruption” at all, which leaves developers unaware of where their lost focus actually went.
- Three concrete levers cited from the research: reflective goal-setting and nudging (a 2018/2023 study pair found 80% of participants said daily reflection helped productivity); reducing technical debt (a 2018 study found developers lose 23% of working time to testing, code analysis, and refactoring caused by tech debt); and making information easier to find (2023 Stack Overflow survey: 54% of developers say waiting on answers disrupts their workflow, 64% hit knowledge silos at least five times a week, 63% spend 30+ minutes a day searching for answers).
- Moore’s framing throughout: staying in flow isn’t purely an individual discipline problem. Reducing internal fragmentation requires team-level investment in tooling, documentation, and workflow design, not just turning off notifications.