Career Journal Template: What to Write Every Week
A simple three-question template for weekly career journaling. Takes under 5 minutes on Friday, gives you material for interviews and reviews for years.
The blank page is where most career journaling habits go to die.
You've heard the advice. Track your wins. Document your accomplishments. Write things down. Great. You open a note, stare at it, type something like "this week was busy," and close the app. Two weeks later you haven't opened it again.
The problem isn't motivation. It's that "reflect on your week" is a vague prompt, and vague prompts produce either nothing or rambling paragraphs that aren't useful later. You need specific questions. Here are three that work.
The template: three questions, every Friday
Set a timer for five minutes. Answer these three questions about your week. Done.
1. What did I do this week that I'd want to remember in 6 months?
2. Was there a moment where I handled something difficult?
3. Did I learn something or change my mind about something?
That's it. No color-coded categories, no rating scales, no elaborate tagging systems. Three questions. Under five minutes. Friday afternoon, before you mentally check out for the weekend.
Why these three questions (and not others)
Each one captures a different kind of career material, and together they cover most of what you'll need later.
Question 1 catches your accomplishments. This is the stuff that belongs on your resume, comes up in performance reviews, and gives you real answers in interviews. The "in 6 months" framing forces you to filter. You're not logging that you replied to 47 emails. You're capturing the project milestone, the deal you closed, the process you fixed. The filter also makes the question easier to answer -- instead of "what happened this week?" you're asking "what was worth keeping?"
Question 2 builds your STAR story library. Behavioral interview questions almost always ask about difficult situations. "Tell me about a time you dealt with a disagreement." "Describe a situation where something went wrong." These stories are gold in interviews, but they're the hardest to recall months later because your brain actively works to smooth over stressful memories. Writing down "I pushed back on the PM's timeline because the API integration wasn't tested and convinced the team to delay by a week" while it's fresh gives you a story you can actually tell later.
Question 3 tracks your growth. This is the one most people skip, but it's surprisingly useful. Changing your mind about a technology, a management approach, or a business decision is evidence of professional development. It also catches the quieter weeks -- you might not have shipped anything, but you learned that your assumptions about the customer onboarding funnel were wrong, and that's worth writing down.
What an actual entry looks like
Here's a real-ish Friday entry to show you what "good enough" looks like:
Worth remembering: Shipped the notification redesign. Open rates went from 12% to 28% in the first three days. Maria and I scoped the whole thing in two afternoons, so the actual build took less than a week. Worth mentioning in my next review.
Difficult moment: Thursday standup -- Luca wanted to add three more features to the release. I said no, explained that scope creep was what killed the last two launches, and suggested we track the requests for v2 instead. He wasn't thrilled but agreed. The release went out on time.
Learned/changed mind: I used to think dark mode was a nice-to-have vanity feature. Looking at the support tickets this week, it's the second most requested thing after better search. I was wrong. It's a real accessibility need for a chunk of our users, not just a preference.
Total writing time: about 4 minutes. Not polished. Not comprehensive. But in 6 months, this entry gives you an accomplishment with real numbers, a conflict-resolution story with a clear structure, and evidence that you update your views based on data.
That's more useful than anything you'd reconstruct from memory.
Most weeks are boring (and that's fine)
Some Fridays, you'll sit down and think "nothing happened this week." That's normal. Most work weeks aren't dramatic. You didn't save the company or have a breakthrough insight.
Write something anyway. Even a thin entry counts:
Worth remembering: Quiet week. Finished the refactor of the payment service tests. Not exciting, but the test suite runs 40% faster now.
Difficult moment: Nothing major. Had to give feedback to a junior dev about their PR -- spent a few minutes thinking about how to phrase it so it was useful, not discouraging.
Learned: Read that article about event-driven architecture. Still not sure if it applies to our stack, but the pattern for handling retries was interesting.
This took two minutes. It's still worth having. The thin weeks build the habit, and they fill in the timeline. When you look back over three months of entries, the quiet weeks give context to the busy ones.
When to do it
Friday afternoon works for most people. The week is fresh, you're winding down, and five minutes of reflection fits the mood. Some people prefer Monday morning as a look-back. Either works, but pick one and keep it consistent.
The worst time is "whenever I remember." That means never. Building the habit matters more than picking the perfect day.
What to do with your entries
After a few months, you'll have 12-15 entries. Each question feeds a different moment:
Before a review
Scan the "worth remembering" answers for concrete evidence of what you delivered.
Before an interview
Pull out the "difficult moment" stories and practice telling them out loud.
Before a career chat
Look at "learned" to spot patterns in what interests and energizes you.
The entries don't need to be polished to be useful. They're raw material, not finished products.
Start this Friday
You don't need a special app for this. A note on your phone works. A text file works. The three questions work in any format.
If you want something that structures this for you and helps you find patterns across entries, that's what Koru does. But the template works with or without tools. The point is to stop staring at a blank page and start answering three specific questions instead.
Five minutes. Three questions. This Friday.