We feel really lucky here at New Relic because we get to work with some of the smartest and most creative technical people on the planet: you! Every day you use the community to ask tough questions and support one another. Best of all for us, you give us great ideas for the future direction of New Relic products.
Today, we're rolling out a new way to discuss those great product ideas you have: the Feature Ideas category. What's it all about?
How it works
Sometimes you bring ideas to the community that you KNOW don't exist as you envision them in our products yet. We're asking you to put those right into the new Feature Ideas category. We've got Sub-categories for every product as well. Other times, you bring a technical question that we realize can only be addressed by a feature that does not yet exist. The community moderators will help move those posts into the proper Feature Ideas sub-category.
Regardless of how a topic is started, our community moderators will ensure that every Feature Idea contains the following:
- A description of the problem that needs to be addressed
- A possible solution for the problem (what is the feature you envision, and how should it work?)
- A list of existing workarounds
- A poll that allows other Community members to weigh in and say "I want this, too!"
- A prompt for comments with additional use use cases/more clarification from poll answers
What's in a name?
For those of you who have been in the community for a long time, you know that we usually tagged posts like these with the "feature-request" tag. We've changed the language here to "Ideas" for a very specific reason - we want to be very clear that these are incredibly helpful discussions for our product teams, but that we can't deliver on every "request."
The simple truth is that New Relic can not make promises about our roadmap. You all know that a thousand unforeseen circumstances can delay or interrupt a software project. In any software development environment, there are a thousand twists and turns encountered every day. What "looks" like a simple feature request may turn out to have much larger implications, so we just can't give you the promise that any request will turn into reality.
We hope that our discussions around feature "Ideas" will help keep us all focused on what we CAN do - provide our product team with the best thinking about what future features might look like. I have discussions with the product teams every day. They are looking to the Community for ideas and read all of your comments. We're hoping this new process makes that even more productive.
Aligning with our values
We also think this change creates a process and a dynamic that is more representative of New Relic's values:
Bold: We take risks to deliver ground-breaking innovation. We are courageous. We love to try new things and experiment here at New Relic, and that next big experiment could come from this community. And this new category is a big bold shake up for us! We will see how it goes and learn as it happens.
Authentic: We are genuine, honest, and inclusive. We can be ourselves at work. We will work hard to ensure that anyone who wants to participate in the discussion of that idea can.
Accountable: We take pride in what we do and hold ourselves to high standards. We deliver on our commitments. This new category should help reset expectations about what a Feature Idea is, and we can be very clear about what will or will not come out of the conversation.
Passionate: We are inspired by, and seek to inspire, our customers. We strive to make a difference. The new category makes it much easier for ur product team to see the amount of interest in and the discussion around their products. They will have a much easier time hearing your voices and being inspired by what they hear.
Connected: We build trusted, personal connections with each other. We are a team. We also hope that this shift leads to much more meaningful conversation around ideas. Our old process presented a static idea with a small chorus of "me too" or "is this going to get implemented?" We want you to share more ideas and have more discussions with our product team members - side by side.
We should point out that we did not come up with this new process in a vacuum. We created a topic with a poll and solicited your feedback before transitioning the topic to an internal category and soliciting feedback from our support and product teams. The truth is that both the Community and the Relics were split 50/50. Half of you wanted to see this new category and half did not.
What everyone agreed on is that they wanted to see more direct communication about what happens with a feature request and more conversation about how we can solve customer problems. We think this is our best shot at that, but we'll be watching and learning as we go, so expect course corrections.
Most importantly, if you have a concern, comment, or idea, @Linds and I (@hross) want to hear from you! So please reply to this topic or feel free to message us directly.
Thanks so much for making this community so special!