👋🏻 Introduction
❓ How often do you [a task that your idea is trying to solve]?
Single Select
❓ What is the desired outcome of the task?
❓ How important is it to achieve the desired outcome?
Numerical Scale
❓ Please elaborate on your choice.
✍️ Text describing the idea, and key value propositions
Text Statement
✍️ Text describing pros and cons of the idea
Text Statement
❓ If [idea] is available today, how likely are you to use this tool?
Numerical Scale
❓ Please elaborate on your choice.
❓ how different is this tool to the other solutions or your current workflow?
Numerical Scale
❓ Please elaborate on your choice.
❓ When was the last time this could’ve been helpful/useful to you?
❓ From your perspective, who would be benefiting the most from using this tool? Why?
👋🏻 Thank you

Validate new feature ideas

Assess the viability of your concept early in the ideation phase by articulating its key value propositions. Gather user feedback rooted in context to fine-tune your idea.

Study objectives

  • Dive deep into understanding how your concept idea directly tackles users' real-world challenges, ensuring the idea is viable and relevant.
  • Clearly identify the problems the concept is effectively solving for its users.
  • Craft a refined and tailored approach to your idea through user feedback grounded in specific contexts.

Validate and fine-tune ideas early stage

Get user feedback grounded in context to iterate your idea

What is this template good for?

  • Test your idea with just the idea of conveying value proposition. You don’t have to have anything built out to test it out. This way, you can save resources in case the idea isn’t fit for the users.

  • If you have multiple ideas generated from brainstorm sessions, this is a cost-effective way to test each idea and prioritize.

  • Experiment with your idea early stage by conveying its value proposition only. No need to fully develop it before testing; this approach conserves resources in case the idea doesn't resonate with users.
  • If you've generated multiple ideas through brainstorming, this method offers a cost-effective way to test and prioritize each one accordingly.

Best practices for validating ideas early

  • Involve users early. If you’re already thinking of conducting ideas early on with this template, you’re on the right track because you are including users as early as possible to gather feedback and insights.

  • Invalidating an idea is just as valuable as validating one. While it may be disheartening to discover that your idea doesn't resonate with users, it's important to recognize that disproving an assumption can be equally informative. By doing so, you save resources that might otherwise be wasted.

  • Prototype iteratively and stay agile: Create prototypes of your product ideas and iterate on them based on user feedback. This allows you to quickly test and refine different concepts before committing to a final design.
  • Be open to feedback: Approach user research with an open mind and be receptive to feedback, even if it challenges your assumptions. Use feedback as an opportunity to learn and improve your ideas.
  • Focus on user outcomes: Prioritize understanding the outcomes that users are seeking to achieve with your product rather than just focusing on features or functionalities. This ensures that your product meets real user needs.

Getting started


Create an account and log in to your Hubble account.


Find and select the template to use.


Edit the questions and text prompt as you see fit.


Run pilot tests with internal users (ideally, people that are not a part of your project).


Preview the study and check if you need to make any last minute changes.


Publish the study and wait for the results to come in.

Frequently Asked Questions

Why is it important to validate ideas early in the user research process?

Validating ideas early helps to minimize the risk of investing time and resources into ideas that may not resonate with users. It allows for early feedback and iteration, ultimately leading to the development of more successful products or solutions.

What are some common challenges when validating ideas early on?

Common challenges include limited resources for conducting research while having numerous concepts and ideas that need to be tested. This could eventually lead to time-consuming process to test each one and prioritize. Another common challenge is becoming married to your own ideas, misinterpreting and having a biased study.

How can I ensure that the feedback gathered during early validation is actionable?

To ensure that feedback gathered during early validation is actionable, it's essential to ask specific and targeted questions that are grounded to context. Participants will feel sorry to share negative feedback and often share positive, surface-level comments. Use a diverse sample of users, and prioritize feedback that aligns with the goals and objectives of the research. Additionally, involving stakeholders in the validation process can help ensure that feedback is relevant and actionable.

What should I do if early validation indicates that an idea needs significant changes or may not be viable?

Invalidating an idea is just as valuable as validating one because you’re saving the resources that could have otherwise been wasted. If early validation suggests that an idea needs significant changes or may not be viable, it's important to iterate on the idea based on the feedback received. This may involve refining the concept, adjusting features or functionalities, or exploring alternative solutions based on user insights. Iteration is a natural part of the validation process and can lead to stronger, more successful ideas in the long run.

Other Study Templates

Test your ideas as early as possible with storyboards

Deep dive into understanding users pain points and opportunity areas

Understand users' mental model and how they group information

Related Blog Posts

Validate and fine-tune ideas early stage

Get user feedback grounded in context to iterate your idea