A timestamped line between tasks costs ten seconds and buys back the context you lose at every switch. How interstitial journaling works, without ceremony.
· Productivity · 6 min read
The expensive part of switching tasks is not the switch. It is the re-entry: the four minutes at the end of the meeting spent remembering what you were doing before it, which file you had open, and what the next move was supposed to be. Multiply that by the number of interruptions in an ordinary day and you lose an hour to nothing but reloading state.
Interstitial journaling is a fix small enough to actually do. In the gap between two pieces of work, you write one timestamped line about what just ended and what starts next. Not a diary entry, not a status report — a line. The term comes from Tony Stubblebine, who described it as a way to use writing as the transition itself rather than as a thing you do about your day afterwards.
A real stretch of a real day, in a single note:
09:14 starting on the billing export bug — reproduced it, it's the timezone offset
10:02 standup done. next: write the failing test before touching the parser
10:47 stuck. the test passes locally and fails in CI, suspect the test container's TZ
11:30 lunch. when I'm back: check CI env vars, not the parser
Four lines, maybe forty seconds of typing across two hours. Read the 11:30 line: it is a note from a colleague who knows exactly what you were doing, handed to you at the moment you would otherwise be sitting down cold. That is most of the value, and it arrives on the first day.
You could write the same lines without times. It would be worth less, for three reasons.
It marks a boundary. The act of typing a time is a small physical ritual that says that thing is over, this thing is starting. Without it the entries blur into a list; with it the day has joints. People report — and this is the part that sounds like magic but isn't — that the ritual alone kills a certain amount of drift, because dropping into Slack for twenty minutes is harder when the last line in your note says 10:02 next: write the failing test.
It makes duration visible. You will discover that the thing you budgeted an hour for took three, and that the thing you dreaded took eleven minutes. Estimation improves only when reality is written down at the granularity where it happened. A daily note tells you what you did on Tuesday; timestamped lines tell you where Tuesday actually went.
It gives you a stop-and-think point. The moment you have decided to write about what happens next, you have to decide what happens next. A surprising number of the entries end up reading "next: X" where X is not what you were about to drift into.
It sits between two habits you may already have, and does not replace either.
It is not quick capture. Capture is for thoughts that arrive unbidden and need somewhere to land before they evaporate — an idea, a name, a link. Interstitial entries are about work state, and they are written deliberately at a boundary, not reactively at the moment of a thought.
It is not time tracking. Time tracking asks you to categorize hours into buckets so they can be summed. Interstitial journaling asks for a sentence, produces prose rather than numbers, and is useless for billing. That is a feature: the compliance burden is what kills tracking habits by week three.
It is also not a separate system from daily notes — it is what fills them. One note per day, timestamped lines down the page, everything else about the day nested underneath. If you already keep daily notes and they feel thin, this is the missing texture.
One note per day, appended top to bottom. Chronological order is the whole structure. Do not sort, group, or clean up. Resist the urge to build a table.
Write at boundaries, not on a timer. The trigger is "I am about to start something different" — end of a meeting, before lunch, after closing a ticket, when you catch yourself having drifted. Roughly five to fifteen entries a day is a healthy rhythm. A pomodoro-style alarm can seed the habit, but the boundary-trigger is the one that survives.
Two clauses, maximum. What just happened, what's next. If an entry wants to become three sentences, it is probably a thought that deserves its own note — write the note, and leave a link on the timestamped line.
Include the feeling when it's loaded. "stuck and irritated, going for a walk" is more useful in retrospect than "debugging." Emotional state is the highest-signal, lowest-cost thing you can log, and it is the part people skip.
Do not read it back every day. The entries pay for themselves the moment you write them. Re-reading is for the weekly review, and even then you are skimming for patterns — which days had no joints, what kept interrupting, which estimate was off by a factor of three — not re-living Tuesday.
Every version of this habit dies the same way: typing the time is annoying. It is nine keystrokes with a colon in the middle, and it happens fifteen times a day at exactly the moments you are least patient. People switch to writing "later" as the timestamp, then stop writing timestamps, then stop writing.
So the only mechanical requirement worth caring about in a tool is that inserting the current time costs approximately nothing. In Indenta, typing !! opens the picker and Insert current time is one of the choices, so a 09:14 lands at the caret without touching the number keys — enough that the habit stops being a decision.
An outline then gives the day its shape. The entry stays one line, as it should. But the work itself produces material — the meeting's notes, the debugging trail — and that goes on indented lines below the entry, which turns the timestamp into a heading for it. Fold those children and the day reads back as nothing but its timestamps. The User Guide covers the syntax. Any editor with a text-expander snippet or an OS-level timestamp shortcut will do the same job — the requirement is the cost, not the app.
Three things, in ascending order of value.
The smallest is the record: an honest log of where the weeks went, more accurate than memory and more specific than a calendar, which shows meetings but not what happened around them.
The middle one is calibration. After a few weeks of watching estimates meet reality in your own handwriting, you get quietly better at knowing what a day holds. No technique produces this; only evidence does.
The largest is the one you feel on day one and stop noticing by day thirty: you stop losing the thread. The gap between two tasks stops being a hole you fall into and becomes a line you wrote. The next task starts with a sentence telling you what it is.
Start at the next boundary — the end of whatever you are doing after reading this. Write the time, write what just ended, write what's next. That's it; the habit is already running.
Try it in practice: Indenta is a free, offline-first outliner — nested notes, backlinks, tags, and peer-to-peer sync, with no account required. Start writing in your browser, or read the User Guide first.