Transcribe Audio & Video to Text

Okay, let's get started. Today is about talking to users before you write any code.

Most teams skip this step because building feels like progress and interviews feel slow.

But every hour you spend listening saves you a week of building the wrong thing.

So how do you run a good interview? First, ask about the past, not the future.

Asking if they would use it gets you polite lies. Asking about the last time gets you facts.

Second, stop talking. Your job is to listen, not to pitch.

If you catch yourself explaining your idea, you have stopped learning.

Third, write everything down. Memory is a terrible research tool.

Record the call, get a transcript, and pull the exact quotes later.

Let's look at an example from last year's class.

One team interviewed twenty nurses about scheduling.

Nobody asked for an app. Everyone mentioned the paper sheet taped to the wall.

That sheet became the product, not the app they planned.

How many interviews are enough? Usually fewer than you think.

When you can predict the next answer, you have enough.

For next week, run five interviews and bring the transcripts to class.

Okay, that's it for today. See you on Thursday.