What makes a reflection reflective
Most reflection examples online fall into two piles: academic samples from university writing guides, and lists of prompts. Both are useful. Neither says clearly what separates a reflection that gets marked down from one that does not. It is one move: going from what happened to why it happened, and from why to what changes.
University guides often describe three levels:
- Descriptive. "I gave the medication and documented it. Later my preceptor asked for the pain score." Accurate, and not yet reflection.
- Analytical. "I treated giving the medication as the end of the task, because two other patients needed me." Now there is a reason.
- Critical, or transformative. "Assessment is a cycle, not a step. From Thursday I write the reassessment time on my handover sheet." Now there is a change, tied to a concept and a date.
Every example on this page reaches the third level. If you are revising your own reflection, find the line where you explain why, and the line where you say what you will do. If either is missing, that is the edit.
How to write a reflective journal entry
- Write soon. Same day if you can. Details fade within a day, and feelings get rewritten.
- Facts first. What happened, who was there, what you did. Keep judgement out of this part.
- Feelings, then and now. Short, honest, and separate from the facts.
- Ask why, twice. The first answer is usually the obvious one ("I was busy"). The second is where the learning is ("I had no reminder because I treat medication as one step").
- Connect it. To a course concept, to earlier feedback, to a pattern in your own past entries.
- One action with a date. Small enough to actually do at the next chance.
Learning journals
A learning journal is a reflective journal pointed at a skill: a language, a course, an instrument, a new job. The structure is the same, with two additions. Add a consistent number (hours, scores, problems solved), and write weekly rather than after every session. The Spanish example shows the shape. Week to week the entries look small; read eight of them in a row and the progress, or the plateau, is obvious.
Closing the loop
The question most reflection guides leave open is what happens after you write. A reflective journal where each entry starts fresh is a set of good intentions. Two habits fix that:
- Start each entry by checking the last action. Did you do it? What happened? That single line is evidence of learning, which is what assessors and your own future self both want.
- Read back once a month. Look for the same "why" appearing in different situations. In the personal example, saying yes in under ten seconds shows up twice. A pattern across entries is worth more than any single reflection.
Common mistakes
- All description. Three paragraphs of what happened and one line of "I learned a lot." Flip the ratio.
- Defending yourself. A reflection is not an appeal. Name your part plainly, the way the team lead example does.
- Vague actions. "Communicate better" cannot be checked. "Say 'let me check with the team' before agreeing to scope" can.
- Theory without the situation. Name-dropping a model without tying it to what happened reads as filler.
- Identifying details. In clinical, teaching or client reflections, use initials or roles, never full names.
If the reflection is about a team project rather than your own part in it, a lessons learned template or a sprint retrospective gives the group a shared structure.
Reflections that change what you do next week
Keep your reflective journal in Scribelet, turn every Now what into a dated task, and ask your entries which actions you followed through on. Free to start, encrypted at rest.
Free plan, no credit card. See pricing