The steps you are holding are the ones you lose
Every page that explains this opens the same way: a definition, a capacity figure, and a list of signs of overload. All of it is accurate, and none of it tells you what to do on a Tuesday afternoon with a job you have now read four times and still not started.
The useful framing is narrower than the definition. Working memory is the small amount of information you are holding right now in order to do the thing in front of you, and the important word is not holding, it is also. You are holding it and also doing the work, and those two draw on the same space. That is the entire mechanism, and it is why a job that is obviously simple can be genuinely impossible to begin.
Nothing below depends on knowing your own capacity, which you cannot measure at your desk anyway. It depends on noticing what you are carrying, which you can do in the middle of a stall.
Losing your place is not the same as forgetting
These get treated as one problem and they behave differently. Forgetting means the information has gone: a name, a figure, a thing somebody asked you for. Losing your place means the information is all still there and you no longer know which part of it you were on.
You can tell them apart by what recovery feels like. Forgetting feels like a blank you have to go and fill from somewhere else. Losing your place feels like having to run the whole thing again from the top, because the only record of what was already done was the fact that you were holding it.
That second one is the expensive failure, and it is the one almost nobody plans for. A four step job interrupted twice can take longer than a twelve step job done straight through, and the person doing it concludes they cannot concentrate, when what actually happened is that the state was destroyed twice and rebuilt from scratch twice.
Three things are being held, and only one is the work
Watch yourself partway through an ordinary administrative job and there are three separate things being carried at the same time. Naming them is useful because they are not equally necessary and they do not cost the same.
- The next step. What you are about to do, which you cannot look up because you decided it in your head a moment ago and it exists nowhere else.
- The state. Which parts are already done and which are not. This is the one nobody writes down, and it is the one an interruption destroys completely.
- The reason. Why this job is being done at all, which is what stops you drifting into a neighbouring job halfway through and calling that progress.
Why a to do list does not empty your head
The standard advice is to write it down. The advice is right and it usually does not work, and the reason is what gets written rather than whether anything was written.
A list of headings is a list of jobs, not a list of steps. "Sort out the insurance" on paper holds exactly as many steps in your head as "sort out the insurance" in your head did. The load moves out only when the written thing is small enough to begin without deciding anything further. A step you can start without thinking has genuinely left your head. A heading you still have to unpack has not, and the list has only recorded that the job exists.
This is why diligent list keepers can still stall every morning with a tidy system in front of them. The capture habit is working and the decomposition is missing, and because both of them look like writing things down, the gap is almost invisible from the inside. The task paralysis guide here covers what that stall feels like from the other side.
The interruption cost, and why the job grows afterwards
An interruption does not take away the minute it occupied. It takes away the state, and the state was the only thing that knew where you were.
So you come back, read the document again, check which emails you already sent, open the folder again to see what is in it. None of that is new work and all of it is time, and it is also the part that makes the job feel bigger than it was, because you have now done the early steps more than once.
The move that fixes this is small and feels pointless at the moment it is needed. Before you turn away, write one line saying what is done and what is next. It feels unnecessary precisely because you are still holding the information while you write it, which is exactly why it is cheap then and expensive later. A sticky note with two half sentences on it is worth more than a careful plan made yesterday.
What to put outside your head, in order
Externalising everything is its own job and gets abandoned in the first difficult patch. A short list in priority order survives.
- The next action, written small enough that starting it requires no further decision.
- The state, updated whenever you stop, including when you stop for a moment.
- Anything exact. A reference, a code, a spelling, an address. One of these costs about as much to carry as a whole step and it is the cheapest thing in the world to write down.
- The reason, once, at the top. It stops the drift into a neighbouring job and it never needs updating.
- Nothing else. A system that needs maintaining is a second job, and the second job is the one dropped when the first gets hard.
Where Task Assistant sits in this
Task Assistant works on the decomposition step rather than the capture step, which is the half most tools leave to you. You say what you are stuck on, and it comes back as small steps with time estimates attached, and a step of that size is the form that actually leaves your head rather than sitting in a list still folded up.
The session then runs one step at a time with a companion on screen, which keeps the state in front of you instead of inside you. There are no streaks, because a missed day that counts as a loss is a reason not to come back. The task breaker is the same decomposition in a browser with nothing to install, and it is the fastest way to find out whether the thing stopping you was the size of the step rather than your attention.
What it does not do is remember things for you in general, and it is not a notes app. It is aimed at one specific load, the held next action, and that load is behind a surprising share of the jobs people read four times.
The short version
If none of the above gets used, these five lines are the part that matters.
- A task you can hold is a task you can start. A task you have to hold is a task that waits.
- If you are re-reading something, what you lost was the state, not the content.
- Write the state, not just the plan, and write it before you turn away rather than after.
- A heading on a list is still in your head. Only a startable step has left it.
- Put the exact things outside first. They cost the most to carry and the least to record.
Try it now
Questions
What is working memory?
The small amount of information you hold while actively doing something with it. The holding and the doing draw on the same space, which is why a task with several steps kept in your head is harder than the same task written out, even though the work itself has not changed.
Why do I keep losing track in the middle of a task?
Because the record of what you had already done existed only in your head. That is place-keeping rather than memory, and it fails first under interruption. The fix is to put the state somewhere outside you, which takes seconds while you still hold it and cannot be done at all once it is gone.
Does writing things down actually help?
Only if what you write is startable. A heading such as sort out the insurance moves nothing, because every step is still held in your head. A line such as find last year policy number in the email folder has genuinely left your head, and that is the difference between a list that works and a list that accumulates.
Why does an interruption make a task feel bigger than it was?
Because you repeat the early steps. The interruption destroys the state, so on returning you re-read, re-check and reopen things to work out where you were. That repeated work is real time and it is also why the job feels longer than the estimate you made of it.
How do I tell whether my problem is attention or working memory?
Ask what happens when the steps are written out in front of you. If the work then proceeds, the load was the problem. If you have a clear single next step on paper and still cannot begin it, that is a different failure, and the executive dysfunction guide here separates the kinds.
Can working memory be trained?
Whatever the answer turns out to be, it is a slow route, and the fast one is available this afternoon: hold less. Reducing what you are carrying works immediately and does not depend on changing anything about you, which makes it the better first move regardless of what training can do.