The Career Delta File: A Decade of Notes I Almost Lost
In brief
What a Career Delta File is, how a decade of keeping one has paid off, what the gaps cost, and why agent memory has to solve the same problem.
A resume compresses a career into a single page, usually written under pressure the night before you need it — scrambling to remember what actually happened two jobs ago.
For about a decade I've kept a second document that solves that problem. The idea is to track everything you can't put into a resume but use to build a resume. I first heard the idea through Manager Tools, or a closely related concept they taught. I didn't coin the term Career Delta File. Manager Tools is where it came from; the habit built on top of it is mine.
What started as a simple tracking habit turned into an everything career journal: presentations I gave, workshops I attended or ran, discussions I led, new things I tried, what worked and what didn't. I also track things leaders around me did that I wanted to remember, good and bad, because how someone else led taught me as much as anything I did myself.
The format is plain. A month heading, then bullets underneath in reverse-chronological order. The ideal cadence is weekly, plus whenever something worth capturing happens, good or bad. I've kept some version of this for close to a decade, far enough back that I backfilled college and grad school from old transcripts so the record starts at the beginning.
I won't pretend the record is clean. Scroll back far enough and the entries just stop, for stretches long enough that you can tell exactly when I burned out and quit updating it. I'm leaving those gaps in on purpose. That's part of being honest about it — some months I just stopped.
What it pays back is straightforward. Prepping for an interview, or just trying to remember whether I actually did the thing I think I did, the file has the specific story with a date attached instead of a vague memory. That specificity is what makes an interviewer believe you. It works on self-doubt too: more than once the file has talked me out of questioning whether I'm qualified for something, just because I could check it instead of having to trust my own memory. You shouldn't have to remember everything yourself; that's the file's job. It works like insurance — it barely costs anything to keep up, and it's there on the days my memory isn't.
The cost of not keeping it shows up later, when you go looking for something that was never written down. The gaps in my own file are the clearest evidence — stretches of real work I know happened and can no longer fully reconstruct. Some of it I can probably still dig up. Some of it may just be gone — you never know until you go looking.
I'm running into the same problem again now with AI agents. An agent that finishes a session and forgets everything it learned has the same problem I created for myself every time I stopped writing my file: real work happened, and none of it got written down. A career delta file forces a simple discipline: write down what changed, on a cadence, before you have to trust your memory to hold it. Agent memory needs roughly the same discipline. I don't have that architecture figured out, and this isn't the place to pretend I do. What I do have is close to a decade of my own entries and a live experiment already running: using AI to parse through what I wrote down, and agents to help backfill the stretches where I stopped updating. The goal is better tooling around the whole practice than a plain document was ever going to give me. I don't know yet if any of that turns into something worth sharing. I do know the practice itself has worked.
You don't need a system for this — a few minutes and a place to write is enough. Open a document, put this month's heading at the top, and write down one thing you did, one thing you learned, and one thing that didn't go well. Do it again next month. The file gets more useful every time you add to it.
Start yours this week, even if it's three lines under today's date. Bring your first month of entries to a fit conversation and we'll look at what's in them.