Stress doesn't erase what you know. It locks the door to it.

You've probably felt this. Production is down, Slack is on fire, three people are watching your screen share, and you can't remember the flag for git reset. You've typed it a hundred times. An hour later, coffee in hand, it comes back instantly.

That isn't you being bad at your job. It's a well-studied feature of the human brain, and it has a slightly annoying lesson for how we learn things in the first place.

A human brain painted as a city at dusk, with thin streets going dark at the front and a bright highway glowing deep inside

The words were still there. They just wouldn't come out.

In 2005, Sabrina Kuhlmann, Marcel Piel and Oliver Wolf at the University of Düsseldorf ran a simple experiment on 19 young men. On day one, each learned a list of 30 words. On day two, some had to go through the Trier Social Stress Test first: a mock job interview and mental arithmetic in front of an unsmiling panel. It's the lab equivalent of a live incident review.

Ten minutes later, right around the time cortisol peaks, they tried to recall the list.

After the control task, they remembered about 64% of the words. After the stress test, about 57%. The words had been learned under calm conditions the day before. Nothing about the learning changed. Only the moment of retrieval did.

Two details are worth noticing. The drop hit emotionally charged words hardest, and cued recall, working memory and attention didn't change in that study. Stress didn't wipe the memory. It made pulling it out on demand harder.

Your prefrontal cortex goes offline first

Why would a brain do that? Yale neuroscientist Amy Arnsten spent years on that question. Her 2009 review in Nature Reviews Neuroscience lays it out: the prefrontal cortex, the part that holds things in mind, plans and reasons, is the brain region most sensitive to stress. Even mild stress you can't control floods it with noradrenaline, dopamine and cortisol, and at high levels those chemicals weaken the connections between prefrontal neurons.

Meanwhile the same chemicals strengthen the amygdala and older, more automatic circuits. In Arnsten's words, stress switches control from the thoughtful prefrontal cortex to more primitive conditioned responses.

From an evolutionary angle, that's sensible. If something is chasing you, you don't want to weigh options. You want to run.

During an outage, it's the worst possible trade. Debugging is almost pure prefrontal work: holding a hypothesis, the logs and the last deploy in your head at once.

Stressed brains fall back on habits

Lars Schwabe and Oliver Wolf, then at Ruhr University Bochum, showed the other half of this in 2009. They had people learn two actions that each earned a different food reward. Some were stressed first (one hand in ice water while being filmed and judged). Then one of the foods was "devalued": participants ate it until they were sick of it.

Unstressed people adjusted. They stopped working for the food they no longer wanted. Stressed people kept doing the old action anyway, as if on autopilot. They also understood the setup worse: 58% of controls could name which action led to which food, against 28% of the stressed group.

Schwabe and Wolf called it the first evidence in humans that stress pushes behaviour from goal-directed to habit.

Anyone who has been on call knows the developer version. You restart the pod because restarting the pod is what you always do. You rerun the failing deploy. Your hands go for the familiar move while the part of you that would ask "wait, what actually changed?" is the part stress just dimmed.

The fix starts before the incident

So far this sounds hopeless. It isn't, and the most interesting study here is about learning, not stress.

In 2016, Amy Smith, Victoria Floerke and Ayanna Thomas at Tufts published a paper in Science with 120 people. Everyone studied 30 words and 30 pictures. Half then learned by restudying, reading the items again. The other half used retrieval practice: closing the material and recalling as much as they could, several times, with no feedback.

The next day, half of each group went through the same kind of stress test, with speeches and math in front of judges.

People who had restudied showed the usual stress dip. On a test about 25 minutes into the stress response, they recalled around 7 items, compared with a little under 9 for the unstressed restudiers. The retrieval-practice group recalled around 11 whether they were stressed or not. Stressed retrieval learners even beat calm restudiers.

Two paths in a storm: a faint footpath being washed away in the grass, and a deeply worn stone path lined with glowing neurons staying clear

The authors' reading: stress hurts weak, shallow memories most. Memories you've already pulled out of your head several times are sturdier.

Now the honest caveat, because this one gets oversold. Replications have been mixed. A registered meta-analysis by Swiss researchers led by Mariela Mihaylova, published in Swiss Psychology Open in 2025, pooled 10 studies with 908 people. Retrieval practice clearly beat restudying under stress (Hedges' g = 0.45). But across those studies, stress didn't reliably hurt either group, so whether retrieval practice specifically "protects" against stress is still open.

What holds up either way: memories you've practised retrieving are stronger, and that advantage survives stressful conditions. When you need it most, it's still there.

Something to try this week

You can't make outages calm. You can change what's in your head before the next one.

  1. Write your runbook from memory first. Pick one incident type you dread (a full disk, a bad migration, an expired cert). Before opening the real runbook, write the steps from memory. Then compare. The gaps are exactly what would vanish at 3 a.m.
  2. Quiz yourself on the commands you keep looking up. The kubectl flags, the git recovery moves, the SQL to find a blocking query. Cover the answer and type it. Getting it wrong first is fine; that attempt is the practice.
  3. Run small fire drills. Teams that do game days are rehearsing retrieval under mild pressure. Even ten minutes of "the database is read-only, go" with a teammate counts.
  4. When it happens, buy back your prefrontal cortex. Arnsten's work points to uncontrollable stress as the trigger. Saying the plan out loud, writing the timeline in the channel, or handing off comms are ways to make the situation feel more controllable. Slow is smooth.

Where I keep mine

Most of what I'd need in an incident I first learned from a conference talk, a post-mortem, or a thread, and then never saw again until the bad day arrived. That's part of why I built Recl. You save the talk or article, it pulls out the key takeaways, and later it asks you about them on a spreading schedule ("Still remember this one?"), so the useful stuff gets retrieved a few times before you need it under pressure.

Recl's recall schedule screen, showing one save coming back on Day 1, then at longer gaps

Next time you blank on an easy command mid-outage, don't read it as "I don't know this." Read it as "I only learned this the comfortable way." Pull it out of your head a few times this week, while nothing is on fire.

Asutosh writes about memory and how brains learn, and builds Recl, an app for remembering what you watch and read.

References