👋🏻 Introduction
❓ How was your overall experience with the [new feature]?
❓ How satisfied are you with the [new feature]?
Numerical Scale
❓ Please elaborate more on why.
❓ How often would you use this [new feature]?
Single Select
❓ What changes would make the [new feature] better?
👋🏻 Thank you
User satisfaction

Gauge users’ first impressions on new features

Recently shipped a new feature? Run quick surveys to gauge users’ first impressions and initial reactions to understand how users feel about it.

Study objectives

  • You already have a sense of how valuable the new feature is to your target users. Now that you’ve built it and delivered it, gauge how users are engaging with the feature.
  • Collect direct, contextual feedback on a newly released feature to gauge user satisfaction.
  • Collect users’ opinions and recommendations to provide context for product usage metrics and quantitative results.
  • Monitor usage and satisfaction after release and make incremental improvements.

Launching a new feature? Get feedback with in-product surveys

Target users after interacting with the new feature to collect contextual feedback

Best practices for running in-product surveys for a new feature

  • Ask open-ended questions: Include open-ended questions to encourage users to provide detailed feedback and insights into their experiences with the new feature.

  • Use rating scales: Incorporate rating scales or Likert scales to quantitatively measure user satisfaction or perceived usefulness of the feature.
  • Time surveys appropriately: Schedule surveys to appear at relevant points during the user journey, such as after completing a transaction related to the new feature or during specific interaction points.

  • Monitor Trends Over Time: Continuously track user feedback trends over time to gauge the impact of any changes or updates made to the feature and ensure ongoing improvement.

  • Integrate with analytics: Combine survey data with quantitative analytics data to gain a comprehensive understanding of user behavior and sentiment regarding the new feature.

Getting started


Create an account and log in to your Hubble account.


Find and select the template to use.


Edit the questions 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

What is an in-product survey, and how does it differ from traditional survey methods?

Hubble’s in-product survey is embedded directly within the product or application, allowing users to provide feedback while using the product. It differs from other survey methods in that it captures feedback in real-time, as users interact with the features or functionalities being evaluated.

Why use in-product surveys to monitor new feature releases?

In-product surveys offer several benefits for monitoring new feature releases, including the ability to capture feedback at the point of interaction, gather insights from actual user experiences, and identify issues or areas for improvement quickly. They also enable targeted feedback collection from users who are actively using the new features.

When should in-product surveys be deployed to monitor new feature releases?

In-product surveys should ideally be deployed shortly after the release of a new feature to capture initial user impressions and feedback. They can also be scheduled to run periodically to monitor user sentiment over time and track any changes or improvements in user satisfaction or usage patterns.

What types of questions can be included in an in-product survey for monitoring new feature releases?

In-product surveys for monitoring new feature releases can include a variety of questions, such as asking users to rate the usefulness or ease of use of the new feature, provide suggestions for improvement, identify any issues or bugs encountered, and share their overall satisfaction with the feature.

Other Study Templates

Measure NPS to assess user satisfaction and loyalty

Follow-up with users with their onboarding experience

Gauge users' overall satisfaction and areas of improvements

Related Blog Posts

Launching a new feature? Get feedback with in-product surveys

Target users after interacting with the new feature to collect contextual feedback