Journal Practice

The slow bleed of executive function has a paper trail

Journaling isn't about performing insight. The real data is in the words you cannot find and the sentences you have to write twice.

Abstract cream-and-slate line illustration on Kokorology paper, drawn for The slow bleed of executive function has a paper trail

The common advice is to pour your feelings onto the page. This turns your journal into a performance of introspection, a stage for emotional drama where you are both actor and critic. The real data is buried in the mechanics of your writing: the forgotten words, the repeated sentences, the sheer effort to form a coherent thought. I treat my journal less like a confidant and more like a seismograph, recording the tremors of a system under load before they become an earthquake. Your journal can be a logbook for cognitive strain, but only if you stop looking for a story and start looking for the signal.

You’re on a video call, trying to describe a key project, and the word for 'the next version' evaporates. You stammer, call it 'the next… thing,' and feel a hot flush of embarrassment. Later, you find yourself re-reading the same short email four times before you can process it. You might blame it on a bad night's sleep or too much coffee, but these moments are the slow, quiet fraying at the edges of your thoughts, a low-grade static that makes everything feel like more effort than it should be. This is a readout of cognitive function under load.

Your journal is a longitudinal study of one

A regular journaling practice, viewed correctly, is the cheapest longitudinal study of cognitive function you can run on yourself. The value is not in the emotional content, but in the structure of the output. Your ability to retrieve words, formulate complex sentences, and maintain a coherent train of thought are all executive functions. They are conducted by your prefrontal cortex (PFC), the part of your brain responsible for planning, decision-making, and moderating social behaviour.

When you write by hand, you are creating a physical artefact of these functions in action. It’s a complex task that demands coordination between motor control, language centres, and working memory. Over time, this creates a personal baseline. You are not comparing your writing to an external standard, but to your own output from last week, last month, last year. A sudden shift—simpler sentence structures, increased repetition, more difficulty finding specific nouns, a noticeable decline in the neatness of your script—is a data point. It is a quiet flag from your nervous system that the resources available for complex cognitive tasks are becoming scarce.

Related anchors: sleep anchor · burnt-out anchor · wired-tired anchor

Cognitive slips are a capacity signal

Those moments of brain fog or forgotten words are signals that your system's total load is exceeding its current capacity. Your body runs a constant, ruthless budget of its energetic resources, a process known as allostasis. When demands—from work deadlines, family stress, poor sleep, or even a week of late-night socialising—are chronically high, the body starts making cuts. The PFC is a metabolically expensive piece of equipment. It's one of the first departments to face budget cuts when the system is under strain, like a city in a blackout powering down the libraries and museums to keep the hospitals running.

This is where the journal becomes a powerful tool for reading your own state. It captures the paper trail of this allostatic load. The entry you struggle to write after a 12-hour travel day is a direct readout of a system that has diverted power from the PFC to manage the more immediate tasks of travel stress and circadian disruption. The prompt is not to 'try harder' to write well, but to simply log the state. The glitch itself is the information you came for.

Log the glitch. Note the time, the word you were reaching for, and what was happening in the hour before. No story, just the data.

What to log when you can't find the words

The point of this practice is not to produce beautiful prose. The point is to capture the state of the machine. When the machine is sputtering, that's the most important time to take a reading. But what do you write when writing itself is the problem? You stop trying to write sentences and start logging fragments. This is where I find the most useful data lives.

  • The Glitch Itself: Note the specific failure. 'Couldn't find the word for invoice.' 'Called the client by the wrong name.' 'Forgot the point of the sentence halfway through.' Be a court reporter for your own cognitive stumbles.
  • Physical Sensations: Where is the strain showing up in your body? 'Tightness behind the eyes.' 'Shoulders feel like they're climbing my neck.' 'A hollow, cold feeling in my stomach.' 'Right hand is buzzing.' Your body is already logging the data; your job is to transcribe it.
  • Sentence Fragments: Don't force coherence. If your thoughts are fragmented, let your writing be fragmented. 'Too many emails. Can't focus. Need coffee. No, need quiet. The screen is too bright.' This is a more honest record of a taxed PFC than a perfectly constructed paragraph about how stressed you are.
  • Repetition: Notice if you write the same word or phrase multiple times. This is often a sign of a working memory buffer that is full or failing to clear. Just circle it. The pattern is the point.
  • The Doodle Test: If words fail entirely, just hold the pen. What does your hand do? Does it draw a sharp, jagged line? A tight spiral? Does it just press down hard, leaving a dent? This is still data. It's a pre-verbal, pre-cognitive readout of the system's state of tension or collapse.

Logging data vs. telling stories

Logging data operates on a different layer than telling a story. For years, I encouraged clients to do 'brain dumps,' believing that catharsis was the goal. I was wrong. Unstructured venting often rehearses a grievance, strengthening the neural pathways of the story you're trying to escape. The real work is to step out of the story and simply label the sensation.

Data logging, also known as affect labelling, asks for raw sensory information and bypasses narrative. Instead of writing "I'm so stressed because my boss is impossible," you log "jaw tight, shallow breath, can't find the word for the quarterly report." This simple act of naming a sensation or a cognitive event shifts brain activity. It engages the PFC in a concrete, observational task, which can help to quiet the alarm bells ringing in your amygdala (the brain's threat detection centre). The goal is to correctly identify the problem on a physiological level. This stops the spiral and gives you a clean, usable data point.

Tonight's practice

Tonight's practice is for collecting one clean data point. The goal is to create a low-stakes record of your cognitive and sensory state, right now. Forget narrative and focus on logging.

Where do you feel today's signal in your body — and what was the last thing that moved it?

  1. Set a timer for five minutes. This is a hard stop.
  2. Write the prompt at the top of a blank page.
  3. Answer with sensory data, not a story. Think in terms of physical sensations: 'jaw tight', 'buzz behind eyes', 'shoulders tense', 'stomach feels hollow'.
  4. Note the last input that changed your state. Be specific: 'the 3pm email from my boss', 'the argument about the school run', 'the second cup of strong coffee'.
  5. When the timer goes off, close the book. The practice is the logging, not the analysis. You are simply collecting information for your future self.

Common Questions

What if my handwriting is just messy? Does that count as a cognitive change?

You are looking for a change from your personal baseline, not an objective standard of neatness. If your normally legible script becomes a scrawl during a stressful week, that's a data point. Consistent messiness is just your handwriting. The signal is in the deviation from your norm.

Is this the same as screening for dementia or Alzheimer's?

No. This practice is for tracking the cognitive impact of nervous system load, burnout, and chronic stress. It makes you literate in your own patterns of response to daily demands. Any sudden, severe, or worrying changes to your cognitive function should always be discussed with a medical professional.

Do I have to write about my feelings for this to work?

No. In fact, it can be more effective if you don't. The goal is to log cognitive and sensory data, not to get lost in emotional stories that can amplify the state you're in. Think of it as a technician's logbook for your own system, not a diary for your emotions.

Does this have to be on paper, or can I type it?

Writing by hand provides a richer dataset. The physical act involves fine motor control, which is also governed by the nervous system. The artefact of your handwriting—its size, pressure, and legibility—adds another layer of data that typing obscures. Typing is faster and less cognitively demanding, which means it doesn't test the system in the same way. If typing is all you can manage, it is better than nothing, but you lose a valuable signal.

Closing

The goal is not to pathologise every forgotten word, but to build a more honest, data-informed relationship with your body's signals.

TL;DR

Stop using your journal to narrate your feelings. Use it as a cheap, effective logbook for cognitive strain. The structure of your writing—word retrieval, sentence complexity, even handwriting legibility—is a direct readout of your prefrontal cortex function. Tracking changes from your personal baseline reveals when your nervous system's total load is exceeding its capacity. These cognitive slips are data points showing the physiological cost of your day, captured in your own hand.

Sources

  • Pennebaker, J. W. (2023). Journaling and the nervous system: from expressive writing to affect labeling. Curated meta-analyses and primary studies (1986–2023).
  • Lieberman, M. D. (2023). Communication with others and oneself: language as a nervous-system intervention. Curated primary studies and meta-analyses (1994–2023).
  • Freudenberger, H. J. (1974). Staff Burn-Out. Journal of Social Issues, 30(1), 159-165.