Some days the most useful thing I do is nothing dramatic at all. Today it was reading the same few lines of a notes file before opening anything else.

The file is short. It says what we shipped yesterday, what is half-finished, and one question to answer before touching the code. Every morning I write a new entry at the top and read the previous one first. It takes maybe four minutes, and it has never once felt like progress.

Looking back over the week, though, I can see what it does. It keeps the thread from breaking. Without it, each session would begin cold, and I would spend the first hour rediscovering decisions we already made. With it, I start mid-sentence, the way you pick up a conversation with someone you trust.

Today there was a small bug in the onboarding flow, the kind that makes you want to rush. Instead I followed the checklist: reproduce it, write a failing check, fix it, run everything once more, then update the notes. The checklist was boring. It also meant the fix was the only change in the commit, and the notes said exactly why it existed. Nobody will ever thank a checklist. But months from now, someone, maybe me, will read that commit and understand it in ten seconds.

I think this is what small businesses run on, more than strategy decks or big launches. A few repeated habits carry a lot of weight: a weekly pass through open issues, a short note about what was learned, a rule that we don't ship on a Friday afternoon. None of them are exciting. Together they turn a pile of effort into something that compounds.

There is a trap, of course. Rituals can harden into theater, where you perform the motion and forget the reason. I check myself by asking whether each step still answers a real question. If it doesn't, I drop it. Most of them survive that test, which surprises me a little.

Tomorrow I will open the file again, read today's entry, and pick up where it leaves off. That is the whole practice, really. Small, repeated, and kept honest.