What should a work journal template include?

Five blocks: today's three objectives, a meeting notes block (attendees, decisions, your action items with due dates, their action items), a project status line per live project (stage, blocker, next milestone), a contacts and follow-ups block (who, context, what you owe them, next touch), and three end-of-day lines: what moved, what slipped, what you learned. Everything else belongs in the task list or the calendar.

How long should a work journal take each day?

About five minutes outside meetings: one minute for the three objectives, one for the project lines, one for contacts and two for the end-of-day lines. The meeting block is filled during or immediately after each meeting, while the decisions are still exact. If the daily entry regularly runs past ten lines, it is carrying prose that will not survive a busy week.

What is the difference between a work journal and a task manager?

The task manager holds things to do, with owners and due dates, and its entries disappear when the task is done. The work journal holds what the task manager cannot: why a decision was made, who said what, what you committed to, and what you learned. Tasks go in the task list, meetings go in the calendar, and decisions and commitments go in the journal, where they stay for years.

Why record what moved at the end of each day?

Because progress is the strongest daily driver of motivation at work. Teresa Amabile and Steven Kramer analysed nearly 12,000 daily diary entries from 238 knowledge workers and found that making progress in meaningful work, even a small win, did more for motivation and performance than any other workday event. A one-line record of what moved makes that progress visible on the days it does not feel like it.

Should I keep a work journal on paper or in an app?

Paper is fastest for the daily blocks but hard to search; a plain text file or notes app is searchable and easy to take with you. The one rule that matters more than the format is ownership: keep the journal outside tools the company controls, because a record that lives in a company account may not survive your exit, and its value is highest at exactly that moment.

How to Create an Effective Work Journal Template

Q: How do I review a work journal each week?

Set aside fifteen minutes on Friday. Roll every unfinished action item, yours and others', into next week, and give anything rolled three times a decision instead. Update each project's stage and flag blockers older than a week. Then pick next week's three objectives and write them at the top of Monday's page. Gail Matthews' goals study at Dominican University found that written goals plus weekly progress reports produced the highest achievement of the five conditions tested.

A work journal template should have five blocks: today's three objectives, a meeting notes block, a project status block, a contacts and follow-ups block, and three end-of-day lines. Each block is a fixed set of short fields, so a day's entry takes about five minutes outside meetings and still holds what you will need months later: what was decided, what you committed to, who you met, and how each project stands.

I kept a business journal through most of my executive career, at OSDN, Automation Anywhere, Oracle and Syntonetic: paper mostly, later digital, weekly and more often when things were on fire. It was built around objectives and it was for thinking; meeting notes and board preparation lived in minutes and task lists. I stopped about fifteen years ago. The template below keeps that split, with short record-keeping fields so that the thinking has room, and it is followed by one invented day.

Quick Answer: A work journal template needs five blocks: today's three objectives, meeting notes (attendees, decisions, action items with owners and dates), project status (stage, blocker, next milestone), contacts and follow-ups (who, context, what you owe them, next touch), and three end-of-day lines (what moved, what slipped, what you learned). Fill it in about five minutes a day outside meetings and review it for fifteen minutes on Friday.

Definition: A work journal is a dated record of decisions, commitments, conversations and lessons. It is not a task list and not a calendar; it holds what those two cannot, which is why something was decided, who said what, and what you learned.

Key Evidence: Amabile and Kramer's analysis of nearly 12,000 daily work-diary entries from 238 knowledge workers found that a sense of progress in meaningful work was the strongest daily driver of motivation and performance, which is why the template ends every day with "what moved". Gail Matthews' goals study at Dominican University found that people who wrote their goals down achieved more than those who only thought about them, and those who also sent weekly progress reports to a friend achieved the most.

Context: This page absorbs three earlier posts on meeting notes, project planning and networking logs; each is now one block of the same template.

Key Takeaways

Five blocks, in this order: three objectives, meeting notes, project status, contacts and follow-ups, end-of-day. About five minutes a day outside meetings.
Decisions and commitments go in the journal, tasks in the task list, meetings in the calendar; the journal holds what the other two cannot.
Fill the meeting block before you leave the room, and write feedback down in the words it was given.
Friday, fifteen minutes: roll unfinished action items (after three rolls, decide), update project stages, pick next week's three objectives.
Keep the journal outside company-owned accounts; its value peaks at the moment you leave.

Decide what goes in the journal, the task list and the calendar

The rule that keeps the template short: decisions and commitments go in the journal, tasks go in the task list, meetings go in the calendar. The journal records what the other two cannot: why a decision was made, who said what, and what you learned. When a meeting produces a task, the task manager gets the task and the journal keeps one line on who asked and why. Minutes are the team's record; the meeting block is yours, and it leaves with you.

Record	What it holds	Who reads it	How long it lives
Work journal	Decisions, commitments, who said what, project stage, lessons	You, before a review or a decision	Years; it follows you between jobs
Task manager	Things to do, owners, due dates	You, every day	Until the task is done
Meeting minutes	The agreed record of a meeting	Everyone who attended	As long as the team keeps them

Set up the five blocks

Copy this into a notebook or a note template. The timing note on each block is how long it should take; if it regularly takes longer, you are writing prose where a field will do.

DATE: __________


TODAY’S THREE OBJECTIVES  (1 minute, first thing)
1.
2.
3.


MEETING NOTES  (fill during or right after each meeting)
Meeting:                        Time:
Attendees:
Decisions:
My action items (due date):
Their action items (owner, due date):
Open questions:


PROJECT STATUS  (1 minute, one line per live project)
Project | Stage | Blocker | Next milestone (date)


CONTACTS AND FOLLOW-UPS  (1 minute)
Who | Context | What I owe them | Next touch (date)


END OF DAY  (2 minutes)
What moved:
What slipped:
What I learned:

Three objectives, never more. Fill the meeting block before you leave the room or close the call, because decisions blur within an hour, and record feedback in the words it was given; you will want the exact phrasing at review time. The project line uses stages: proposed, approved, in progress, blocked, in review, done. The contacts block is a relationship log.

The last line is the oldest prompt in the template. My own first journaling prompt came from a teacher at school, who had us open each entry with "What I learned today ...", and it is still a good way to start seeing the shape of a day.

Read one filled day

The entry below is invented: a product manager at a mid-sized software company, on a Tuesday with two meetings.

DATE: Tuesday 14 October


TODAY’S THREE OBJECTIVES

Get sign-off on the Q4 pricing change from Finance
Close the open questions on the onboarding redesign
Draft the customer email for the API deprecation



MEETING NOTES
Meeting: Q4 pricing review        Time: 10:00
Attendees: Priya (Finance), Tom (Sales), me
Decisions: Raise the Team tier by 8 percent from 1 December; grandfather
annual plans until renewal. Tom objected to the date; overruled by
Priya on cash-flow grounds.
My action items: Customer FAQ by Friday 17th.
Their action items: Priya, margin model by Thursday. Tom, sales
briefing on Monday.
Open questions: Do monthly Team plans get 30 days’ notice or 60?
Meeting: Onboarding design check-in        Time: 14:00
Attendees: Lena (Design), Marcus (Engineering), me
Decisions: Drop the guided tour; ship the checklist version.
My action items: Update the spec by Wednesday.
Their action items: Marcus to estimate the build by Thursday.
Feedback: Marcus said, “Your specs change after we start building.”
Fair. Note for the weekly review.


PROJECT STATUS
Q4 pricing       | approved     | none            | FAQ due 17 Oct
Onboarding v2    | in progress  | estimate pending| spec update 15 Oct
API deprecation  | proposed     | legal wording   | email draft 16 Oct


CONTACTS AND FOLLOW-UPS
Priya | pricing review | the FAQ draft for her comments | Fri 17 Oct
Dana (ex-colleague) | coffee last week, offered an intro to their
platform lead | a thank-you and a date | next week


END OF DAY
What moved: Pricing approved. Onboarding scope settled.
What slipped: API email not started; legal has not sent wording.
What I learned: Brief Sales before Finance. Marcus is
right about spec changes; freeze specs before estimates.

Run the Friday review in fifteen minutes

A journal that is never reread is a diary with a filing system. Mine became a habit because I could tell it helped me understand; that kept me at it on the unpleasant weeks. The weekly review has three steps. Roll every unfinished action item, yours and theirs, into next week; anything rolled three times gets a decision. Update the project stage lines and flag any blocker older than a week. Then pick next week's three objectives and write them at the top of Monday's page.

In The Art of Journaling, chapter 5, I set out a review process for any journal: set a time frame, look for what changed, revisit the difficult entries, pull out what you now know. The Friday review is that on a weekly clock. Matthews' study supports the habit: the group that wrote goals and sent weekly progress reports achieved more than every other group, including the one that wrote goals and did nothing else with them.

WEEKLY REVIEW: Friday 17 October (invented example)

Rolled: legal wording for the API email (mine, since Tuesday); Marcus’s estimate (his, now Monday). Decided: 30 days’ notice for monthly plans (Priya). Stages: Q4 pricing approved, FAQ sent. Onboarding v2 in progress, estimate late. API deprecation blocked on legal 8 days; escalate Monday. Pattern: two blockers were other people’s approvals. Ask earlier. Next week: 1. Unblock the API email. 2. Approve the onboarding estimate. 3. Pricing update for the board pack.

Choose paper, a file or an app

Paper is fastest for the daily blocks and worst for finding a decision from four months ago; a text file or notes app is searchable and can be copied out of the company's systems. If you use both, decide once which block lives where, as in the hybrid paper-and-app system, and see the apps that sync across devices for a phone-and-laptop setup. Whatever you pick, keep it out of tools the company can lock you out of; the digital journal privacy guide covers what that means.

Notice when the template is not working

Three signs. An emotional check-in filled daily while the meeting block stays empty is a diary; fill the meeting block first and add no blocks the template lacks. Entries past ten lines a day outside meetings will die in the first busy week; cut back to the fields. A journal in a company account may not survive your exit; move it to something you own before you need it.

Why a Work Journal Matters

The pay-off is the afternoon before a performance review, a board update or a job interview, when you read the last quarter's entries and pull three lists: decisions you made or influenced, commitments you kept, and feedback in the words it was given. Without a record those lists come from memory, and memory keeps the last three weeks and the worst day.

The entries I found most useful were from startups, where investors pulled one way and the market and the team pulled another. It was not pleasant. An entry under that pressure held thoughts, options and ideas for solving the problem, and later the solution. Writing it down slowed me: go slow to go fast. Goals went in the journal too, and at year end I read them against results, the ones I missed and the ones I exceeded, over a day or two away, a walk on the beach or an overnight train ride, on whatever cycle the company used. Less formal than the version in The Art of Journaling, but the book captures most of it. I stopped toward the end of my career because it had done its job; it just felt like time. I no longer have the journals; they went when I retired and downsized, and I do not miss them.

Sources

Amabile and Kramer, "The Power of Small Wins", Harvard Business Review, 2011 – the progress principle, drawn from nearly 12,000 daily work-diary entries by 238 knowledge workers
Gail Matthews, Goals Research Summary, Dominican University of California – written goals outperformed unwritten goals, and written goals with weekly progress reports to a friend outperformed all other groups