makwarth

Cheers!

Got it, makes sense. Appreciate the concrete example! As for the event tracking data, do you use a tracking plan, like Segment Protocols?

True ;) Sometimes, though, a new feature isn't getting engagement because people are busy. Product and Product marketing can use low engagement metrics to raise awareness.

Good point! Talking to some of the users of the feature you're about to remove is probably a good first step. Do those users use the feature in a way that's aligned with your product strategy?

How do you track that exactly? Any chance you can share a concrete example?

Hi, I’m the solo founder of Bucket. I’ve built this tool to easily measure the success of software features. Out of the box, Bucket will tell you how many users are engaging with your feature, and how often (daily, weekly, monthly). That’s it! It’s simple but enough to be actionable.

I’ve needed something like this in previous SaaS companies. For whatever reason, traditional product analytics platforms were never adopted outside of a small group of product managers. Bucket is analytics for the individual features.

I hope that software teams (engineers, designers, product, etc.) will consider using this. Sometimes we need to ship less new features and iterate on existing ones. Maybe even delete some features once in a while! :)

Feedback very welcome!