Discussion ProjectSessionsQuotes DiscussionCodebookAnalysis

Mockup for docs/design-discussion-lens.md. The lens projects extracted quotes onto the researcher's uploaded discussion guide. Order is guide order (the interview rarely follows it); a question shows the balanced spread of responses, and an honest split count of who was asked vs where evidence landed. Cards use production timecode, PersonBadge and sentiment-Badge markup; everything .dl-* is invented and flagged in source.

Toggle No guide in the bar to see the empty state.

PROPOSED
PROPOSED 26 Jul 2026 — not built.
Part of the discussion-lens set. design-discussion-lens.md is status: pending and says in terms that there is “no shipped reality to reconcile against”; there is no discussion lens in the code. The UX is mockup-proven and the feature is not built — those are different claims, and this is the second one.

About your job

Last analysis experience

“Walk me through the last time you had to make sense of a batch of interviews.”

Asked in 8 sessions · evidence in 8

asked 8 ways
  • m1“Tell me about your last project where you had a pile of interviews.”
  • m1“When did you last sit down with a set of transcripts — walk me through it.”
  • m1“Last time you did analysis — what did that actually look like?”
  • m1“Take me back to the last study you analysed.”
[04:12]
“Honestly it was a spreadsheet and a lot of swearing.” p3Rachel
frustration
[04:31]
“I'd tag everything by hand, then re-tag half of it a week later when the story changed.” p3Rachel
[11:58]
“I mostly live in Miro. Sticky notes, cluster, photograph the wall.” p6Tomas

Biggest frustration

“What's the most frustrating part of that whole process for you?”

Asked in 8 sessions · evidence in 6

Most named the re-tagging churn4 of 6

[06:40]
“By the time I've coded it all, my framework's moved on and I have to redo it.” p1Marcus
frustration
[09:02]
“The manual bit. It's just hours I don't have.” p7Devi

A couple pointed at sharing, not analysis2 of 6

[14:20]
“Analysis is fine. Getting it into a deck the client trusts — that's the pain.” p5Jon

Try the prototype

Task — participant drives; moderator observes. “Have a go at exporting a report to share with a colleague.”

First impressions of export

“So — how did you find that? Was the export what you expected?”

Asked in 8 sessions · evidence in 7

asked 7 ways
  • m1“What did you make of the export there?”
  • m1“Did that do what you thought it would?”
  • m1“Talk me through what just happened when you hit export.”
  • m1“Any surprises with the export?”

Most found it obvious5 of 7

[22:03]
“I just hit Export and it did the thing.” p3Rachel
satisfaction
[22:11]
“And that's exactly what I'd expect — no menu-diving, no ‘are you sure’ dance. It just went.” p3Rachel
[18:47]
“Button was right where I looked. Done.” p1Marcus
[31:15]
“Obvious. Next.” p7Devi

A few wanted a preview before it went2 of 7

[25:52]
“I clicked it and then panicked — did it just send to everyone?” p5Jon
doubt
[26:04]
“I'd want to see what's going out before it goes. Just a glance.” p5Jon
[29:38]
“A little confirmation step, just so I know what I'm handing over.” p2Aisha

One hit a blocker1 of 7

[27:19]
“It was greyed out and I couldn't tell why. I just sat there.” p6Tomas
confusion

Naming the themes

“If you had to name what you just saw, what would you call it?”

Asked in 8 sessions · evidence in 2 · ran short on time in most sessions

[44:02]
“I'd call it ‘the export panic’, honestly.” p5Jon