Where I Was Wrong (And What the Pattern Showed Me)
- Amy Westlake
- Jun 9
- 4 min read
Situation
I thought I knew my own resume.
I've been doing this work for a long time. I pay attention. I keep a daily journal - five minutes, a few questions I've written about before. I had months of entries. I figured querying them would jog my memory on a few specifics.
That's not what happened.
I sat down to update my resume. The kind of thing that should take an hour and takes three. I queried several months of journal entries - not for feelings, not for a pick-me-up, but for evidence. I asked it to surface accomplishments. Patterns. Signals of impact. Things I could actually use.
The AI Move
I'd been keeping my journal in NotebookLM which meant all those entries were already loaded and queryable as a single source. I didn't have to reconstruct anything. It was just there: months of daily observations, sitting in one place, waiting to be asked the right question.
I framed it deliberately. I wasn't asking for a summary. I wasn't asking how I was feeling. I asked it to approach the entries like a research task: find the accomplishments. Surface the patterns of impact. Show me where I'd changed how work got done, not just for me, but for the people around me. Give me evidence I could put on paper.
I also asked it to think beyond what I'd explicitly labeled as wins. Because I knew, even as I typed it, that I wouldn't have labeled most of them. That was the whole problem I was trying to solve.
What came back wasn't a list of things I'd forgotten.
It was a list of things I was currently doing.
The Shift
That's the part that stopped me.
I'd expected the gap to be memory - things I'd done and lost track of over time. What the journal surfaced was different. I wasn't forgetting. I was doing things that hadn't registered as worth claiming.
Not because they weren't significant. Because they were just... the work. The recurring, unglamorous, this-is-just-how-I-operate work that I'd never thought to name.
There were patterns in there I couldn't have articulated without the data. Ways I'd been influencing decisions across teams. A process I'd quietly changed that other people now used. Impact I'd been creating in increments, inside the normal rhythm of the week, that I'd never associated with impact at all.
My resume had gaps. Not because I'd forgotten things. Because I had never claimed them in the first place.
I stared at that for a while.
The Pattern
Our brains don't naturally translate daily work into evidence.
We do things. We move on. We clear the blocker, log the note, end the meeting, close the tab. Unless something gets celebrated or written down deliberately, it lives in the undifferentiated pile of just doing your job. The brain treats that pile as overhead, not achievement.
There's a specific version of this that I think gets missed: incremental change.
We make small changes every day. A process gets a little cleaner. A decision gets made differently because you raised something in a meeting two months ago. A tool gets adopted because you quietly modeled it. None of these get announced. There's no big bang rollout, no launch email, no moment anyone stops to say: that was a change. They just happen. They slip into how the team works, and within a few weeks, that's just how the team works.
But add up a year of incremental changes and you might have transformed something significant. The problem is, without a record, you can't see it. And if you can't see it, you can't claim it.
The journal intercepts that. Not because it helps you remember, though it does. But because it asks you the same questions, in the same format, across a long enough stretch of time that patterns become visible. When you query those patterns with a specific lens (accomplishments, impact, influence), you stop seeing noise. You see signal.
What emerged wasn't what I'd done in the past. It was what I'd been doing. Continuously. Quietly. Without stopping to name it.
I'd been wrong about my own work. In the best possible way.
The Implication
If you keep any kind of log, even an informal one, even inconsistently, try this.
Ask it: what have I accomplished over the past few months? What patterns of impact show up? What am I doing that's changing how work gets done around me?
Read the answer slowly. Not looking for things you forgot, but for things you're actively doing that you haven't thought to claim.
There's a version of your own contributions you haven't written down anywhere. Not because you haven't done them. Because no one, including you, stopped long enough to name them.
What I'm Testing Next
I've started using the same approach for quarterly check-ins and performance conversations. Not to reconstruct what happened, but to give the data a job: surface the signal in the noise I've been generating all quarter.
The journal doesn't just record what you did. It shows you who you've been at work, consistently, over time. That turns out to be a different document than a resume. And in some ways, a more accurate one.
Comments