JustToBeDone: Transcribe and Analyze Interviews

You ran six user interviews and now you sit over hour-long recordings with a notebook. Transcribing eats the evening, and you end up with three conclusions. JustToBeDone takes the routine on: it turns interview audio into text and breaks it down with the JTBD methodology. 🎧

It is built for product managers and product teams, and works as a mini app inside Telegram.

What it does with a recording

Four actions, as described by the developer:

• JTBD analysis. The interview is reviewed through the Jobs To Be Done methodology.
• Audio transcription. The recording becomes text.
• Speaker separation. The interviewer's lines are split from the participant's.
• Results as files. Output arrives as text files that are easy to save or forward to the team.

Press the Start button to begin. You get three free analyses and thirty minutes of interview transcription at the start. 🎁

JTBD in a nutshell

The idea is simple: people do not buy a product for its own sake. They hire it to do a specific job in their life. Nobody wants a drill, they want a hole in the wall. Nobody wants a notes app, they want peace of mind that nothing gets forgotten.

So in an interview you listen less about features and more about the situation: what happened, what the person wanted, what they tried before.

What to look for in a transcript

JTBD interviews usually hunt for the forces behind a choice. They are often grouped into four kinds:

1. Push. What was wrong with the old solution.
2. Pull. What attracted the person to the new one.
3. Anxiety. What they feared about switching.
4. Habit. What kept them on the old way.

A clean transcript makes these phrases easy to find and compare across respondents.

Running interviews that analyze well

Analysis is only as good as the recording. A few rules save time:

• Record in a quiet place, ideally with a separate microphone.
• Ask the person to recall the last real case instead of speaking "in general".
• Do not feed answers and avoid questions that a plain "yes" can settle.
• Ask for permission to record at the start of the call.

The more honest and specific the respondent is, the richer the final report. 🎤

When a transcript really pays off

With one or two interviews, notes may be enough. With ten, you need text: you cannot keep every detail in your head, and hunting for a quote in audio takes too long.

Text lets you search words, highlight phrases and paste quotes into a team presentation. That saves hours before every sprint. ⏱️

What to do with the output

An automatic breakdown is a draft, not a verdict. Read the text yourself and mark what feels important. Compare interviews with each other: motives that repeat are almost always worth attention.

Then turn your findings into product hypotheses: what to change in onboarding, which promise to put on the first screen, what users fear. 📝

A word on privacy

Interviews often contain names, company titles and internal details. Before you upload a recording, get the participant's consent and trim what is unnecessary. For a confidential project, check with your team whether such material may go to an outside service. 🔒