Comments on: Releasing a New Feature? Don’t Forget to Do This.

By: Thomas Qvist Krüger

Thomas Qvist Krüger — Thu, 26 Jan 2017 08:16:34 +0000

I know this is a not a new blog post, but it is just so simple. At http://productionhero.co we use this startup hack because of the simplicity. We have easily integrated in to our roadmap on trello. Thank for the tip!

By: Jens Gössing

Jens Gössing — Wed, 16 Nov 2016 14:30:28 +0000

Hey Len,
for us it is important to have the people participating in the decision about new features to be implemented in addition to what you describe. Are you doing this at all. Can you suggest any addon to the described to best involve the people based on voting? By the way, it would be awsome if you would simply add a feature request section and voting to the groove knowledge base 😉

By: Petr Pinkas

Petr Pinkas — Wed, 04 Nov 2015 07:33:19 +0000

Looking good, great idea to use Trello on this. We usually use our bugtracking system, works too, but a little bit different. I mean, new features always are in forms of bug tickets which needs to be resolved. Thanks for sharing your workflow Len.

By: Joe Pour

Joe Pour — Tue, 03 Nov 2015 21:47:47 +0000

Hey Len, nice post.

One thing to note with this method is that you need to be careful of the expectation you are setting. Just because a customer has asked for a feature and it got added to the product, doesn’t mean that everything they ask for in the future will be done.

Another thing I do is save all the emails from other internal departments when they request features (whether it be on behalf of a customer they have spoken to or for themselves). This way when a feature goes live, I shall reply to that email with a note mentioning that it is in production – goes a long way and makes them feel like the product team is listening 🙂

By: Brady Dowling

Brady Dowling — Tue, 03 Nov 2015 21:24:19 +0000

Good post, been thinking of what route we want to really push forward on when we announce our features and this is a good thing to keep in mind.

By: Dan Dukeson

Dan Dukeson — Tue, 03 Nov 2015 15:48:29 +0000

Hey Len good post, its super important to get back to the people that asked for the feature so that they know you 1) were listening and 2) acted upon their feedback. Trello is a good first step to remembering who to talk to about a feature, but I didn’t like the manual step involved. Its too easy to forget, or get the I always used to search back in my gmail for customers that had mentioned it (and hope I’d thought of all the different ways to describe a feature). This was a major part in what drove us to build our startup Receptive https://receptive.io to manage feature requests from customers and work out what to build next.

By: Yakov Karda

Yakov Karda — Tue, 03 Nov 2015 15:38:50 +0000

You have some serious mind-reading abilities. Len. You know what, I was just reading our own Chatra.io feature release announcement (we made an intelligent pre-chat form that that visitors love to fill with their contact information) when your e-mail arrived. What I’ll be doing now is going through the past records to find the customers who requested just that :—) Thank you!