What a work journal is for
A work journal is a running record of what you worked on, what came of it, and anything you’ll want to remember later. It’s a different thing from a timesheet, since nobody will ask how many hours the bug took, and it’s different from a personal diary too. Feelings are fine to write down, they just won’t help much in your review.
You’re writing it for one reader: you, a few weeks or months from now. That future you shows up at three moments:
- on Friday, trying to write the weekly update
- in review season, trying to remember what happened in March
- while job hunting, trying to turn two years of work into five résumé bullets
All three go badly when you’re working from memory, and all three get easy when there’s a list to pick from.
Why most work journals die in week two
The usual pattern goes like this. You find a template with ten fields, fill it in carefully for four days, skip a busy Thursday, and never open it again.
What keeps a journal alive is mostly unglamorous. Keep each entry short enough that skipping it feels silly. Write at the same moment every day, ideally right before you close the laptop. And use it at least once a week, because a journal you never read back starts to feel like homework, while one that saved you twenty minutes on Friday feels worth keeping.
What’s worth writing down
You don’t need everything. You need the things you’ll be glad to find later:
- What you finished or moved forward, with a number if there is one
- Problems you solved, especially the invisible ones with no ticket, like a flaky deploy you fixed or a teammate you unblocked
- Decisions and the reason behind them, since future you will remember the decision and forget the why
- Help you gave and help you got: reviews, pairing, mentoring
- Praise and feedback, quoted or screenshotted, because you will not remember the exact words in six months
- Something you learned
You can skip hours, every meeting you sat in, and anything already written down in the ticket.
Work journal template
Copy this into whatever you’ll actually open: a text file, Notion, a Google Doc, your notes app.
Tue, Oct 7
Did
- [What you finished or moved forward], [result or number, if any]
Solved / unblocked
- [Problem], [how you fixed it]
Decided
- [Decision], because [reason]
Note to future me
- [Anything you'll want at review time: praise, a metric to check later, a link]Not every heading needs something every day. Most days you’ll only fill in one or two.
Prefer a spreadsheet? Use one row per day with these columns: Date, Did, Result or number, Solved / unblocked, Decided, Note to future me.
And if even that feels like too much, here’s the one-line version that still works: “Today I ___, which ___.”
Work journal examples
Here are three days from a backend engineer’s journal, written the way people actually write them: fast and a bit messy.
Tue, Oct 7
Did
- Merged retry backoff for the webhook worker. Failed deliveries
in staging went from ~6% to under 1%.
Solved / unblocked
- Nightly export kept timing out: missing index on events.created_at.
Added it, export went from 40 min to 6.
Decided
- Running the old queue in parallel for a week instead of a hard
cutover, because billing still reads from it.
Note to future me
- Priya (support lead) thanked us in #support for the export fix.
Screenshot saved.
Wed, Oct 8
Did
- Reviewed 4 PRs, including Sam's first one. Walked him through
our migration conventions.
- First draft of the RFC for moving notifications off the monolith.
Thu, Oct 9
Did
- Got paged at 2am for the payments latency spike. Rolled back the
cache config, recovered in 18 min.
Note to future me
- Write the post-mortem tomorrow. Good "ownership" example for review.None of these took more than two minutes, and each one already has a number, a name, or a reason in it, which is exactly what goes missing when you try to remember a month later.
How the journal pays off
On Friday you skim the week and pick three to six lines. That’s most of your weekly report done, and you’re editing instead of remembering.
At review time you search for numbers and “note to future me”. The CI fix in March and the support lead’s thank-you are right there, ready to go into your self-evaluation.
When you start job hunting, your best entries already read like résumé bullets, because they say what you did and what changed.
Where to keep it
The best tool is whichever one you’ll actually open every day. A plain text file is the fastest. Notion and Google Docs are easier to search and share. They all have the same two weaknesses, though: nothing reminds you to write, and nothing turns the entries into anything. Pulling together a weekly report or a self-review is still a job you do by hand.
Perfly is a work journal built to handle both of those for you:
- At the end of the day you jot down a few rough lines, in whatever language is fastest. Perfly splits them into separate items and you confirm which ones to keep. If you connect GitHub, Jira, Google Calendar, or Notion, it drafts entries from your activity too, using metadata only. If you work with Claude Code, Codex, or Cursor, your agent can write the entry for you.
- After your workday ends, Perfly tidies up the day’s notes and can send you an email or push notification when the draft is ready to confirm.
- When an item would be stronger with a number, it asks for the one that matters, like how many users or how much faster.
- On report day your weekly report is already drafted. At review time it drafts your self-review, and when you need a résumé it pulls from the same entries. Every sentence links back to the entry it came from.
Starting late? Connect GitHub and Google Calendar and Perfly can pull in the last 12 months of activity, so your journal doesn’t start empty.
FAQ
How long should a work journal entry be?
Two to five lines. If it’s taking more than a couple of minutes, you’re writing too much and you’ll stop doing it.
Should I write daily or weekly?
Daily is easier, which sounds backwards. On Tuesday evening you remember Tuesday clearly, but by Friday afternoon Tuesday is mostly gone. If daily won’t happen, weekly still beats nothing.
Is a work journal the same as a brag document?
They’re close cousins. A brag document is the curated highlight reel, and a work journal is the raw daily feed you pull those highlights from. Keep the journal and the brag doc mostly writes itself.
Where should I keep it if I might change jobs?
Somewhere you’ll still be able to open after you leave, and keep confidential material like code, customer data, and internal documents out of it. Summarize instead of pasting things in. Perfly’s integrations read activity metadata only, and its agent connection accepts short summaries, never code or document contents.
How much does Perfly cost?
30 days free with everything unlocked. After that it’s $6.99 a month, or $69.99 a year.