Why you keep forgetting what matters
Map atrophy explained
The grade appeared in the portal at the end of the semester: C. I stared at it, confused. I had done all the homework. Every single assignment, turned in on time. So what happened?
The tests. I had bombed the tests because I didn’t actually understand the material. And I didn’t understand the material because when I sat down to do the homework, I had focused entirely on getting it done and submitted, not on learning anything from it.
It wasn’t that I had decided learning didn’t matter. When I started each assignment, I knew why I was doing it: to learn the material, to prepare for tests, to actually understand the concepts. But somewhere between question one and question fifteen, those reasons vanished from my thinking. The work became about completion. Finish the problem set. Submit before the deadline. Check the box.
The reasons I cared were still there (I really did want to learn, I really did care about doing well on tests), but they had disappeared from my conscious thinking. And so I acted as if they didn’t exist at all.
This happens constantly, in ways both trivial and catastrophic. You know what matters. You start working on it with the right reasons in mind. And then, mid-work, you forget. Not because you stop caring, but because your mental map of the situation atrophies under cognitive load—dropping elements even though they still matter.
The map is not the territory
Consider what happens when you work on any problem. You can’t hold the entire situation in your head: all the reasons something matters, all the ways it connects to what you care about, all the implications of getting it right or wrong. Instead, you work with a simplified model: a conscious sense of what you’re doing and why.
This is what I mean by working with a map rather than the territory. The territory is the full reality of your situation: your actual drives, your actual reasons, the actual state of things in the world. The map is your conscious model of that situation, the version you can think about and act on.
The problem is that maps atrophy. Under cognitive load, they compress and drop information. And when you make deliberate choices that depend on conscious reasoning (like deciding what strategy to use, or whether to keep going), you can only act based on what’s in your map. If something has fallen out of your conscious model, those deliberate choices will proceed as if it doesn’t exist, even when it’s still there in the territory, still mattering. Parts of you below conscious awareness might still respond to it (you might keep feeling vaguely dissatisfied, for instance), but your conscious strategy won’t.1
When I sat down to do homework, my initial map included multiple problems: learn the material, prepare for tests, build understanding, get a good grade. But as I worked, cognitive resources got tight. Attention narrowed. The map atrophied to just one thing: complete and submit. The other problems didn’t disappear from reality (I still cared about learning, the tests were still coming), but they disappeared from my map. And so my deliberate actions ignored them entirely.
This is different from changing your mind about what matters. I didn’t decide, halfway through problem three, that learning was unimportant. The atrophy happened below the level of conscious decision. My working memory filled with the immediate task. The broader reasons receded. And I kept working, now optimizing for the wrong thing, without noticing the shift.
When the stakes are higher
The homework example is relatively harmless: a bad grade in one class. But the same pattern shows up in situations where the consequences are severe.
During my second year of engineering school, I seriously considered switching to philosophy. I loved philosophy. I was good at it. Engineering felt, at times, genuinely terrible. Problem sets I didn’t care about, material that seemed pointless, grades that weren’t great. Philosophy felt meaningful, exciting, like the thing I was supposed to be doing.
The pull was strong enough that I asked advisors if switching was possible. I made schedules for what a philosophy major would look like. I came very close to doing it.
But there were reasons to stay in engineering that weren’t in my map during those moments of strongest temptation. Career flexibility. Keeping options open. The practical skills I’d gain. Financial stability down the line. These reasons were still there in the territory; they were real considerations that actually mattered to my future. But when I was sitting in a terrible engineering lecture, feeling miserable, they had atrophied out of my conscious thinking.
If I had acted based only on what was in my map in those moments (philosophy feels better right now, engineering feels terrible), I would have switched. And I’m fairly confident that would have been the wrong choice. Not because philosophy doesn’t matter to me (it does, deeply), but because the reasons to stay in engineering were real and important, even when I couldn’t feel them.
What brought those reasons back into my map was deliberate review. Sitting down, away from the immediate misery of a bad problem set, and explicitly asking: what do I actually care about here? What are all the reasons this matters? Making decision matrices. Talking it through with people I trusted. Forcing myself to query the territory rather than just acting on whatever was currently in my atrophied map.
The territory hadn’t changed in the relevant sense. The reasons to stay in engineering were always there. But my map had dropped them, and if I’d relied only on what I could consciously feel in the moment, I would have acted as if they didn’t exist.
Here’s the important part: if I had switched to philosophy based on that atrophied map, I wouldn’t have simply lived happily ever after in my new major. At some point, I would have realized something was off. The map would have turned out to be wrong about the territory in important ways. The career flexibility I’d given up would have started to matter. The financial stability would have become relevant. The mismatch between what my map said (this is right) and what the territory was signaling (something’s missing) would have become impossible to ignore. The atrophy would have revealed itself, eventually, through dissatisfaction I couldn’t quite explain.
Realizing that, I didn’t switch. The decision to stay in engineering is a complex one, so even now, sometimes when things get tough, my map atrophies and I don’t remember why I chose this path. I feel lost, like I might have made the wrong choice. But because I externalized it all by writing down the reasons, the tradeoffs, what actually matters, I can go over everything again and find peace. The reasons are still there. I just need to look at them.
The counterintuitive bit
Here’s what makes this confusing: it feels like “do I actually care about this?” should have a simple answer. Either you care or you don’t. Either learning matters to you or it doesn’t. Either philosophy is your calling or it isn’t.
But when you understand that you’re always working with a map that can atrophy, the question becomes more subtle. You can care about something deeply (it can be there in the territory, actively driving you, genuinely mattering) while simultaneously not being in your conscious map at the moment.
This creates a strange kind of internal conflict. You feel pulled toward one thing (finish the homework, switch to philosophy) while some other part of you knows that’s not quite right. The feeling is real; it’s in your map. But the knowing is also real; it’s in the territory, even if you can’t currently access it consciously.
Framed in terms of problems: yes, you care about learning (it’s there in the territory as an active problem, a drive toward understanding). But your map has temporarily dropped it. The caring persists whether or not you’re consciously tracking it. And because you make decisions and evaluate success based on what you care about, knowing what you care about (keeping your map reasonably aligned with territory) actually matters.
This is why you can finish a homework set and feel simultaneously satisfied (I completed the task) and dissatisfied (I didn’t actually learn anything). The satisfaction comes from resolving what was in your map. The dissatisfaction comes from the territory signaling that other problems are still unresolved.
What to do about it
The first thing to understand is that some map atrophy is inevitable. You cannot hold everything in conscious attention simultaneously. Action requires simplified models. Mid-work compression is not a personal failing. It’s a necessary feature of how cognition works under resource constraints.
But accepting that atrophy happens doesn’t mean accepting it passively. It means acting proportionally to the importance of what’s been dropped. If the problems your map has lost are trivial—like losing muscle strength in your pinky—let them stay dropped. But if they’re important—like losing strength in your legs, which you depend on constantly—you need to do what you can to restore them, even if you can’t prevent all atrophy.
The most reliable way to do this is externalization. Get your problems out of your head and into a system you can actually see. This externalized system is also a map, but it’s one that isn’t subject to the same cognitive pressures you are. It doesn’t have working memory limits. When the reasons something matters are written down explicitly, they remain visible even when your mental map atrophies. You can look at them, remember them, check whether your current actions actually serve them.
This is what going up and going down in the productivity system actually does. “Why does this matter?” is a query to the territory. It forces you to surface reasons that might have atrophied out of your map. “How might this be resolved?” generates paths while keeping the full problem visible. Regular review is the exercise that keeps your map healthy—deliberately checking whether what you’re working on still serves what you actually care about.
How to build a productivity system around problems
In my last essay, I argued that productivity isn’t about completing tasks efficiently—it’s about resolving the problems you actually care about. The response was immediate: “Okay, but how? How do I actually organize my work this way?”
The practice matters more than perfection. You won’t catch every instance of atrophy. Your map will still compress mid-work. But if you’re reviewing regularly (daily, or at least weekly), you can catch the important ones before you’ve spent months optimizing for the wrong thing.
Tools can help here, though current options make this harder than it needs to be. A good system would make it easy to externalize problems, see their connections, and check whether your actions are serving them. It would help you query the territory efficiently rather than relying on what happens to be in your conscious map at the moment. Better tools for this are possible, and worth building, but even with what’s available now, the practice of deliberate review makes a difference.
One more thing worth noting: problems in the territory aren’t static. They come and go. New drives emerge, old ones fade. Sometimes you can change the territory to actually close a problem entirely—resolve it so completely it’s no longer there. But when you find yourself in conflict, pulled in multiple directions, that conflict comes from problems that are active in the territory. When I turn ninety-seven it might suddenly become my dream to die in Egypt, a problem that wasn’t there when I was born, now intensely active. The territory changes over time. At any given moment, the question is just whether your map is tracking what’s actually there.
Why this matters
You already know, in some sense, that you forget what matters. You’ve had the experience of finishing something and realizing you optimized for the wrong thing. You’ve felt the dissatisfaction that comes from resolving what was in your map while leaving what actually mattered unresolved.
What changes when you see this as map atrophy rather than simple forgetting is that you stop treating it as a personal failure. You stop thinking “I just need to focus harder” or “I should have remembered.” Instead, you build systems that compensate for the inevitable compression. You externalize. You review. You query the territory deliberately rather than trusting that important things will stay in your map on their own.
The homework is done, the grade is recorded, and you can’t go back. But you can notice when your map has dropped something important. You can build practices that catch the atrophy before it costs you a semester, or a major, or years spent working on the wrong problems.
Your reasons are still there, even when you can’t feel them. The question is whether you’re checking.
Written with the help of AI.
Technically, whenever the map “drops something,” that is the territory changing, since the map is part of the territory. But it’s not changing in the relevant sense for our purposes here. We care about whether the map accurately represents the rest of the territory (your drives, the world state, the reasons things matter), not whether the map itself is changing. If you were mapping the map itself, things would get quite complex.