Working with Structured Reflection in Practice
I've spent more years than I'd like to admit wrestling with reflection frameworks in clinical and organizational settings. People keep asking me about Hansen Guided Reflection Questions because they've heard it produces cleaner thinking than freeform journaling, which is true, but the reality is messier. I'll walk through how it actually works, where it trips people up, and what I do when the standard approach falls apart. The Hansen framework is a set of structured prompts designed to move a person through a deliberate review of an experience, ideally extracting actionable learning rather than just venting or reviscribing events. The questions typically follow a sequence: What happened? What did I notice? What assumptions were I working from? What would I do differently? The exact phrasing varies depending on who's adapted it — healthcare, education, and leadership coaching all have slightly different versions. Here's what most guides leave out: the value isn't in answering each question perfectly. The value is in the friction between them. When you push past "What happened?" into "What assumptions was I working from?" most people hit a wall. That wall is where the actual work lives.
The Method, Broken Down
Start with the factual layer. Write down what occurred without interpretation. This seems obvious and nobody follows it. I see people skip straight into analysis because they're in a hurry or uncomfortable sitting with raw data. Two minutes of pure description saves twenty minutes of correcting course later. Your questions here are simple: timeline, actors, outcomes, observable behaviors. Nothing more. Then move to the interpretive layer. What did you notice that surprised you? What didn't match your expectations? This is where most reflection sessions die because people conflate observation with judgment. "The team was unmotivated" is not an observation. "Three people checked their phones during the entire forty-five-minute briefing" is. Train yourself to separate these before proceeding. The assumption audit is the hardest section and the one most practitioners rush through. List the beliefs you held going into the situation that turned out to be wrong or incomplete. Your assumptions about timelines, stakeholder priorities, resource availability, risk factors. Write them down explicitly. If you can't identify any wrong assumptions, you either didn't learn anything or you're not being honest with yourself. Both are worth noting.
Finally, the forward-looking questions. What would you change? What would you keep doing? What do you need to investigate further? This section should produce concrete next steps, not vague intentions like "I'll communicate better." "I'll send a summary email within two hours of each client meeting" is a next step.
Get the Full Details
A Real Problem I Ran Into
Last year I was running a Hansen-style reflection session with a senior project manager who kept circling back to blame external factors — budget cuts, leadership decisions, vendor failures. We were stuck on the assumption audit for forty-five minutes and producing nothing. The standard framework wasn't working because his defensive patterns were too well-practiced. He'd done enough corporate self-improvement workshops to recognize the exercise and sidestep it. The workaround was to change the order. Instead of starting with the facts and moving toward assumptions, I flipped it. We started with the assumption audit directly. I asked him to write down every reason the project had gone off track before he was allowed to describe what happened. By the time he finished, he'd listed eight external causes. Then I asked him to pick the one he was most responsible for influencing and trace his role in it. The entire conversation shifted in about six minutes. Structure matters less than sequencing sometimes.
Counter-Intuitive Things Most People Miss
First, more questions don't make reflection deeper. The Hansen framework works best with five to seven prompts maximum. When you add more, people start answering the easy ones and glossing over the hard ones. They check boxes. The quality drops noticeably after question seven. Keep it short and force the discomfort early. Second, written reflection and verbal reflection produce different results. Writing forces linear thinking and exposes gaps in your logic that conversation smooths over. If you're using this for serious professional development, always write first, discuss second. I've seen the opposite recommendation from people who value collaborative processing, and while that has its place, it tends to reinforce confirmation bias rather than challenge it. Third, the reflection is only as good as your honesty threshold, and that threshold is almost always lower than you think. The first pass through any reflection framework produces surface-level answers. The second pass reveals the actual issues. The third pass, if you're willing to go there, uncovers the uncomfortable truths most people avoid. Budget time for at least two rounds on anything that matters.
Where This Approach Breaks Down
Hansen Guided Reflection Questions assumes a baseline of self-awareness and willingness to be uncomfortable. It fails completely with people who lack the vocabulary for internal states or who are operating under acute stress where cognitive bandwidth is already depleted. In crisis situations, structured reflection is the wrong tool. A quick after-action review with a focus on immediate corrective steps works better and takes ten minutes instead of an hour. It also doesn't account well for cultural differences in communication style. In some professional cultures, direct self-criticism isn't normative or safe. The assumption audit, which requires admitting your beliefs were wrong, can feel like professional self-harm in environments where maintaining face is structurally important. In those contexts, reframing the questions around organizational learning rather than personal failure produces usable results without triggering defensive resistance. If you're working with teams rather than individuals, the framework needs adaptation. Individual reflection surfaces personal blind spots. Team reflection surfaces coordination gaps, and the questions need to shift accordingly. The "what assumptions were we working from" becomes "what assumptions did our group share that may not have been shared with stakeholders?" It's a meaningful distinction that the standard template doesn't capture.
Practical Setup
You don't need special software. A document with the prompts as headers and a dedicated space below each works fine. I've used Google Docs, handwritten notes, and a simple spreadsheet. The medium doesn't matter. What matters is consistency — running the same structure repeatedly builds a pattern you can compare across time. One-off reflections are forgettable. Regular reflections create a record. Schedule reflection after significant events, not just at periodic intervals. A project milestone, a difficult conversation, a decision with unexpected consequences — those are the moments worth processing. Monthly reflection calendars produce mediocrity because people reflect on whatever happened to be memorable that month rather than whatever was actually important. Trigger-based reflection is more reliable. The output should be a short summary, not a thesis. Three to five sentences capturing the main insight and one specific action for next time. Anything longer indicates you're documenting rather than reflecting. Documentation is valuable separately but it's not the same activity.
