Cluster: workshop-as-shared-build

Post-Session Notes That Actually Help

By Michael Polzin, Regenerative Architect, IamHITL. Published 2026-07-01.

A session that felt clear on Wednesday tends to blur by the following Tuesday. The notes you write in the last five minutes are what carries the loop across that gap. Most session notes fail because they try to be a transcript. Yours do not have to.

What notes are actually for

Between sessions, you are the one holding the practice. The notes are the handoff from the version of you who just did the work to the version of you who will pick it back up in seven days. That is a smaller job than "capture everything," and a bigger job than "write down what we said." The goal is a note that a tired, distracted future-you can act on without re-reading the whole file. In the practitioner literature on reflective practice, brief structured prompts outperform open-ended journaling for retention across weeks (Class E, Schon 1983 and subsequent replications).

The four-line structure

Aim for four short lines. Any more and you will stop writing them. Any fewer and the loop drops signal.

1. What I noticed. One sentence on the moment in the session that carried the most information. Not the most emotional moment, the most informative one. Sometimes they are the same. Often they are not.
2. What I tried. The concrete move, phrase, or shift you attempted, in the words you actually used. If you cannot remember the exact words, write down what you can, and mark the gap (Class U).
3. What happened. The immediate response. What shifted, what did not, what surprised you. Keep it observational. This is the closest thing to a receipt the loop produces.
4. What I want to test next. One thing, not five. A specific move you can run at the next session or during the week. If you cannot name a next test, write "hold and observe" and stop. That is a valid entry.

Four lines. Roughly three minutes. Written into the same file every time so the sequence becomes its own record. The structure is deliberately narrow because friction is what kills a practice, not effort (Class C, matches the tool-use log pattern we already use in the workshop).

Where honest labels help

The notes will contain guesses. That is fine, as long as the guesses are labeled. We use the same evidence-class tags across the workshop and the receipts on this site: B for something you can inspect directly, E for something you are relying on an outside source for, F for something you have set up as a falsifier (a specific outcome that would tell you the move did not work), U for anything unverified. A note that says "the shift on Tuesday felt real (U), and I will know by Friday if the sleep pattern also moved (F)" is doing more work than a paragraph of certainty.

None of this is therapy. None of it treats or diagnoses anything. It is the practitioner side of a human-in-the-loop practice: you are the one closing the loop between what you tried and what happened, and the notes are how you keep that loop honest week to week.

What to skip

Skip the summary. Skip the mood rating. Skip anything you are writing because you think you should. A three-minute note you actually write beats a fifteen-minute note you skip, and the skipped one is the more common failure mode in every practice-tracking study we have looked at (Class E, generalized from adherence data across behavior-change interventions; specifics vary and none of it maps one-to-one to this context).

If you find yourself writing the same "want to test next" three sessions in a row, that is a signal, not a failure. It means the move is worth bringing to the next workshop conversation rather than testing alone. That is exactly what the loop is for.

Keep going