Changelog

You can now customize your organization with your own logo. It’ll show in the top left, next to the app switcher. Simply drag and drop to set it up.

Here’s how:

More updates soon!

We’ve recently released Focus Mode and Feature Views. Today, we’ve fully integrated the two which enables you to set up Focus Slack reports per Feature View!

As your account grows on Bucket, having all features in the same place gets messy. Therefore, you want to use Views to group and organize features by product team or product area.

With today’s release, you can enable a Focus report per each View. This means that “Team Mobile” can get a dedicated report of their features to “#product-mobile” and “Team Payments” can get their weekly report to “#core-payments”. And so on.

Focus and Views works out of the box but is designed to be flexible enough to fit any organization as it scales. Once you have multiple Views on Bucket, you may want to disable the Focus report on the “All”-view, so you don’t receive duplicate feature reports.

Happy shipping!

‍

Large accounts quickly track a lot of features, which means a growing need to get those features organized. A common way to group features is by product team or by product area.

To support this, we’ve just released Feature Views!

Feature views are highly flexible, so they fit any organization. For example, you can create a view for all features that are owned by “Team Mobile”, or a view for all features related to “Payments”. You can navigate views from the updated sidebar.

Whenever you track a new feature on Bucket, you can choose an view for it.

Here’s what it looks like:

More updates soon!

‍

We’ve just updated our UI with a brand new sidebar, and a bunch of general UI polish to ensure the app stays clean and keeps focus on the content.

In the updated sidebar, you’ll now see the app selector at the very top. We’ve also moved the “Track feature” button to the sidebar. This frees up space in the top right of the screen which is a location we’ll generally use for actions related to the current view. 

We’ve also streamlined common UI components like buttons and inputs for better consistency, and improved focus/keyboard navigation. Oh, and dark mode is now a bit more easy on the eyes.

Here’s what the updated UI looks like:

Besides the facelift, the updated sidebar unlocks some great features in the pipeline… 👀

More updates soon!

We’re delivering engagement metrics for any feature with Bucket’s turn-key feature report. It empowers product teams to quickly learn, if their feature is done or needs another iteration.

Having feature-scoped analytics at your fingertip is a major step in the right direction compared to the status quo. However, the problem with dashboards is this: They’re only useful when you look at them.

We believe that product teams need feature metrics to be pushed into their existing workflow for them to be used sufficiently and repeatedly.

Today, we’re releasing the first of several workflow features that’s designed to embed Bucket’s feature metrics into the existing workflow of modern product teams.

But first, let’s quickly unpack the problem.

Short feature attention span

Nowadays, product teams are really efficient in designing, building and delivering features. Once the feature has been deployed, the team (rightly) celebrates, and soon after moves on to the next backlog item. That’s the problem.

The existing feature development toolkit has improved dramatically in the past decade. As an industry, we now have streamlined, powerful tools that help us “ship faster”. It’s terrific for releasing features that work technically.

However, once the feature is deployed and is with the customers - which objectively is the most important part of the cycle - our existing tools takes us no further and we drop our attention at the most crucial time. It’s pretty nuts, really!

Introducing Focus Mode

Focus Mode enables product teams to keep an eye on the features that need attention the most - often newly released features - by pinning those in the UI and reporting their metrics to Slack.

Here's what it looks like:

Once a feature goes into Focus, it’s pinned at the top of the redesigned list view.

More importantly, it’s also featured in the new Focus report that’s sent to Slack every Monday morning.

The purpose of the report is to enable teams to easily skim live engagement metrics for newly-released features at least once a week. With this data, product teams can follow the “health” of a feature as it goes into production to the customers.

We believe such a workflow is transformative for any product and engineering team in terms of prioritizing backlog items vs live features that aren’t doing very well.

Rinse and repeat

How long should features stay in Focus, you might ask. In short, until the team can decide on one of the following three outcomes:

• Validated
• Needs new iteration
• Remove it

Most features will take at least a month to evaluate: Customers need to become aware of the feature, try it, become active users of it and hopefully stay retained over time.

Once the product team has sufficient data from the Bucket reports, and potentially customer feedback, too, they can make a decision on the feature and take it out of Focus.

Then, rinse and repeat with the next feature release.

Happy shipping!

‍

If your feature has an onboarding funnel, you can now filter on event attributes when creating funnel steps. This enables you to track the funnel sliced by a certain attribute value - like browser, feature version or any other custom attribute - or to use just one event for all the funnel steps.

In the example below, the funnel onboarding steps use an event called `messaging_setup` which then has an attribute called `funnelStep: [1,2,3…]` for each step of the funnel.

More updates soon!

You can now sort companies by when they first or last used a feature. When shipping a new feature, this view enables you to easily track its new adopters. Who are they and how often do they use the new feature after the first try.

On the “Stopped” tab, you can track which adopters that ended up churning away. Those are likely the companies you want to reach out to for feedback in order to learn how to improve the feature in its next iteration.

We use this feature ourselves whenever we ship a new feature, like this one ;)

More updates soon!

We’ve spent the past weeks making significant improvements to load times in Bucket. The application was getting pretty slow for accounts with a large number of end-users (~20K+) that also tracked a large number of features. In particular, the list of features could take a loong time to load. Sorry!

To address this, we’ve enabled caching on most queries. Once you’ve visited a page, Bucket will cache it and make sure the data is fresh and loading fast going forward.

Here’s a visualization of the load time improvement for a very large account - from 10+ seconds to 1-2 seconds:

Speaking of larger accounts, we’ve also shipped better formatting of large numbers.. Instead of seeing e.g. “19542 companies” you’ll now see “19K companies”in the UI.

More updates soon 👋

‍

When creating a feature in Bucket it's now possible to specify that only events with attributes which fulfill certain criteria be included in the feature report. This makes it even easier to start tracking advanced features in Bucket!

Imagine having built a chat application and introducing the possibility of sending emojis in messages. You might be tracking whenever anyone sends a message by generating a “Sent message” event and when the message contains emojis you set the “hasEmoji” attribute on those events. Or you want to track how many companies have made a real group chat that wasn’t just a 1 on 1 chat by selecting the “Started Group Chat” event, but only selecting those events where there were more than two members in the group.

Happy shipping!

‍

Last week we shipped the ability to create a feature onboarding funnel which tracks the steps people go through before moving into the “Tried it” state.

In Bucket you can track features based on events that your users trigger but you can also track feature usage through attributes set on companies. Imagine having built a Slack integration for your application. It’s convenient to track who has set up the integration using an attribute "has_slack_enabled=true" which you set on the account.

However, enabling the slack integration is a multi-step process. Users must authenticate with Slack, decide which kind of updates they want to receive in Slack, pick a Slack channel to receive the updates, etc.. Finally when the user has gone through the setup process, your application will update the attribute on their account to indicate the Slack integration is now enabled for this account. 

This week we extended the functionality we shipped last week to work for features that track feature-usage using attributes - in addition to features that use events to track usage.

The way it works is that to be counted in the last step of the funnel, a company must have performed all the previous steps in order and then the company attributes must be updated to fulfill the Adoption criteria as it’s defined for the given feature. In the case of our example, the company must have first sent the “Authenticated” event, then the “Channel selected” event and then finally the company attributes must have been updated such that "has_slack_enabled=true".

Happy shipping!