A professional reflection journal earns its time only if it changes what you do next. Three short daily notes (a morning list, a midday adjustment, an evening review) and one twenty-minute weekly review are enough, provided the weekly review ends with at least one decision you will make differently. Everything else on this page, the check-in questions, the merged weekly table, the one-row action plan, and the prompt table, exists to produce that decision.
I kept a journal through my executive roles, as GM at OSDN, Slashdot, and SourceForge, COO at Automation Anywhere, VP at Oracle, and CEO of Syntonetic. It was organised around business objectives, kept on paper and later digitally, written weekly and more often when things were on fire. I have not kept one in fifteen years; I stopped towards the end of my career because it had done its job, and it just felt like time. The notebooks went when I retired and downsized, so the examples below are illustrative; none is a page from my own. The daily check-in is the routine I would recommend to someone starting now; the weekly review is the part I actually did.
Quick Answer: Each day, write a morning list (three tasks, one risk, one mood word), a midday adjustment (one thing dropped and why), and an evening note (what went well, what tripped, one lesson). Each week, fill a six-row review (results, goals, meetings, numbers, emotions, next week) and turn one insight into one action with a result to check the following week. Under 15 minutes a day.
Definition: A professional reflection journal is a work record reviewed on a schedule, where each entry moves from what happened to why it happened to what you will do differently. The University of Cambridge Reflective Practice Toolkit describes that describe, evaluate, analyse, plan sequence as the common shape of reflective models, including Gibbs' reflective cycle.
Key Evidence: The Cambridge toolkit notes that reflective writing is already part of working life "from appraisal and planning documents" onward, and that an appraisal asks you "to record what went well and why as well as identifying areas for improvement." A journal kept this way is the raw material for that.
Key Takeaways
- Answer the morning question "What decision is pending that I am avoiding?" every day; a named decision tends to get made by the evening.
- Budget 3 minutes in the morning, 2 at midday, 5 in the evening, and 20 for the weekly review: under 15 minutes a day.
- Fill one six-row weekly table (results, goals, meetings, numbers, emotions, next week) and read the rows against each other, numbers first.
- End every weekly review with one action row: insight, goal, step, and a result to check the following week.
- Apply the rule: an entry that names no decision you would make differently is a diary entry. One per week, minimum.
The daily check-in: three moments, twelve questions
The three moments take about ten minutes in total: three in the morning, two at midday, five in the evening.
MORNING (3 min) 1. What are the three things that must get done today? 2. What is the one thing most likely to go wrong? 3. What decision is pending that I am avoiding? 4. Mood, one word.MIDDAY (2 min) 5. What is done, and what is not? 6. What am I dropping from the list, and why? 7. Do I need to change the plan, or just the pace?
EVENING (5 min) 8. What went well, and what caused it? 9. What tripped me up, and what caused that? 10. What did I do that I would do differently? 11. What did I learn today? 12. What goes on tomorrow’s morning list?
Question 3 is the one most people skip. A pending decision named in the morning tends to get made by the evening; an unnamed one drifts for weeks. My own first journaling prompt came from a teacher at school, "What I learned today ..." as the opening line of an entry, and I still think it is a great way to start visualising the day, which is why it sits at question 11.
An illustrative day
Suppose a sales manager's Tuesday. Morning: "Three things: renewal call with Harlan, sign off the Q3 forecast, one-to-one with Priya. Likely to go wrong: Harlan pushes on price and I fold. Avoiding: whether to put Dev on a performance plan. Mood: tight." Midday: "Forecast done. Moved Priya's one-to-one to Thursday; the forecast took two hours and she deserves a proper hour. Change of pace, same plan." Evening: "Harlan call went well because I opened with the usage numbers and left price until he raised it. Tripped on the forecast: I had no view of pipeline by stage and rebuilt it from scratch. Would do differently: ask for the stage report on Monday. Learned: I still avoid the Dev decision when I am tired. Tomorrow: Dev decision, first thing."
That is about 120 words, and each answer names a cause or a next step.
The weekly review: one table, six rows
Set aside twenty minutes, ideally Friday afternoon or Monday morning, and fill one table. The rows below replace the separate achievement, goal, meeting, KPI, and emotion tables that most templates spread across a page; merged, the rows can be read against each other.
| Row | What to write |
|---|---|
| Results | What got done, what did not, and the cause of each |
| Goals | Each active goal: on track or not, and the one adjustment if not |
| Meetings | The two or three interactions that changed something, and what you would repeat or stop |
| Numbers | The three or four measures you own: target, actual, and a cause for any gap |
| Emotions | Where dread, irritation, or relief showed up, and what preceded it |
| Next week | The three things that must happen, and the decision you will make differently |
The order is numbers before feelings. The most valuable journaling I did was at the startups, pulled one way by investors and another by the market and the team. An entry under that kind of pressure held thoughts, options, and ideas for solving the problem, and later the solution. Goals went in too, and I reflected on the ones I did not reach and the ones I exceeded. It was not a pleasant exercise, and I would not dress it up as one. It became a habit, and I knew it helped me understand better; that is what kept me doing it when it was unpleasant.
One boundary from that practice is worth copying. Meeting notes, board preparation, and conversations were never in the journal; those lived in minutes and task lists. The journal was for thinking; the record-keeping lived elsewhere. So the meetings row above holds what a meeting changed and what you would do differently in the next one.
An illustrative week
Results: "Two of three enterprise proposals out; the third slipped because legal review took four days." Goals: "Pipeline coverage goal off track; adjustment: stop adding small deals to make the count look better." Meetings: "Harlan renewal: repeat opening with usage data. Board prep: stop presenting pipeline without stage." Numbers: "Customer calls 12 of 15. Gap cause: three calls pushed on Thursday afternoon." Emotions: "Dread before the two calls with accounts that churned last year; both got pushed." Next week: "Write a two-line prep script for churned-account calls before booking them. Decision made differently: book those calls for mornings, when I do not push things."
Read the rows together and the review writes its own action: the numbers row says 12 of 15, the emotions row says why those three were the ones missed, and the next-week row turns that into a script and a scheduling rule.
The action plan: one row, four columns
The action plan is one row, added at the end of each weekly review and checked at the start of the next.
| Insight | Goal | Step | Result (checked next week) |
|---|---|---|---|
| Calls I dread get pushed to Thursday and then dropped | 15 of 15 customer calls next week | Two-line prep script for churned accounts; book them before 11am | Next Friday: calls made, and whether the script was used |
The decision rule that keeps this honest: a reflection entry that does not name a decision you would make differently is a diary entry. One per week, minimum. Diary entries are fine, but they are not what a professional journal is for. The phrase I used for the point of the exercise was "go slow to go fast": writing the problem down slowed my thinking and made me work it through thoroughly, so that I could then move quickly. In Write Your Way, chapter 13, I set out a fuller toolkit for the harder decisions (a brain dump, a weighted pros-and-cons list, a decision matrix, and a decision deadline for when analysis stalls); the weekly row is the routine version of the same idea.
Monthly and year-end
Once a month, reread the four weekly tables and the four action rows. Look for the insight that appeared twice; that one becomes the month's single goal. Once a year, do the same at greater length. I ran a year-end review on calendar-year, fiscal-year, or mid-year cycles depending on the company, and the three were no different from one another: a day or two of retreat, sometimes a walk on the beach, sometimes an overnight train ride, with the year's entries and goals to hand. It was less formal than the version in The Art of Journaling, though chapter 5 of that book captures most of the process I had settled into: review on a regular cycle, mark the recurring themes, reflect on what they mean, and track progress against specific goals over time.
Prompts by category
Use these when a daily or weekly answer comes out thin. Two per category is enough; a longer list gets skimmed.
| Category | Two prompts |
|---|---|
| Performance | What did I finish this week that I would be comfortable being judged on? What did I start that I should not have? |
| Emotions at work | Which reaction this week would I not want a colleague to have seen? What happened in the hour before it? |
| Growth | What did I do for the first time? What did I do for the fiftieth time that someone else should now be doing? |
| Collaboration | Whose work did I make easier this week, and whose did I make harder? What did I owe someone and not deliver? |
| Decisions | Which decision did I make with less information than I could have had? Which one did I delay past the point where waiting helped? |
| Clients | What did a client tell me this week that I did not want to hear? What did I promise that depends on someone else? |
| Work and the rest of life | Which evening did work take that it should not have, and what did I fail to say no to? What recharged me, and can it be scheduled? |
When this does not work
Reflection becomes self-criticism. If the evening note is a list of failures with no causes, the entries are venting. The Cambridge toolkit's summary of Gibbs' cycle is the corrective: after feelings comes evaluation, then analysis, then a conclusion about "what other actions (if any) we could have taken," then an action plan. Stop at feelings and you have a diary; push through to the action and you have a journal.
Numbers rows with no owner. A measure you do not control produces a gap you cannot close, and a weekly row that only records that gap will teach you nothing. Track the three or four numbers you can move, and put the rest in the results row as context.
Reviews skipped in busy weeks. The busy week is the one that most needs reviewing, and the one where the twenty minutes will not happen. Rule: in a week like that, do the evening note only, five minutes, and let the weekly table wait. A gap in the table is recoverable; a gap in the daily notes is not, because the causes are forgotten by Friday.
Journals kept on employer devices. An evening note that says "I still avoid the Dev decision" is not something you want in a company-owned account. Keep the journal on your own device and in your own storage, and read the guide to digital journal privacy before you decide where it lives.
Milestones, promotions, and the documentation you build up for review cycles belong in a career progress journal, kept separate from this routine.
Start tonight
Tonight, answer the five evening questions in five minutes. Tomorrow morning, answer the four morning ones. Fill the weekly table on Friday, and add one action row before you close it.
Why a professional reflection journal matters
Experience only teaches when it is examined, and a working week leaves no time for that unless the time is scheduled. The daily notes and the weekly table are that schedule. Over a year they hold your decisions and their outcomes, your numbers and their causes, and the material the Cambridge toolkit says an appraisal will ask for: what went well and why, and where to improve.
The part that mattered in my own case was understanding. Writing a problem down under pressure slowed my thinking enough to work it through, and that is why the rule about naming a decision sits at the centre of this page.
Related reading
- Career Progress Journal: Track Milestones, Achievements and Reviews
- How to Create an Effective Work Journal Template
- How to Start Your Career Development Journal
- Digital Journal Privacy: How to Protect Your Entries
Sources
- University of Cambridge Reflective Practice Toolkit: Reflective writing – reflective writing as part of appraisal and planning documents, and appraisals asking what went well and why plus areas for improvement
- University of Cambridge Reflective Practice Toolkit: Models of reflection – the description of Gibbs' reflective cycle (description, feelings, evaluation, analysis, conclusion, action plan) used in the definition and the self-criticism section
