Skip to content

Example Transcripts

An interview transcript is the input Processor works from. The example on this page shows the kind of text that produces useful first-draft process maps — so you can try Processor on a known input before bringing your own interview notes.

This is a starting point too

Like the diagrams Processor draws, this transcript is an illustrative sample. Use it to get a feel for the input, then swap in your own.

What makes a good transcript

Processor reads a transcript and looks for the business processes it describes — who does what, in what order, and where decisions branch. You'll get the most useful diagrams when the transcript:

  • Describes how work actually flows — steps in sequence ("first the customer submits…, then the team reviews…, if it's approved…").
  • Names the actors or roles — who performs each step (the requester, the approver, the system).
  • Includes decision points and exceptions — what happens when something is rejected, missing, or escalated.
  • Stays reasonably focused — one conversation about a handful of related processes works better than a sprawling transcript covering everything.

Plain text is all that's needed. Speaker labels (e.g. BA: / SME:) are welcome but not required.

How to use the example

  1. Download the transcript below (or open it and copy the text).
  2. In the Processor panel, paste or upload it.
  3. Pick a target process count from the dropdown to match the "suggested count" note.
  4. Analyze, then draw a process to see the straw-man on your board.

New to the flow? See Getting started and the Which level am I? guide.

Example 1 — Food-delivery app (requirements elicitation session)

About this transcript

  • What it is: the transcript of a publicly available YouTube tutorial in which a business analyst elicits requirements for a DoorDash-style food-delivery app, moving from actors and functionality to workflows and user stories.
  • Processes it describes: browsing menus and placing orders, payment, order tracking and delivery, cancellation (including late-cancellation charges), restaurant and menu onboarding, and delivery-driver registration.
  • Suggested target count: 5–10.

Download a copy: Download this transcript (.txt)

What to notice: the text is raw auto-caption output — no punctuation, no speaker labels — yet it still names the actors (customers, restaurant owners, delivery drivers, admin), the steps, and the exceptions. Your own interview notes don't need to be polished either.

Processor user guide