Find the pattern across a round of user interviews
A themed synthesis where every theme points back to the interviews that produced it. Built for a product team with twelve interview transcripts and no time to reread them.
Notion
4 steps1 integrationRuns before each meeting
Twelve transcripts, remembered by whoever ran them. What it costs while the work is still done by hand.
- 01Each interview is remembered by whoever ran it.
- 02Themes are asserted from the two most recent conversations.
- 03The transcripts are never opened again.
- Read notes12 transcripts · 4 weeks
- Group themes6 themes · 84 quotes
- Count voicesonboarding · 9 of 12
- Publishcreate_page · quotes linked
One workflow, four steps. ModuleX drafts this graph from a single sentence, and every step stays editable.
- 01Read the interview notes.Notion
- 02Group what was said by theme rather than by interview.ModuleX
- 03Note how many people raised each theme, and who.ModuleX
- 04Publish the synthesis with quotes linked to their source.Notion
The workflow is an editable graph. Reading runs freely; publish the synthesis with quotes linked to their source waits for your opt-in approval until you loosen it. The graph is the receipt.
Themes, with receipts. Paste this into ModuleX chat, or hit Use this workflow.
find the pattern across a round of user interviews: read the interview notes; group what was said by theme rather than by interview; note how many people raised each theme, and who; publish the synthesis with quotes linked to their source. Ask me before anything is sent or written.
to: composerOr skip the workflow entirely. Ask the assistant in chat and it runs the same job agentically: it picks the right actions, chains them, and reports back. The composer is for when you want it repeatable.
Find the pattern across a round of user interviews. A themed synthesis where every theme points back to the interviews that produced it.
- notion · create_page
A themed synthesis where every theme points back to the interviews that produced it.
Where this fits. The tools it runs on, and the teams that run it.
Keep the momentum. Nearby workflows that reuse the accounts you just connected.
Assemble the evidence pack for a reviewAn evidence pack assembled from your systems, with the gaps named and assigned. Built for whoever collects the same screenshots and exports every audit cycle.
Build a one-pager on a company before you meet themA one-pager combining public background with your own record, reusable by whoever meets them next. Built for anyone walking into a meeting knowing only the company name.
Capture a request as a task without leaving the threadA task that carries the original request and links back to where it was made. Built for anyone who says yes in an email and then forgets.
About this use case.
No. It reports what was said, grouped.