Interview strategy
Choose discovery, problem validation, solution validation, pricing, churn, or positioning before writing questions.
Tool task
User Interview Guide Generator
Go beyond a generic question list. Create a decision-oriented interview playbook: who to recruit, what to ask, what to listen for, and which answers count as strong evidence.
Generate a reviewable user interview guide
Enter your product context, research goal, and target participants. Tomako uses an Agent to produce a structured guide with missing information, assumptions, and human review checks.
What you get
Participant criteria
Turn 'talk to users' into concrete screener criteria that prioritize people with recent real behavior.
Questions, purpose, and probes
Each question explains why it exists, what to listen for, how to probe, and which leading behavior to avoid.
Evidence signals and review checks
Separate strong signals, weak feedback, risks, missing information, and post-interview handoff actions.
Best-fit use cases
- You need to validate whether a pain is real and strong before building a feature or MVP.
- You want interviews to serve a product decision instead of collecting loose opinions.
- You already have a prototype, demo, or page and need to learn when users would actually use it.
- You need a guide that another teammate can run with clear flow, probes, and evidence signals.
What this does not replace
- It does not replace real interviews, behavior data, conversion tests, or paid experiments.
- It cannot decide that a product is worth building from one vague idea.
- It is not suitable for medical, legal, financial, or other regulated research without professional review.
- If the input is test text, numbers, or vague filler, the page blocks it or marks missing context.
Failure and recovery
- If task submission fails, the page keeps your input so you can add context and retry.
- If the Agent does not write back a structured result, the page shows the task id for Skills-OL debugging.
- If the result type or schema does not match, the page will not display a fake success state.
- The generated guide still needs human review for sensitive questions, recruit scope, and leading phrasing.
How to use the result
- First check whether the research objective maps to a near-term product decision.
- Use the participant criteria as a screener and filter out people without recent real experience.
- During the interview, probe concrete behavior before explaining the solution.
- After the interview, send the transcript to the record generator, then synthesize multiple records into insights.
Why use Tomako here
Built around decisions, not documents
The result ties questions, probes, signals, and handoff actions back to the product decision you need to make.
Clear failure boundaries
The page exposes missing information and review checks, and it does not pass off a local template as an Agent result.
Connects to the research workflow
The same interview output can feed structured notes and multi-interview insight reports.
Useful for small teams
Indie builders, PMs, and founders can get an executable draft, then calibrate it with one or two pilot interviews.
Quality standard for this tool
- When input is thin, the tool should expose the gap instead of generating confident filler.
- The output should support recruiting, interviewing, note-taking, and review, not just advice.
- Every question should have a purpose, probes, and an anti-leading reminder.
- The result must be copyable, reviewable, handoff-ready, and tied to a task id for debugging.
FAQ
Will this tell me whether the product is worth building?
No. It designs interviews that produce better evidence. The build decision still needs transcripts, behavior data, competition, technical cost, and real conversion tests.
Can I ask whether users would pay?
Yes, but do not rely on stated intent alone. Past spending, current workaround, cost of the problem, and willingness to enter a next-step test matter more.
Can I interview users without a prototype?
Yes. Without a prototype, discovery or problem validation is usually stronger. Reconstruct recent behavior before testing solution reactions.
Why does the generated guide still need review?
Interviews affect recruiting, privacy, sensitive questions, and product judgment. Tomako drafts a structured guide, but your team still needs to check fit and compliance.
After the interview, turn the transcript into a structured record, then synthesize multiple records into insights.