Feature launch dashboard example

Photo of Helena Pilih, Product Manager at Geckoboard
Helena Pilih

Product Manager

* Contains sample data

What’s this dashboard for?

When several teams are involved in one project, it’s sometimes difficult to share crucial data efficiently if it comes from multiple sources. One way to solve this is by displaying key data on a real-time TV dashboard that everyone can easily see and understand.

Through this, you can make teams aware of critical developments after you’ve rolled out your feature. And this will help them identify problems and take action early on.

We have two data sources for our feature launch dashboard: our own internal database, and Mixpanel.

All payment-related data comes from our internal database. To separate this from our feature-usage data, we’ve split the dashboard in two. The left-hand side displays payment-related data, while the right-hand side focuses on feature-usage data. Splitting the dashboard helps us distinguish the overall success metrics – which take more than 30 days to assess – from real-time data that tells us how the feature is performing right now.

Our payment-related area has three metrics. The first two are success metrics – metrics that are tied to a goal – and the third is an overall metric:

  • Percentage of trialists who added a database widget and converted to a customer
  • Percentage of trialists who connected a database and converted to a customer
  • Number of customers who’ve added a database widget in the past 90 days

Meanwhile, on the right-hand side, our feature-usage area has two metrics. The first metric gives us a detailed understanding of users’ behavior when they use the new feature, from first touchpoint to final setup. And this helps us spot, early on, any problems in the user journey.

The second feature-usage metric shows how many users recovered from a database connection-failure. Through this, we’ve exposed the most vulnerable part of the feature-usage funnel so we can spot any problems and react to them immediately.

As a product manager, I’m constantly looking at key user flows in the product. But other people, like Engineering and Customer Support, don’t see this information. And that’s why I built this dashboard. I wanted to share the most important metrics for our new database integration launch, to ensure a successful roll-out.

The TV dashboard is displayed in a prominent place in the office, so it’s always visible to the product team. They have access to relevant data whenever they need it. And I can focus on what’s important because I don’t have to send out emails and data reports.

At first, we had a metric on our dashboard that showed the rate of users who had a failed database query but were eventually able to execute it.

This was another crucial part of the funnel, so we wanted to be aware of any problems here. Engineering had worked hard on building smarter error messaging for this feature compared with previous ones. And I wanted the team to see their hard work paying off.

But, over the first few weeks we saw that this part of the funnel was doing well enough, so we didn't need to monitor the metric any more.

You only want metrics on your feature launch dashboard that will help you improve the user’s journey.

  • Gives an instant overview of the success of a feature launch, by displaying real-time feature-usage data
  • Helps you anticipate feature launch problems before they occur
  • Communicates key data to people in different departments

See more