A researchers guide to session observation:
look, listen, and type.

Why it matters: Behavior lives in the silence after a question. A great researcher observes the reaction, the response, and investigates the difference between the two. The space is where thinking happens. Each extra word is guiding the participant towards your own hypotheses and biases. This space is uncomfortable, and filling this space with follow ups, rephrasing, or leading is a great way to lose a huge benefit of research. So you did the smart thing and hired a professional moderator. Now what do you do? Sit on your hands? NO! Get typing!

What the moderator is actually tracking.

Three things, running in parallel the whole session: what the participant says, what they do (behavior vs. stated preference), and where they hesitate. The hesitation is the conversational crux. Here, the participant evaluates, and evaluation is where the information and insights live.

These "a-ha moments" emerge to form the differentiated product – the moments of delight, joy, or just plain emotional relief that show the experience knows you, understands you, and shifts based on what you need.

But seeing the a-ha moment is tricky! And trickier still is capturing them and creating alignment around them?

Rolling Research sessions aren't a black box.

So we include everyone in research sessions. Yes, everyone is invited (tho not everyone joins). So how do observers stay connected to the a-ha moments?

• The Session Calendar: While watching is opt-in, the calendar invites are not. Any interested person is added to a shared calendar with observer links.
• Slack threads: scheduled to send at session start, Slack reminds observers things are happening and provides a link to join. Observers congregate in these threads – there to watch together. During the session, they'll take notes, post context, flag questions to probe on, and interact with the moderator, who prioritizes and shares at the right time in session. Participant slack threads are where active, real-time learning happens.
• Session debrief: A five minute window after the session allows observers and moderators to share top line observations, Session surprises are noted, and refinements for future sessions are made. This is not synthesis, but a moment to share and align. The inter-session debrief for the researcher to refine protocol, not synthesize sessions.

Yes, but — my stakeholders are too busy to join sessions.

We get that joining and watching every session is just not possible, especially as work accelerates. The answer is Superstar sessions! The researcher flags the two or three best sessions — the participant(s) who surfaced the clearest articulation of the core finding, or who cleaved the hypothesis in the cleanest way. Watching a superstar session is the best way for busy stakeholders to see what actually happened, get connected to the a-ha moments, and experience the work. Once stakeholders have watched, Flash Findings land as validation, not revelation.

The real objection I hear in the "want to watch sessions" vibe isn't time. It's sessions that feel like researcher-owned territory. This is one of the biggest sad-face moments for me as a researcher, because research is about all of us learning together. That's where the name "Sibling Systems" came from: we're all siblings working together to co-create new information spaces of shared meaning. I realize that's a bit heady, but "learning together" is exactly what sets flash findings and rolling research apart from typical "vet it and forget it and get a report later" research.

The Bottom line: A project where the researcher alone is involved produces Flash Findings that feel more like a "go do." A backed claim, but still, a claim that is more "insight" and less "knowledge." A project where three teammates watched sessions and chimed in creates a sense of alignment on what we know – we agree on the knowledge we're creating. And this "agreed on knowledge" is precisely what your AI's RAG corpus needs.