You had the perfect sentence in your head. You started typing it. Halfway through, the second half evaporated.
You stare at the screen, half-sentence frozen in place, trying to retrieve what you were about to say. It doesn't come back the same. You write something close, but flatter. You move on, vaguely annoyed.
This happens to almost everyone who writes for a living, dozens of times a day. Most of us blame distractions: the Slack ping, the open tab, the cat. The real culprit is usually sitting under your fingertips.
Writing flow has a name. The psychologist Mihaly Csikszentmihalyi coined flow state to describe the feeling of effortless concentration where time disappears and the work seems to write itself. Writers love it, talk about it, chase it. And then they sit down at a keyboard that is structurally guaranteed to break it.
What writing in flow state actually is
Csikszentmihalyi spent decades studying people who lose themselves in their work: surgeons, climbers, chess players, novelists. He found a small set of conditions that reliably produce flow. A clear goal. A task that matches your skill level. Fast feedback. Unbroken attention.
Writing fits most of these naturally. You know what you're trying to say. You have the skill to say it. Each sentence gives you feedback right away (does it sound right or not?). The only condition that's hard to maintain is the last one: unbroken attention.
This is why most deep work advice centers on attention. Close the browser tabs. Put your phone in another room. Block your most distracting sites. The implicit promise is that if you remove all the external interruptions, flow will arrive on its own.
It usually doesn't.
The hidden flow-killer is your typing speed
The average adult types around 40 words per minute. The average person thinks and speaks at closer to 150. That gap isn't a small inefficiency. It's a constant micro-interruption, happening every few seconds, all day, every day you write.
Here's what the gap looks like in practice. Your brain produces a complete thought in two seconds. Your fingers need eight seconds to get it onto the page. For six of those seconds, you're not generating new ideas. You're *holding* an existing one in working memory while waiting for your hands. The longer you hold it, the more likely it is to leak.
When the thought leaks, you have two options. You stop typing and try to remember what you were saying, which kicks you out of flow. Or you keep typing whatever comes next, which usually means the second half of your sentence is weaker than the first. Either way, you've lost something.
Touch typists at very high speeds (80+ wpm) get partway out of this trap. A Psychology Today piece on touch typing and flow argued that fluent touch typing can "unclamp" the brain by removing the conscious effort of finding keys. That helps. But even at 80 wpm you're still running at roughly half the speed of your own thinking.
There's a second problem the keyboard creates. Every typo, every backspace, every red squiggle wakes up the part of your brain that edits. The editor and the generator are different mental modes. Flipping between them is the most reliable way to break flow there is.
Why "just focus harder" doesn't fix this
Most popular advice on writing flow treats the keyboard as a neutral instrument. Sit in the right chair. Play the right music. Write at the right time of day. Your words will flow. The hardware itself is never the suspect.
But focus is a finite resource, and your fingers are quietly draining it the entire time you write. Even with notifications off and a cleared desk, you're spending a chunk of your attention on the mechanical act of converting thought into keystrokes. The cleaner your environment, the more obvious this becomes. You notice the friction precisely when there's nothing else to blame.
This is also why many writers feel more fluent talking through an idea than writing it down. In conversation, the speed of your output matches the speed of your thinking. Nothing has to be held back. Your brain isn't allocating working memory to wait on your hands.
The fix is to close the gap, not to wish it away.
Three habits that protect your flow
These three changes do most of the work. None of them require a new app, though one of them gets easier with the right tool.
1. Separate drafting from editing
When you write, your job is to get the idea out. When you edit, your job is to make it sharper. Doing both at once is what produces the half-finished sentence and the blinking cursor. Write the messy version first. Fix it on a second pass.
2. Work in 60–90 minute blocks
Flow takes about 15 minutes to enter and collapses the moment you context-switch. A single one-hour block, phone in a drawer, one document open. Anything shorter and you've barely warmed up.
3. Close the speed gap
This is the one most writers skip. If your output device runs at 40 wpm and your brain runs at 150, you will lose ideas no matter how well-rested or focused you are. The realistic options: get your typing speed substantially higher (years of practice for modest gains), or stop typing as your primary input. Dictation, done well, runs at roughly the speed of your thinking. See why voice is faster than the keyboard for the underlying numbers.
If you've already dialed in your environment and you're still losing the second half of every sentence, the keyboard is the variable left to change.
If you've tried dictation before and given up because the raw transcript needed too much cleanup, the tooling has changed. Voicr polishes your speech into clean, finished text in one step: hold FN, speak, paste. That removes the editing tax that made dictation feel like more work than typing in the first place.
The case for speaking instead of typing
Speaking is the only writing input fast enough to keep up with thought. That's the whole argument, and it's a strong one. But it's worth being honest about what changes when you switch.
What you gain: - Speed. Most people speak around 150 wpm without trying. Roughly 3–4x typing speed. - Continuous thought. You can finish a paragraph before your hands would have finished the first sentence. Ideas don't have time to leak. - A relaxed body. Shoulders drop, wrists rest. Long writing sessions stop hurting. - Less editor brain. No red squiggles. No typos to fix mid-thought.
What's harder: - Privacy. You can't comfortably dictate in a quiet coffee shop or an open office. Speaking out loud is socially loaded in a way typing isn't. - Punctuation and structure. Raw dictation gives you a wall of words. You either say "comma, new paragraph, quote" out loud, or you use a tool that handles structure for you. - The first week. It feels strange to talk to your computer. Most people get past this in three or four sessions.
For long-form writing, email, Slack messages, doc comments, meeting notes, and journaling, the tradeoffs land firmly in favor of speaking. For dense code or precise legal language, typing still wins.
How to set up a no-friction dictation workflow
The setup matters more than the tool. A dictation workflow that requires you to open an app, click a button, wait for a window, copy a result, and paste it somewhere is not a flow workflow. It's a worse version of typing.
The shortest path looks like this: 1. Bind dictation to one key you already hold. A function key, a modifier key, or a side mouse button. The goal is no app switching, no cursor movement. 2. Speak in complete thoughts. Don't dictate word by word. Let yourself say a whole paragraph before you stop. The polishing step is much better with more context. 3. Use a tool that cleans the output. Raw transcripts aren't finished text. You want something that removes "um" and "uh," fixes obvious grammar slips, and structures the result so it's ready to paste. 4. Match the style to the app you're in. A Slack message should sound casual. An email to a client should sound professional. A doc comment should be concise. The same dictation can produce all three depending on context.
That last step is where most setups stall, because it usually requires you to manually pick a style each time. A few tools handle it automatically by detecting the active app. Worth looking for if you write across many surfaces in a single day. A practical example is laid out in this dictation workflow that saves two hours a day.
Try this tomorrow
If you want to test the typing-is-the-bottleneck theory on yourself, here's a 20-minute experiment.
Pick a writing task you've been putting off. An email you owe someone, a doc you've been drafting, a journal entry. Set a 20-minute timer. Spend the first 10 minutes typing it the normal way. Spend the second 10 minutes speaking the same content into any dictation tool.
Compare the two. Pay attention to: - How much you produced - Whether you lost the thread of your ideas at any point - How your shoulders and wrists feel afterward
Most people are surprised by the volume difference. The more interesting result is usually the second one: the dictated version often sounds *more* like you, because you didn't have time to second-guess yourself out of your own voice.
What to try next
Flow isn't a mystical state. It's a set of conditions, and one of those conditions is that your output has to keep pace with your thinking. The other advice (block your time, kill notifications, separate drafting from editing) is good. It just works much better when the keyboard isn't quietly eating half your ideas.
The fastest way to start is to dictate the next thing you would have typed. An email. A Slack message. A paragraph of a doc. If you want a setup that handles the polishing automatically (works from any Mac app, hold-to-talk, paste-ready text), Voicr does exactly that. Hold FN, speak, release, paste. The thought arrives at the page roughly as fast as you thought it.