A notebook that tells me what I've forgotten

I’ve realised I spent years writing notes largely out of habit, rather than because I was any good at using them afterwards.

Paper notebooks were the worst. I’d write something down because writing it felt useful in the moment. Then the notebook would close, and a week later I’d barely remember what was in it.

Digital notes were better, but not by much. OneNote gave me somewhere to put things. It didn’t give me a reason to come back to them.

So I accumulated notes rather than knowledge.

The problem was never capture

It took me a long time to work out what I actually wanted, mostly because “take better notes” is such an available answer that it stops you looking for a different one.

What I wanted wasn’t a record at all. It was a running answer to three questions I have most working days.

Where am I with this? What have I forgotten? And what am I actually supposed to be doing today?

A notebook can only tell you what you wrote down. It cannot tell you what you’ve dropped, because the things you’ve dropped are precisely the things you stopped writing about. That gap is where most of my unfinished work has always quietly gone.

Keeping the North Star in front of you

The second thing is harder and matters more.

Most working days are governed by whatever is immediately in front of you. The long-term direction — the thing you’re actually trying to get to, and in my case the company goals the work is supposed to serve — sits somewhere further back, in a document nobody opens between quarters.

A system that holds both can keep the direction in view while you deal with today. It can point out that a task you’re about to spend the afternoon on has drifted from the thing it was meant to serve, or that something you decided three weeks ago has gone quiet.

That isn’t record keeping. It’s orientation, which is a different job, and the tools I used for twenty years were only ever built for the first one.

This is the Daily OS, run by one person

It took me embarrassingly long to notice that I had already written this down.

The Daily OS is the cadence layer of Editorial Intelligence: capture, connect, create, activate, measure, learn, on a daily, weekly and monthly rhythm, so that evidence accumulates instead of resetting with every campaign. That is exactly what I’ve been doing for the past fortnight, at a scale of one.

The framework says plainly that it is not a personal productivity system, and when I wrote it I meant it. It describes a shared rhythm for organisational learning, and I had no particular reason to think the same loop would hold with nobody else in it.

What I’ve added is the part the framework doesn’t specify. Capture and connect are in there. Orientation isn’t. Keeping the direction visible while you deal with the day — where am I, what have I dropped, does this afternoon still serve the thing it was supposed to — is a different function, and it turns out to be the one I actually needed.

A fortnight establishes one thing only: that a single operator can run the loop. It says nothing about whether that is sustainable under normal working conditions, and nothing about whether it produces better outcomes than a team would. Those are three separate claims, and I have evidence for the first.

Keeping them apart matters, because collapsing them is how a methodology built from one practitioner’s experience becomes an increasingly convincing account of how that practitioner thinks the world works. The missing piece, though, was never capture.

Which is why GitHub has stopped feeling like a repository to me.

It’s becoming my notebook. Except that unlike every notebook I’ve owned, it tells me what I’ve stopped paying attention to.