A value proposition from customer interviews: job, outcome and proof
Build a value proposition from customer interviews by connecting a segment and situation to the job, desired outcome, obstacle and proof. Includes an example and template.
Value depends on the situation
“We save time and improve efficiency” fits almost any service, so it gives customers little reason to choose. Interviews yield more specific language: what they need to produce, by when, which error to avoid and what a good result looks like.
A value proposition is a messaging hypothesis. Even if the words come from interviews, check whether they’re clear and whether the product delivers what they describe. Avoid promising automatic results that depend on recording quality, human review or further work.
Connect the job, obstacle and proof
Choose one segment and moment
Name the role and situation in which the customer chooses. The same person may care about different outcomes when preparing minutes, writing an article or making subtitles.
Collect words that describe the job
Find the verbs and criteria in people’s accounts: what they need to do, why it matters now and what happens without a solution. Don’t quote a striking line out of context.
State the result and its limits
Promise what the product actually helps achieve. Explain any review or manual step that affects quality.
Give customers a reason to believe
Show how the process works, state a clear condition, give an example result or point to a verifiable capability. Don’t invent percentages or claim superiority without data.
What matters to someone producing a long interview
This is a fictional training example. The names, circumstances and outcomes are included solely to explain the method.
I don’t need a polished recap. I want to find the guest’s exact answers quickly and go back to the recording if a line seems questionable.
The important outcome is finding a specific answer and being able to check it against the source. Mention structure, search and timestamps if the product supports them in this workflow.
Training example: “Turn your interview recording into a working transcript with timestamps so you can find answers faster and check uncertain passages against the source.” It doesn’t promise perfect accuracy. The example is fictional.
| Part | What the interview tells us | Messaging |
|---|---|---|
| Segment | Producer of a long interview | For people who produce interviews |
| Job | Find an exact answer | Find answers faster |
| Criterion | Return to the source | Check against the timestamp |
| Limit | Review uncertain passages | Avoid promising perfect accuracy |
Value proposition worksheet
Create a separate version for each situation you understand well.
Segment and context: What triggers the job: What the person is trying to do: Main obstacle: Desired outcome: What a good outcome looks like: Current alternative: Customer language — quotes and timestamps: What the product actually does: Human review required: Reason to believe: Short value proposition: What we’ll test:
Check that the promise is accurate and clear
- The segment and situation are specific.
- The outcome matters to the customer.
- The reason to believe can be demonstrated or verified.
- Accuracy or success is only promised under stated conditions.
A closer look
Should we repeat the customer’s exact words?
You can adapt the wording to the format while keeping the meaning and natural language. Mark direct quotes and never combine multiple people’s words into one quote.
How many value propositions do we need?
Separate hypotheses are usually useful for different segments and situations. An overall slogan can sit alongside specific messages on pages and in sales conversations.