Repo path
research/interviews/2026-04-28-musgrave-discussion-groups-live-edit/README.md
A short customer interview documenting live editing, respondent privacy and test-before-publish requirements for asynchronous groups.
Repo path
research/interviews/2026-04-28-musgrave-discussion-groups-live-edit/README.md
Notes
No additional notes recorded.
Mapped workstreams
Mapped appendices
Raw source preview
Raw, unprocessed file text shown below.
--- title: "Musgrave Discussion Groups live-edit interview" status: processed source_type: customer workflow interview session_date: 2026-04-28 duration: "5m 24s" customer: "Musgrave" participants: - Cliona Kennedy - Desmond Leo product_area: "Discussion Groups" tags: [musgrave, discussion-groups, live-edit, privacy, customer-evidence] --- # Musgrave Discussion Groups live-edit interview ## Source file - [discussion-groups-live-edit-interview.docx](./discussion-groups-live-edit-interview.docx) — original Microsoft Teams transcript export. ## Evidence relevant to launch - Cliona had needed to add a new topic after a live forum launched and sometimes simplified wording when the responses were not answering the intended question (0:38–1:22). - In B2B work, respondents must not see competitors' answers (1:55–2:06). - She preferred testing changes before making them live and saw that check as useful for training or junior users and for catching mistakes (3:25–5:07). ## What this supports Live editing, privacy between respondents and a test-before-publish flow answer concrete customer workflow needs in Discussion Groups. ## What this does not prove This short session does not measure time saved, project outcomes, renewal or willingness to pay for the product on its own.