I’m using reflexive thematic analysis as outlined by Braun & Clarke, which makes room for subjectivity – not just as something to “manage,” but as a central part of meaning-making. That means your values, experiences, and responses matter and should be visible in your process.
For me, journaling wasn’t just about transparency for the sake of a future methodology chapter. It helped me:
• Track how my thinking changed over time
• Record doubts, questions, and decisions so I could revisit them
• Notice emotional responses I might have brushed off
• Stay connected to the humanity of my participants
In short, it helped me be a better, more self-aware researcher.
Why I Chose Day One as My Journaling Tool
First of all, I paid full price for Day One on apples App Store and was in no way gifted or sponsored anything for this. I did start with apples free journaling tool which may also work for you.
I wanted a digital journal that was:
• Easy to access across devices (I could journal straight after interviews on my phone, or type up a longer reflection on my laptop…or access things from my iPad during supervisor meetings)
• Searchable and taggable (so I could find entries linked to certain interviews, moments, or themes). This was the biggest downside to the Apple free one as they simply did not have it and the tags were really important for me
• Flexible (I could insert screenshots of coded segments, voice memos, or links to articles I was thinking about)
Day One ticked all those boxes. It also has a really clean, distraction-free interface, which meant I actually used it.
What I Wrote About (with Real Examples)
I didn’t use a rigid structure, but over time, a few types of entries emerged:
• Post-interview reflections: What stood out? What surprised me? What emotional responses did I have? Did anything feel hard to hear or hard to believe?
• Coding notes: After a coding session, I’d jot down what I found challenging or energising. Sometimes I’d question myself: “Am I forcing this theme because I want it to be there?”
• Theme development entries: When a theme was forming or changing, I’d write about how it emerged and why I thought it mattered. These entries were messy and full of “maybe it’s actually about…” moments.
• Supervisor meetings: I’d quickly record what we discussed, what I felt unsure about, and what I was excited to try next. This helped track how our conversations shaped the project.
• Messy feelings: I wrote entries like “I’m worried this isn’t interesting enough,” or “I think I’m over-identifying with this participant.” These were often the most useful entries when it came to writing my reflexivity section.
How Often I Journaled
This varied depending on the phase of research. Roughly:
• After each interview (within 24 hours)
• After each major coding session
• Anytime I felt stuck or had a strong reaction
• After supervision meetings
• When something shifted in my thinking
I didn’t force myself to write every day. But I did treat journaling as an essential part of the research, not an “extra.” I’d often set a timer for 10 minutes and just see what came out.
Prompts I Used (or Wrote to Myself)
These were a mix of pre-planned and spontaneous:
• What assumptions am I bringing today?
• What is sitting uncomfortably with me?
• What did I want to find, and did I find it?
• What voices or perspectives am I ignoring here?
• Is this theme emerging from the data…or from me?
• What’s changed in how I see this topic since I started?
Sometimes I just started typing: I don’t know what to write but I feel like something’s shifted…
What I’d Do Differently Next Time
Looking back, a few things I’d improve:
• Be more consistent in tagging entries by theme, stage, or emotional tone
• Include more screenshots from my coding software (NVivo) to link journaling directly with data
• Write the messy stuff sooner, I often waited until I had a “neat” insight, but the raw uncertainty was just as valuable
• Schedule regular reflection time into my week, not just when things felt intense
Why This Helped So Much
Journaling helped me stay accountable to my values. It reminded me that I wasn’t trying to be an objective robot sifting through words…I was a human, engaging deeply with other humans’ stories.
It also gave me material I later used in my methodology and discussion chapters. I could literally quote past entries that showed how my themes emerged, or how I wrestled with a particular coding decision.
More than anything, it was a space to think. Not to prove anything, just to notice, reflect, and stay open.
Final Thoughts
If you’re doing qualitative research and have been told to “keep a reflexive journal,” I hope this helped lift the veil a little. You don’t have to write perfect, poetic entries. You don’t have to journal daily. You just have to show up with honesty and curiosity – and find a method that helps you track your learning as you go.
Day One worked for me. Maybe a notebook, Word doc, or voice memo app will work for you.
Whatever you choose, just start. The messy thoughts are often the most meaningful.
Melissa Smith 