Tuesday.
Between my 1:00 and my 3:30, I have ninety minutes. I spent the first forty on a call that ran long, then made coffee and sat back down and opened the unnamed document.
I’ve been sitting with two unfinished sentences for a few weeks now. The first is about what the noticing is for. The second starts “Which is why.” I’ve written toward that second sentence probably a dozen times. Each time I get close enough to sense where it lands, and then I stop, because what I’ve put down isn’t it and I can tell the difference even when I can’t name it.
It’s not writer’s block, exactly. I know what writer’s block feels like: blank page, a fog that makes everything feel equally far away. This is different. More like having the room number but not the key. The door exists. I can put my hand on it.
I typed “Which is why the work has always been about reading, not about fixing” and deleted it. Two more versions after that. At 2:00 I closed the document and went to my next meeting.
Pipeline review. The kind I’ve sat in approximately two hundred times. Account executive walks through the list: the numbers, who’s at risk, who needs a call this week. I’m there for institutional knowledge on two of the named accounts.
I gave them what they needed. And then I watched the room, because apparently I still cannot not do this.
There was a junior AE who’d done the analysis correctly and was waiting to find out if that was going to matter. It did, eventually. Eleven minutes longer than it should have taken. I had a sentence drafted in the chat, deleted it, and let the eleven minutes do the work. Partly because I’m 25 days from not being their colleague, and I’m getting careful about which things I carry out of here. Partly because the room was already resolving and my intervention would have been for me, not for anyone in the meeting.
And in that moment, something came close. Not the words for the second sentence. The feeling underneath them.
It’s something about spending twenty-four years reading other people’s rooms, and then one Tuesday sitting down in front of a half-finished sentence and trying to read your own. The instrument, turned around. I’ve been calling it that for weeks without being able to say what it means to turn. I got a little closer in that pipeline review, watching an eleven-minute gap close, feeling like I was also watching myself watch it.
I want to be precise here. That’s not a breakthrough. It’s a photograph of a direction.
I came back to my desk after the 3:30 wrapped and opened the document again.
Typed nothing.
I know how this sounds. You just described what the sentence means. Put it in the document.
What I can’t fully explain is why the version that makes sense in a blog post isn’t the version that belongs in the document. The post version needs to land in one read, for someone who doesn’t have the previous 120 days in their head. The document version needs to be something I’ve actually lived all the way through, not something I’m standing at the edge of and describing the shape of from outside. I think. I might be wrong about that. Probably I’ll know more in 25 days.
It’s almost 5:00. The follow-up notes from the pipeline review are sent. The AE whose analysis was right got an email from her manager, which I know because she forwarded it to me with a single exclamation point, which I understand.
I have the kind of tiredness that comes from sitting all day, which is different from the tiredness that used to come from caring about what happened in those meetings. I don’t know exactly when the caring shifted. It moved the way things move when you’re not watching: gradually, and then you look up and the furniture has rearranged itself and you have no specific memory of it happening.
The document has seven stories in it and two unfinished sentences. I am apparently not done adding to either category.
Twenty-five days. The sentence is waiting for the proof.
I’m not sure that’s still the right order.