Set the context and ask permission
Explain that you are learning about a workflow and how people handle it today. Ask if it is a convenient time and whether you may take notes. If you want to record the conversation, obtain permission first. Invite them to skip anything confidential.
Keep the opening specific: ‘I'm learning how independent contractors prepare a quote after a site visit. Could you walk me through a recent example?’ This gives someone enough context without suggesting that the process must be broken.
Reconstruct a recent event
Let the person narrate the sequence before you ask for evaluations. Follow up on concrete details. If the answer becomes hypothetical, return to the last time the task happened.
- What started the task?
- What did you do first, and what happened next?
- Which tools or documents did you use?
- Where did you have to wait, redo work, or ask someone else?
- How did you know the task was finished?
Understand consequences and alternatives
A difficult step does not automatically justify a product. Find out how often it occurs and whether the person has already tried to improve it. Treat the existing workaround as competition, even if it is just a shared spreadsheet.
- How often did this happen in the last month?
- What happens if you leave it undone?
- What have you tried to make it easier?
- What worked well enough that you kept it?
- Why did you stop using an alternative?
Learn how a change would happen
The person experiencing the problem may not choose the tools or control the budget. Ask how their team adopted a previous tool, who reviewed it, and what had to be connected or approved.
Avoid collecting private contract details. You usually need the decision process and constraints, not an exact internal budget. Ask what would prevent a trial, including setup time, data access, training, or switching costs.
Copy this worksheet into your notes
Use a separate record for each conversation. Replace identifying details with a role or pseudonym unless you have a reason and permission to retain them.
- Date and role:
- Recent event and trigger:
- Steps and tools used:
- Hardest step, in their words:
- Frequency and consequence:
- Current workaround and alternatives tried:
- Who chooses or pays for tools:
- Constraints on a trial:
- Observed evidence versus interpretation:
- Next question or experiment:
Look for a pattern without erasing disagreement
Compare the trigger, workaround, and consequence across interviews. Record examples that contradict your idea. A sample from friends or one community may not represent the audience you hope to serve.
When you find a pattern, choose a small next test that delivers an inspectable result. If you share a problem on WorthBuilding, summarize the workflow without publishing a customer's private details. Votes and comments can point to follow-up conversations, while actual use and buying decisions require separate evidence.
Explore problems to investigate
- Small business software ideas
- Productivity app ideas & everyday friction
- Education app ideas & learning problems
