The Discovery Space in Vistaly is where product teams explore customer needs, generate solution ideas, and validate assumptions with testing.
Pro Tip 💡**:** Insight count will only display when is enabled in card settings
Sizing Criterion | Description |
---|---|
Frequency | How often do customers experience this pain/need? |
Reach | How many customers experience this pain/need? |
Severity | How painful will it be to customers if left unaddressed? |
Differentiation | Is it table stakes or a differentiator? |
Pro Tip 💡: Find the right balance with custom fields. Too many can slow down your process, while too few might not provide enough context for decision-making.
Pro Tip 💡: Custom fields will only display when they are enabled in card settings. Some custom fields will only display with data.
Stage | Commitment | Description |
---|---|---|
Identified | No/Unknown commitment | Aware that the Opportunity exists but have made no commitment to solving it. This is how all Opportunities start. |
Not now | No commitment | Recognized as an opportunity but deliberately chosen not to address it at this time, possibly due to resource constraints or competing priorities. |
Later | Committed (Moderate Confidence) | Committed (for now) to solving the Opportunity. Confidence is relatively high that it’s an opportunity worth addressing, but this is subject to change. |
Next | Committed | Committed and will begin work soon to start addressing the opportunity. It may be the case that the opportunity is currently being researched or solutions being identified. |
Now | Committed | Committed and work is actively underway to address it. It’s best if there is an identified solution associated with an opportunity in Now - if not, solutioning should be underway. |
Pro Tip 💡: When you catch yourself proposing a solution as an outcome, ask “Why do we want this?” to uncover the underlying value you want to provide.
Stage | Commitment | Description |
---|---|---|
Idea | No/Unknown commitment | Initial concept for addressing an Opportunity. No commitment to implementation has been made. |
Not now | No commitment | Solution evaluated but intentionally deprioritized due to resource constraints, technical limitations, or strategic considerations. |
Later | Committed (Moderate Confidence) | Planned for a future timeframe beyond the current planning horizon. Recognized as valuable but with lower immediate priority than Now/Next items. |
Next | Committed | Solution approved with implementation details being finalized. Awaiting resource allocation or developer availability. |
Now | Committed | Solution actively under development. Implementation work is in progress. |
Assumption Type | Description |
---|---|
Desirability | Does this solution solve a meaningful problem for users, and will they want it? |
Usability | Will users intuitively understand and successfully use this solution? |
Feasibility | Can this solution be delivered with the current team, resources, and capabilities? |
Viability | Does this solution align with strategic goals and generate measurable business value? |
Assumption Type | Description |
---|---|
Ethical Considerations | Does this solution align with ethical standards and avoid potential harm to users, society, or the environment? |
Scalability | Can this solution grow to meet increasing demand without degrading quality or performance? |
Legal | Are there legal considerations that might impact implementation or adoption? |
Test Type | Description |
---|---|
One Question Survey | A targeted, single-question instrument designed to validate a specific assumption with users. Provides quick, focused feedback on a narrow hypothesis. |
Visual Prototype | Low or medium-fidelity visual representation of a solution to test user reactions and validate assumptions about usability, desirability, or comprehension. |
Research Effort | Structured investigation involving interviews, contextual inquiry, or usability testing to understand user behaviors, needs, and pain points related to an assumption. |
Data Analysis Effort | Examination of existing user data, metrics, or analytics to validate assumptions based on actual behavior patterns rather than stated preferences. |
Painted Door Test | A technique that presents users with an interface element (button, link, etc.) for a non-existent feature to gauge interest before building the actual feature. |
Stage | Commitment | Description |
---|---|---|
Developing | In preparation | Experiment design is being created or refined before execution. Methods and metrics are being established. |
Pending | Ready for execution | Experiment is fully designed and waiting to be run. All prerequisites are in place. |
Running | In progress | Experiment is currently active and collecting data. Results are not yet available. |
Failed | Completed (invalidated) | Experiment has concluded and results indicate the assumption was incorrect or not supported by evidence. |
Passed | Completed (validated) | Experiment has concluded and results support the original assumption, providing validation. |