
There's a particular kind of entry people won't write.
Not the boring ones — those get skipped through laziness and it doesn't matter much. The ones that don't get written are the ones that would say something you'd rather not have recorded. Third week in a row I've done nothing on this. Spent the evening avoiding it again. Told them it was nearly finished, which isn't true.
Those are the entries that would be worth most, and the reason they're worth most is exactly the reason they don't get written.
What a partial record does
A log with the good weeks in it and the bad weeks missing isn't a neutral, incomplete record. It's an actively misleading one, and it misleads in a consistent direction.
Read back in October, four entries in September and twelve blank days looks like a month you barely worked. If eight of those blanks were evenings you sat down and got nowhere, or evenings you avoided entirely for reasons you could have named, the record has misrepresented your own life to you.
And you'll draw conclusions from it. That you're inconsistent, that this goal isn't viable, that you're not the sort of person who finishes things. Those are significant judgements to make on the basis of a record you accidentally rigged.
The version with the uncomfortable entries in it says something quite different: that you engaged with this thing twelve times in September and eight of those went badly. That's a hard month rather than an absent one, and the response to it is different.
Why the shame gets in
Three things, and they're worth naming because they operate whether or not you notice them.
The log feels like it's being read by someone. Not consciously — but people write differently when there's an imagined audience, and the imagined reader of a work journal is usually a slightly disappointed version of themselves. So the entries get curated, tidied, or omitted.
Writing something down makes it more true. An unrecorded fortnight of avoidance can stay slightly blurry. Written as avoided this again, three weeks now, it's fixed and countable, and there's a real reluctance to convert a vague discomfort into a definite fact.
And there's a fear that the record will be used against you later — by you. If you write told the client it was nearly done, you'll have to see that again.
That fear is well-founded and slightly misdirected. You will see it again — that's the mechanism, and it's the entire value. What people expect is that seeing it will feel like an accusation. What usually happens is that it prompts a small correction while the correction is still cheap, which is considerably better than the alternative of finding out in six weeks.
What to write instead of nothing
The rule that makes this survivable: describe, don't grade.
Didn't open it. Third week. is a description. Wasted another week, hopeless at this is a grade, and a log that grades you becomes a log you avoid on exactly the days it matters. The first is a fact you can act on. The second is a small self-punishment, and self-punishment doesn't produce information.
Same with the awkward ones. Told Priya it's nearly finished. It isn't — the case studies aren't started. That's a factual note and it's precisely the kind that changes something, because you'll see it next week and the discrepancy will be sitting there in writing.
Keep it short. The shorter the entry, the less it feels like a confession, and the more likely it is to get written. Six words is plenty.
And write it at the time. An uncomfortable entry composed the same evening is a description of what happened; the same entry attempted a fortnight later becomes a summary of a fortnight, which is a much harder thing to sit down and write and generally doesn't get written at all.
The strongest objection
There's a real argument against all this, and it deserves stating properly.
For some people, a written record of their own failures is genuinely harmful. If you have a tendency towards rumination, or you're in a period where you're already being unkind to yourself, then a file full of entries documenting what you didn't do is not a neutral diagnostic tool — it's ammunition, and it'll be used. The idea that the record is objective doesn't help much when the reading of it isn't.
If that's you, the honest adaptation is to write only what happened and never why, and to read it rarely and deliberately rather than whenever you open the app. Or not to keep one at all for a while, which is a legitimate choice rather than a failure of practice.
There's also a limit around other people. A log with candid notes about colleagues, clients or a partner is a document that could do damage if seen, and nobody will read it is an assumption rather than a guarantee. Write about your own conduct freely and about other people's carefully.
Eleven entries and a conversation
Six weeks into a difficult contract, she's certain February was a write-off and is about to tell the client the timeline is slipping.
The log has eleven entries, and four of them are ones she nearly didn't write. Nothing, dreading opening the model. Nothing. Two hours reading around the sector, didn't touch the model. Told them it was on track. It isn't.
Read together with the other seven, February is a month in which a data source was eliminated, two analytical approaches failed, a dependency appeared, and there was about a week of avoidance concentrated in the middle. That's a legible account of a hard month.
The entry that changes what she does is the last one. Seeing told them it was on track in her own handwriting produces enough discomfort to prompt an actual email, sent that evening, correcting it. The client's response is mild — they'd assumed as much — and the whole thing is resolved in a day.
Left unwritten, the discrepancy would have stayed vague for another three weeks, and by then the correction would have been a much larger conversation.
Why nobody else has it
The record is on your machine. Nothing is sent anywhere for the app to work, and the notes aren't held on anyone else's hardware.
That's a technical arrangement, and it exists partly for this. A log is only worth keeping if it's honest, and it will only be honest if you're confident about who can see it. An app that syncs your candid notes about your own avoidance to a server is asking for a level of trust that would be reasonable to withhold — and most people, sensibly, would just write blander entries instead.
The blander entries are the failure. Everything useful in this practice comes from the ones you didn't want to write.
Related: The session that produced nothing still counts · Notes as evidence · Local-first software, explained
Share: