Choose from 15 guided interview techniques based on the saved map.
Why this exists
Many teams cannot answer a blank-sheet pain interview cleanly. Operators may normalize the friction, avoid naming sensitive problems, or jump straight to solutions. Pain Discovery Studio gives a facilitator a more structured way to surface what hurts and why it matters.
How the studio works
- Start from a saved company model so the session inherits known workflows, owners, constraints, accounts, and obligations.
- Accept or trim the recommended set of 15 guided interview techniques.
- Suggest possible problems from saved processes. Start with workflows that have not been discussed, then look for nearby friction even where one problem is already recorded.
- Validate one target by naming the owner, evidence request, baseline, and stop condition.
- Add only reviewed problems to the company evidence so they can affect the opportunity ranking.
What makes it different from a notes doc
The studio labels suggestions separately from facts, connects each interview question to the company map, and asks for the least-sensitive evidence needed to validate a claim. A session can be exported as Markdown, and reviewed problems return to the same evidence used by the roadmap.
Where it fits in the workflow
Use Pain Discovery Studio after a model has enough substance to suggest workflows, but before a sponsor expects a ranked roadmap. It is the bridge between partial evidence and better pain proof, especially in advisor-led workshops and cross-functional discovery sessions.