Why Writing It Down Makes You Better at the Next Task

You’ve probably heard the advice: don’t write things down, you’ll become dependent on your notes. Train your memory. Keep it all in your head so you stay sharp.

It sounds reasonable. It’s also wrong — or at least, it’s missing the bigger picture. A growing body of cognitive science research shows that when you save information externally, your brain doesn’t get lazier. It gets better at learning the next thing.

For developers juggling multiple work items, pull requests, and half-finished debugging sessions, this has real implications for how you work.

The saving-enhanced memory effect

In 2015, researchers Benjamin Storm and Sean Stone ran a series of experiments to test what happens to memory after you save information to an external source. The setup was straightforward: participants studied a list of items, then either saved the list to a file or didn’t. After that, they studied a second list and were tested on it.

The result was consistent across three experiments. People who saved the first list remembered the second list significantly better than those who kept everything in their heads. Storm and Stone called this the “saving-enhanced memory” effect — the act of offloading information to an external store freed up cognitive resources that improved encoding of whatever came next.[1]

This wasn’t a small effect. And it wasn’t just about reduced interference between the two lists. The researchers found evidence that saving information actively improved participants’ ability to learn new material, as though the brain recognized it could reallocate resources once the first set of information was safely stored elsewhere.

The tradeoff is real — but worth it

Before you take this as permission to never remember anything again, there’s a catch. A 2021 study by Grinschgl and colleagues confirmed the saving-enhanced memory effect but added nuance: people who offloaded information to an external tool remembered the saved items less well than those who kept everything internal. You trade recall of the thing you saved for better performance on whatever you do next.[2]

For most knowledge work, that tradeoff is clearly positive. You saved the information precisely so you wouldn’t need to recall it from memory. It’s sitting in your notes, your tool, your list. The whole point of writing it down is that you don’t have to remember it. What you do need is a sharp, unfragmented mind for the next problem — and that’s exactly what offloading gives you.

What cognitive offloading actually is

Risko and Gilbert defined cognitive offloading in a 2016 review paper as “the use of physical action to alter the information processing requirements of a task so as to reduce cognitive demand.” It’s a broad concept that covers everything from writing a shopping list to setting a reminder on your phone to bookmarking a browser tab for later.[3]

The key insight is that offloading isn’t cheating. It’s a fundamental cognitive strategy that humans use constantly, and it has measurable benefits. Your working memory — the mental workspace where you hold and manipulate information in real time — has hard limits. Roughly four items at once. Every piece of context you’re holding “just in case” is taking up space that could be used for active problem-solving.

When developers talk about being “in the zone” or achieving flow state, what they’re describing neurologically is a state where working memory is fully allocated to the problem at hand. No background threads. No mental bookkeeping. Just the code, the bug, the architecture. Anything that clears working memory of non-essential items makes that state easier to reach and sustain.

What this means for how you write code

Think about a typical afternoon. You’re working on a feature and you hit a blocker — maybe you need a response from another team, or you’re waiting on a CI pipeline. You switch to a different work item. Before you do, you have a choice:

Option A: Close the tab and trust yourself to remember where you left off. You were in PaymentService.ts, around line 340, and the failing test was related to a null check on the response object. You’ll remember that. Probably.

Option B: Spend 30 seconds writing a note — “left off at PaymentService.ts:340, failing null check on processPayment response” — and then switch.

Option A feels faster. But Storm and Stone’s research says Option B doesn’t just preserve context for when you come back. It actively makes you better at the next task you pick up. Your brain treats the note as a signal that it can safely release that context from working memory, freeing up capacity for the new problem.

Option A keeps the old context loaded in the background. You might not be consciously thinking about PaymentService.ts while you work on the next item, but your brain is still holding fragments of it — what researchers call attention residue. That residue makes you slower, less focused, and more prone to errors on the thing you’re supposed to be doing now.

Building offloading into your workflow

The research is clear, but knowing about cognitive offloading and actually doing it are different things. The problem is friction. If saving context takes effort — opening a separate notes app, finding the right page, writing enough detail to be useful later — you’ll skip it when you’re busy, which is exactly when you need it most.

This is why we built context capture directly into TicketHop. When you’re working in Azure DevOps and you need to switch tasks, you can attach a private markdown note to any work item in seconds. Hit Ctrl+K (or Cmd+K on Mac), click into the work item, and write your note. It stays attached to the work item itself — not in a separate doc, not in a Notion page you’ll forget about.

The note is there the next time you open that work item, whether that’s two hours later or two weeks later. No searching, no trying to remember where you wrote it down.

TicketHop also automatically tracks every work item you visit, which is cognitive offloading you don’t even have to think about. You don’t need to remember which work items you touched this week. Your visit history is already there, sorted by recency, searchable by keyword or ID. That’s one less thing your working memory needs to hold onto.

The myth of the lazy brain

The persistent fear that external tools make your memory weaker comes from a misunderstanding of how memory works. Yes, you’ll remember the specific saved items less well — Grinschgl’s research confirmed that. But memory isn’t a fixed resource that degrades with disuse. It’s a dynamic system that allocates capacity based on demand.

When you tell your brain “this information is safely stored somewhere else,” you’re not making it lazy. You’re redirecting its resources. The same way a developer wouldn’t hold a database query result in a local variable when they could just re-query when needed — your brain is being efficient, not weak.

For developers who are already battling context-switching fatigue from dozens of daily interruptions, that efficiency matters. Every scrap of working memory you reclaim is working memory you can put toward the problem in front of you.

Start small

You don’t need a complete personal knowledge management system. Start with one habit: when you switch away from a work item, spend 20 seconds writing down where you left off. That’s it.

If you’re working in Azure DevOps, TicketHop makes this dead simple — private notes live directly on the work item, your visit history is automatic, and everything is searchable from a keyboard shortcut. But even if you use a text file or a sticky note, the research says the same thing: the act of saving frees your brain to do better work next.

Your memory isn’t failing you. You’re just asking it to do a job that a tool can do better — so it can focus on the job only it can do.

---

References

[1] Storm, B. C. & Stone, S. M. (2015). “Saving-Enhanced Memory: The Benefits of Saving on the Learning and Remembering of New Information.” Psychological Science, 26(2), 182–188. https://pubmed.ncbi.nlm.nih.gov/25491269/

[2] Grinschgl, S., Papenmeier, F. & Meyerhoff, H. S. (2021). “Consequences of Cognitive Offloading: Boosting Performance but Diminishing Memory.” Quarterly Journal of Experimental Psychology, 74(11), 1477–1496. https://pmc.ncbi.nlm.nih.gov/articles/PMC8358584/

[3] Risko, E. F. & Gilbert, S. J. (2016). “Cognitive Offloading.” Trends in Cognitive Sciences, 20(9), 676–688. https://www.cell.com/trends/cognitive-sciences/abstract/S1364-6613(16)30098-5