Walk out of the discovery call with the stories already drafted.

Welcome to Issue #02.
Every Saturday I ship one field-tested lesson from live BA × AI delivery — the stuff I actually use on client work this week, not repackaged theory.

Last issue was the 30-minute setup before a project starts. This one is what I do inside the room. The gap most analysts lose time to isn't writing requirements — it's the 48 hours between a good call and a clean set of stories, where half the nuance evaporates. Here's how I close that gap to zero.

The live-capture setup

Three moves, all running before the stakeholder says their first sentence. Set them up once and every call after pays you back.

1. A transcript running from minute one

Recording with consent, a transcript captures every "actually, it's more like…" that you'd otherwise paraphrase from memory. You stay present in the conversation instead of scribbling. The transcript — not your recollection — becomes the source of truth you can cite later.

2. A story-shaped extraction prompt, ready before the call

I keep one prompt open in my BA Prompt Stack that turns raw transcript into draft user stories: actor, goal, reason, plus a bulleted list of open questions it couldn't answer. The moment the call ends, I paste the transcript and get a first draft in seconds — structured the way my backlog expects.

3. A confirm-in-the-room pass

With five minutes left, I read the AI's open questions back to the stakeholders and resolve them live. This is the whole trick: the ambiguity gets closed while everyone is still on the call, not in a follow-up email thread three days later.

What NOT to do

• Don't let AI invent acceptance criteria. It will happily fill gaps with plausible-sounding rules nobody agreed to. Every criterion still comes from a person in the room.
• Don't paste client audio or transcripts into a public model. Recordings are PII-heavy. Anonymize or use an enterprise tier — this is a contract-level rule, not a preference.
• Don't skip reading it back. A story the stakeholder never heard out loud isn't confirmed — it's a guess with good formatting.

Try this week

On your next requirements call: turn on transcription (with consent), and keep one extraction prompt ready. The second the call ends, run it, then spend five minutes cleaning the draft instead of an afternoon reconstructing it. Do it once and you'll never go back to memory-notes.

See you next Saturday.
— Dibya Mishra, Senior Business Analyst