How to remember what you were doing, when fourteen windows are open

The interruption is not the expensive part. Someone asks you something, you answer in ninety seconds, and you turn back to the screen.

The expensive part is the next twenty minutes: reading your own terminal output to work out what state the migration is in, opening three tabs to find the one you had a question about, and trying to recall what you had decided about row 40 before the phone rang.

That is not a discipline problem. It is a storage problem. The information you needed was in working memory, working memory is volatile, and nothing on your screen was holding a copy.

Why the usual answers do not work

"Close more windows." Fine for windows you are finished with. But most open windows are open precisely because the work in them is not finished, so closing them does not remove the state — it just deletes the only remaining hint about it.

"Write it in your task manager." A task manager is read when you open it. The moment you need this particular information is the moment you look at the window, and at that moment the task manager is closed. The note is correct and unread.

"Use sticky notes." Better, because they are visible. Worse, because a desktop sticky note floats over everything and belongs to nothing: ten of them are a wall, and none of them says which window it is about.

"Just remember." This works right up until Friday afternoon, and then it costs you Monday morning.

The system, in three rules

None of this requires software. It requires that the note be in the right place, and software only makes that easier.

Rule 1: Write the state, not the task

The useless version: "finish the importer."

The useful version: "half done, the failing case is empty rows, branch feat/import is pushed."

You are not writing a to-do. You are writing the thing you would have to reconstruct — the two or three facts that took you an hour to establish and would take another hour to re-establish. If a sentence would be obvious to you in a month, it does not belong in the note.

Rule 2: Write it before the interruption, not after

The habit worth building is a single keystroke at the moment you stand up. Not at the end of the day, when the state is already half gone — at the moment something takes you away.

This is the reason a shortcut matters more than it sounds. Anything that requires switching applications will not happen, because at the moment you need to do it you are already halfway to the meeting.

Rule 3: Put the note where you will next look

Which is on the window. Not on the desktop, not in a document, not in a different app — on the thing whose meaning you will have forgotten.

This one rule does most of the work, because it removes the retrieval step entirely. You do not remember to check the note. The note is on what you are already looking at.

What a good state note looks like

Four fields, and three of them are one word:

• Status. Blocked, waiting, in progress, review, done. One glance across six windows and you know where everything stands.
• Title. What this window is. "Staging box." "Q3 forecast, sent version."
• The state. One or two sentences: what is true right now, what would surprise you if you forgot it.
• The next step. What you would do first if you sat down again.

The status is doing more work than it looks like. Once six windows each carry a coloured word, you stop reading them and start scanning them — which is the difference between a system you keep using and one you abandon in a week.

The awkward part: Monday

Everything above works until you shut the machine down, and then it collapses — unless the notes come back attached to the right windows.

This is genuinely hard, and it is worth knowing why: a window has no lasting identity. Its ID is reused after it closes, its title changes while you work, and its app will open forty more that look identical. Anything that claims to reattach notes after a restart is doing a fair amount of guessing, and the good implementations tell you when they are guessing.

If you want the detail, it is in why a window is so hard to recognise twice.

Try it for one week

Pick your two most confusing windows — the ones you have to work out from scratch every time you come back to them. Put a state note on each. Do nothing else.

If the two notes are still there and still useful on Friday, the system works for you and you can extend it. If they are not, you have lost nothing.

That is why WindowNote's free tier is two windows and has no time limit: two is enough to find out, and a week is enough to know.