Fixing one sentence feels free. It is not. The fix itself takes seconds, but the loop around it, switch, paste, prompt, wait, paste back, is where your time and your focus quietly leak away.
We watched people fix ordinary text: an email line, a Slack message, a form field. Almost nobody fixes in place. They copy the text, open another tab, paste it into a chat tool, type an instruction, wait for a reply, copy the result, switch back, and paste it in. Then they reformat, because the paste broke the styling.
The loop, timed
Here is a typical single fix, broken into the steps most people actually perform. The times are conservative averages, not worst cases.
| Step | What happens | Time |
|---|---|---|
| 1 | Switch tab, open another tool | ~30s |
| 2 | Copy, paste, wait for a response | ~45s |
| 3 | Write the instruction, iterate once | ~60s |
| 4 | Paste back, reformat | ~30s |
| Total per fix | ~2 min 45s |
Under three minutes. That sounds small, until you count how often it happens. Most knowledge workers make this kind of edit several times an hour without noticing.
The part the clock does not show
The bigger cost is not the seconds. It is the context switch. Every time you leave the page you were working on, you drop the thread of what you were doing. Coming back, you have to reload it: where was I, what was I about to say next?
The fix takes two seconds. Rebuilding your concentration afterward takes far longer.
Research on interruptions has found the same pattern for years: the recovery time after a break is many times longer than the break itself. A one-minute detour can cost several minutes of lost momentum. Multiply that by four small fixes an hour and the math stops being trivial.
What it adds up to
- Four fixes an hour at three minutes each is twelve minutes of loop, every hour.
- Add the recovery tax on focus and the felt cost is higher still.
- Over a working week that is hours spent not on writing, but on the mechanics of correcting it.
Removing the loop, not speeding it up
The usual response is to make each step faster: a quicker tool, a saved prompt, a keyboard shortcut to switch tabs. That helps at the margins, but it accepts the loop as a given. The loop is the problem.
The alternative is to fix text where it already lives. No new tab, no copy, no paste, no prompt. You select the sentence, right-click, and the corrected version appears in place, ready to accept. The four steps collapse into one, and the context switch never happens.
Why in-place matters more than fast
- Speed shrinks each step. In-place deletes the steps entirely.
- No tab switch means no lost thread, so there is nothing to recover.
- The result stays editable, so you keep control without leaving the page.
That is the whole point of Prose: not a faster detour, but no detour. If you want to see why it only corrects and never rewrites, read fix, do not rewrite.
