Stay in the Text: Keyboard-First Writing for Flow

The most useful keyboard habit is to keep your hands on the keys while a thought is still warm — not to shave seconds, but to avoid breaking the sentence you are halfway through. Reach for the mouse and you trade a fast, shallow interruption for a slow, deep one. The honest case for keyboard-first writing is flow, not speed.

That distinction matters because the speed case is built on sand. As Dan Luu put it after digging into the literature, "The widely cited studies on mouse vs. keyboard efficiency are completely bogus." ¹ So this is not a "save N seconds per task" post. It is a how-to for staying inside the text — a small starter set of shortcuts, a command palette as the keyboard-first hub, and the honest trade-offs — built so the habit lives in your files and travels across any editor you ever open.

Are keyboard shortcuts actually faster for note-taking?

No, not in any way the famous studies prove. The often-repeated "keyboard beats the mouse" claim traces back to experiments nobody can reproduce. The real benefit is different: a keyboard-first habit keeps you in flow and cuts the friction of leaving the text, and because it lives in your hands and your files, it travels with you between editors.

Dan Luu's takedown is blunt about why the speed claim collapses. Of Bruce "Tog" Tognazzini's famous Apple study, he writes that "the result is unreproducible because 'Tog' not only doesn't cite the details of the experiments, Tog doesn't even describe the experiments and just makes a blanket claim." ² When the canonical source for "the keyboard is faster" will not even describe its method, the honest move is to stop quoting a speed number and ask the better question: what does leaving the text actually cost you?

What leaving the text actually costs

It costs flow, and flow has a price you can feel. The cost of an interruption is not mainly lost minutes — it is stress and effort. In a controlled study, people who were interrupted finished their work just as fast, but paid for it in strain. The toolbar trip is a small self-interruption, repeated hundreds of times a day.

The clearest evidence comes from Gloria Mark and colleagues at UC Irvine. In their CHI 2008 paper, they found that "people completed interrupted tasks in less time with no difference in quality. Our data suggests that people compensate for interruptions by working faster, but this comes at a price: experiencing more stress, higher frustration, time pressure and effort." ³ You do not lose the time. You lose the calm.

And the strain arrives quickly. The same study reports that "after only 20 minutes of interrupted performance people reported significantly higher stress, frustration, workload, effort, and pressure." ⁴ Twenty minutes of breaking your own focus to hunt a menu is enough to feel it. The point of staying on the keyboard is to protect the state psychologists call flow — "the mental state in which a person performing some activity is fully immersed in a feeling of energized focus, full involvement, and enjoyment in the process of the activity," a concept introduced by Mihály Csíkszentmihályi in 1975. ⁵ Constant trips to the toolbar are flow's quiet enemy.

The small starter set

Learn the handful of moves that cover the editing you actually do, not the full keymap. Most of writing is moving the cursor, selecting, formatting, saving, and finding. A short, memorized core handles all of it, and the same moves exist in nearly every editor. Add the rest only when you reach for the mouse twice.

A starter set worth memorizing first:

• Move and select by word and line — jump the cursor a word or a paragraph at a time; hold the selection modifier to grab text without dragging.
• Bold, italic, and links — the three formatting moves a writer makes most; in Markdown these wrap the selection.
• Save, undo, and redo — the safety net; the muscle memory you never want to think about.
• Find and replace — search inside the document instead of scrolling for a phrase.
• The command palette — the one shortcut that reaches every other command (see below).

Note what is missing: there is no "twenty shortcuts cover eighty percent" rule here, because there is no honest study behind that number. The defensible claim is softer and truer — a small learnable core covers most of the editing you do, and you will discover your own core faster by noticing which mouse trips you repeat.

The five-minute version

Spend five minutes wiring the core into muscle memory, then write normally and let repetition finish the job. You do not study a keymap; you write a real note and force yourself to use keys for the five moves above. The cost is real, a few clumsy days, and naming it honestly is what makes the habit stick.

1. Pick the five moves above. Write them on a sticky note, or in a scratch note you keep open.
2. Write one real paragraph using only keys. No mouse. It will feel slow. That feeling is the learning, not a verdict on the method.
3. When you reach for the mouse, stop and find the key. The interruption you notice is the one you will replace.
4. Open the command palette once per session (next section) and run one command by name instead of hunting its menu.
5. Repeat for a week. Flow is a habit, not a setting. The first three days are the tax; the rest is the dividend.

The command palette: one shortcut to reach the rest

A command palette is a keyboard-driven, fuzzy-matched menu of every command an app can run, the hub that means you never have to memorize the rest. Open it, type a few letters, run the command. It is the single highest-leverage key to learn, because it turns "I don't know the shortcut" into "I don't need to."

This is not a fad. The pattern is decades old and now industry-baseline. Sublime Text, which first appeared in 2008, shipped "a 'command palette' with adaptive matching for quick keyboard invocation of frequently used commands." ⁶ Visual Studio Code's own documentation makes the same promise plainly: "The Command Palette provides access to many commands. You can run editor commands, open files, search for symbols, and see a quick outline of a file, all using the same interactive window." ⁷

The reason the palette is the keyboard-first hub — not just one feature among many — is reach. As VS Code's docs put it, its palette "brings up the Command Palette. From here, you have access to all functionality within VS Code, including keyboard shortcuts for the most common operations." ⁸ The palette is where you learn the rest of the keys: run a command by name today, and it shows you the shortcut for next time. The pattern's deep ancestor is older still — it dates back to Emacs's M-x, the keyboard-first "run any command by name" prompt that long predates the modern editor.

How a command palette note workflow fits together

Drive the whole writing session from the palette, and the keyboard becomes the only surface you need. Create a note, search your notes, jump to a heading, toggle a format, export: each is a command you summon by name, hands still. The workflow is not "memorize everything." It is "memorize the palette, then ask it for the rest."

Here is the shape of a keyboard-only writing session, framed by what the palette gives you:

• Start — open the palette, type "new note," write.
• Move — jump to a heading or search a phrase instead of scrolling; navigating a long note by its outline is one palette command away.
• Format — wrap a selection in bold or a link with the core shortcut, or run the command by name if you forget the key.
• Find — search across notes from the same window rather than opening a separate screen.
• Finish — export or copy via a command, hands still on the keys.

The friction this removes is the dozens of tiny toolbar trips per session — each a small self-interruption of exactly the kind the CHI 2008 study measured. ³ Vendors notice this too: Evernote's own help page frames its shortcuts as flow, not speed, promising they reduce "friction in your note-taking process, allowing for a seamless, fast experience that keeps you focused on the content rather than the controls." ⁹ Focused on the content rather than the controls — that is the whole point, stated by a company with no reason to undersell speed.

Common mistakes

The usual ways this goes wrong are chasing a speed number, over-memorizing, and binding the habit to one app. Each one quietly undoes the flow you were after, and each is avoidable once you can name it. Watch for these five; the worst share one root, optimizing for the wrong thing instead of for staying inside your text.

• Chasing speed. If your reason for learning shortcuts is "be X percent faster," you have adopted a goal the evidence does not support — Dan Luu's whole point is that those numbers are unreproducible. ¹ Aim for flow and friction instead; those are real and felt.
• Over-memorizing. Trying to learn the entire keymap at once is how people quit in week one. Learn the five-move core plus the palette; let everything else arrive when you reach for the mouse twice.
• App-locked muscle memory. If your shortcuts only exist inside one proprietary toolbar, you have built a habit you cannot take with you. Favor the moves that are near-universal — cursor and selection, the standard format keys, the palette — so the skill survives a switch of editor.
• Skipping the honest trade-off. There is a genuine upfront learning cost. Pretending otherwise sets you up to give up the first time it feels slow. Budget a clumsy week.
• Assuming flow requires constant motion. Worth surfacing the contrary view: even a sympathetic reader of the flow argument has written, "I doubt that flow must be based on constant action." ¹⁰ Staying on the keyboard is not about never pausing — it is about not breaking a thought to operate the interface. Some of your best writing happens while your hands are still.

How this works in MNMNOTE

In a plain-text editor that runs in your browser, keyboard-first editing is the default, not a setting you hunt for, and the habit lives in your files, not the app's chrome. Because your notes are open Markdown, the moves you learn keep working wherever you open them. A toolbar belongs to one app; the habit is yours.

That portability is what the speed listicles never mention: the skill and the words travel together, across any editor you ever choose. (Whether the keyboard helps you think better than a pen is a different question — this is about staying inside the text once you are typing.)

Frequently Asked Questions

These are the questions writers type into a search bar before learning shortcuts: whether the speed claim is real, whether the effort pays off, what a command palette even is. Each answer below leads with the honest version, flow over speed, a real learning cost named plainly, and a habit built to be portable rather than locked to one app.

Are keyboard shortcuts actually faster for note-taking?

Not in any way the famous studies prove — Dan Luu calls them "completely bogus," because the canonical experiments are unreproducible. ^{1 2} The honest benefit is flow, not measured speed: staying on the keyboard avoids the small self-interruptions of reaching for a toolbar, and interruptions are what cost you stress and effort. ³

Are keyboard shortcuts worth it?

Yes — for flow and friction, not for a speed promise. The 2008 study by Gloria Mark and colleagues found interrupted work is finished just as fast but "at a price: experiencing more stress, higher frustration, time pressure and effort." ³ Fewer trips away from the text means fewer of those small costs. Budget a clumsy week.

Keyboard shortcuts vs mouse — which is faster?

The famous studies claiming the keyboard wins are unreproducible, so "X percent faster" is not a claim you can defend. ^{1 2} Reframe the question: the keyboard keeps you in the text and the mouse pulls you out of it, and the cost of being pulled out is broken focus. Optimize for staying in flow, not for a stopwatch.

What is a command palette, and how do I use it?

A command palette is a keyboard-driven, fuzzy-matched menu of every command an app can run. You open it, type a few letters, and run the command without a mouse. VS Code's docs describe it as a single window giving "access to all functionality." ^{7 8} Sublime Text pioneered the modern version in 2008. ⁶

Is the command palette worth learning?

It is the highest-leverage single key to learn, because it reaches every other command, so you no longer have to memorize the rest. The real cost is the upfront habit of opening it instead of hunting a menu. Learn it first: run a command by name today and the palette shows you its key for tomorrow.

Does keyboard-first writing lock me into one app?

It does not have to, and choosing portable moves is the point. Cursor and selection keys, the standard format shortcuts, and the command palette are near-universal across serious editors, and a plain-text Markdown file opens anywhere. Build the habit on those, store your notes as open files you control, and the skill — and the words — travel with you.

A keyboard habit will not put a number on your speed, and the studies that promised one never could — but it will keep you inside the sentence you are writing, and it will follow your files into whatever you open next. If you want a place to practice it that keeps your notes as plain text on your own device, mnmnote.com runs in your browser.