My day lives in one note. Every morning I create a new daily note in Obsidian. It becomes the source of truth for the next sixteen hours. I do not check my calendars once the day starts. The meetings, the reminders, the blocks of focus time, they all live in that note.
This sounds small, but it changed how I recover from interruptions. And interruptions are the thing that used to break my sprints.
The Daily Note as Navigation Hub
I wrote earlier about the daily note as a navigation hub. The idea is simple. The daily note links out to everything I touch that day: the sprint note, the meeting notes, the book I am reading, the side project I am thinking about, the conversation I need to follow up on. Those links turn the daily note into a door. I can walk through it into any part of my work, and I can walk back.
At the top of the daily note I paste the calendar entries. I do this once in the morning, pulling from my work and personal calendars. It is a quick list: 10 AM daily scrum, 2 PM refinement, 4 PM check-in. After that, the note is open. I add to it as the day happens.
What I Actually Write Down
During the day, the daily note collects three kinds of entries.
What I did. A short bullet for each chunk of work. Not a timesheet. Just enough to reconstruct the thread later. “Stubbed the endpoints for the new contract.” “Paired with a teammate on validation logic.” “Updated the board after the refinement session.”
What I learned. If I hit a problem and figured it out, I write the gist. If somebody explains something well, I capture the explanation in my own words. If I read a useful article, I paste the link and a sentence about why it matters.
What comes next. This is the breadcrumb. Before I stop working on something, I write the very next thing I would do if I kept going. Not a vague “keep working on story two.” A specific next action. “Look into the validation error on line 47.” “Ask the backend lead about the contract shape.” “Create the command handlers for the new endpoints.”
That last one is the difference between a five-minute recovery and a thirty-minute recovery.
The Cost of an Interruption
We have all heard the number. It takes somewhere between fifteen and thirty minutes to fully recover from an interruption. I do not know if that number is exact for every person, but it feels right for me. I lose the thread. I have to rebuild the mental model. I check Teams, I check email, and by the time I remember what I was doing, half an hour is gone.
The breadcrumb shortens that distance. When I come back to the note, I see exactly where I left off. The context is right there. I do not have to reconstruct it from the open tabs and the half-written function.
Interruptions are still annoying. But they are no longer expensive in the same way.
Boundaries and Breadcrumbs Together
I am not naive about interruptions. I know they will happen. Some are welcome. Some are part of the job. I still tell the team that if I am in a Pomodoro, the building needs to be on fire before I want a verbal interruption. But when something genuinely urgent pulls me away, the breadcrumb is what lets me hand the context off cleanly.
This is the same reason I keep AI in my loop, not me in the AI’s loop. Agents and tools can run their own threads, but I still own the context. The daily note is where that context lives. If an AI assistant or a teammate takes over a task, the breadcrumb tells them where to start. If I pick it back up tomorrow, the breadcrumb tells me where to start too.
The Graph View Reconstructs Memory
The links do more than help me navigate. They reconstruct memory. In Obsidian, every note has a local graph. From my sprint note, I can see all the daily notes that link to it. From a daily note, I can see the other notes I touched that day. Sometimes that is the sprint note. Sometimes it is a book I was reading, a meeting note, or a side project.
That view helps me answer questions I did not know I would have. I might look at a note a year from now and wonder why I wrote it. When I pull up the graph, I see the day. I see the sprint. I see the book club meeting and the demo prep session that surrounded it. The memory comes back because the connections are visible.
The same idea shows up in the brain’s inability to multitask. The daily note is how I fake multithreading. I can only hold one real context at a time. The note holds the others for me. When it is time to switch, I read the breadcrumb, I load the context, and I go.
A Real Example
Here is what a typical mid-day entry looks like.
- Working on: contract validation for story two.
- Did: stubbed the endpoints, adjusted the contract shape on the board, got stuck on the validation rule for the edge case.
- Next: check the validation error with the backend lead and create the command handlers for the new endpoints.
That is it. It takes under a minute to write. But it saves me from the blank stare when I come back after lunch and wonder what I was thinking.
The Daily Note Is Not a Diary
The daily note is not a diary. I do not write long reflections about my feelings. It is not a todo list. I have a separate place for committed tasks. It is not a calendar. The calendar just seeds it.
It is a working memory extension. It holds the context I cannot fit in my head. It is messy, chronological, and practical. And because it links to the sprint note, it feeds the larger system instead of living in isolation.
In the next post I will describe how all of this feeds into sprint reviews and retros. That is where the notes stop being personal memory and start becoming team value.
I cannot prevent every interruption. I can make them cheap to recover from, and that has been enough.
Leave a Reply