The Systems I Build Are the Ones I Needed

The Setup

A few months ago, my manager and I argued about a chart.

He needed it for a leadership presentation. I had the data. I should have sent something inside an hour. Instead, I spent the afternoon building a version that updated itself, so no one would rebuild it next time. He said, fairly, that I was being slow.

A few months later, the company ran a planning session. Every team had to present goals for the year. The format everyone was asked to use was the same chart. We already had ours.

I came down with a fever the morning of the session and had to go home before our slot. He presented without me, and sent me a message after: this is how we should operate.

I have been thinking about that argument ever since.

The Thinking

I have always built things.

I used to think it was a personality trait. I liked tools. I liked systems. I liked the satisfaction of a thing that worked on its own. The story I told myself was that I was a builder by temperament.

Last year I was diagnosed with ADHD. The diagnosis itself was not a surprise. The re-reading was.

Once I had the frame, the building stopped looking like preference and started looking like compensation. The phone-only rule when I leave the house, because I have left things behind too many times to trust the longer list. The checklists for travel. The chart that updates itself. The notes system that recreates today's page whether I remember it or not. None of this is hobby. It is scaffolding for a brain that does not hold things reliably.

The thing I had been calling preference was a workaround I had built so early I forgot it was one.

The diagnosis is small. A name, a frame. The re-reading is where the work is. You go back through the catalogue and find the same evidence sitting in different folders.

The Work

The reflex I am still building is harder to name than the systems are.

For years I thought the problem was forgetting. The phone rule, the checklists, the chart — all aimed at memory. They work, mostly. But memory was never the right word.

What I lose is not the fact. It is the context around it. Why I wrote the note. What state I was in. Which thread it belongs to. A reminder without context is a fragment with my handwriting on it.

The reflex I am working on now is not write it down. It is write down enough that a later version of me can re-enter the moment. When I keep a daily note, I do not just write what happened. I write where it goes — which project, which person, which open thread. The placing is the work. Capture without placing is almost useless a week later.

The placing is not always foreground. Sometimes I do it while building, because the context is hot. Sometimes I do it when my brain is tired of building and needs a low-stimulation task. Sorting notes turns out to be a kind of rest. The admin is not the cost of the building. It is the recovery from it.

I do not have this right yet. Some days the placing fails — wrong folder, wrong context. The reflex is not finished. But the move is clearer now: I am not building external memory. I am building external context, and learning what to put in it.

The Edge

The systems part of the pattern is the easy part.

I can build a chart that updates itself. I can write a note that places itself. I can hand my future-self enough context to re-enter a moment I have already left. The work side of the catalogue has tools.

The other side does not.

The same brain that automates a backlog also loses the thread halfway through a conversation. Replays one sentence for an hour after the meeting ends. Arrives at a one-on-one non-linear when the other person expected linear. There is no auto-updating chart for that. There is no version of me to outsource it to. I am the surface the context has to live on, and the surface is the thing that does not hold.

That is the part the systems do not reach.