No one knows our products better than you, our users. We love hearing about how you use our tools and what would make them better.
This topic is to provide some guidance for product feedback about the Nx Witness Software Suite. Don't worry, if your post should be in another topic, the Nx Support Team has your back and will move your post to the correct topic.
Here are a few guidelines on how we see and how you can use the Feature Feedback section.
We receive a quite a few of feature feedback posts every month, so there's a good chance someone has already made a suggestion similar to yours. Keeping conversations in existing threads makes them easier for others to find, and helps keep the Community organized. Also, it gives our team a better impression of the demand for such feature request or improvement.
Give details, examples, and tell us about the problem you’re trying to solve
The most helpful Product Feedback posts are the ones that describe the nature and scope of a problem. Try to share the following information in your post or comment:
- Feature Request Summary
- Use Case
- Product limitation or missing feature
- Business impact of limitation or missing feature
- Other necessary information or resources
Here is a template for feature requests that you can copy and paste and then just fill in your details.
It's much easier for us to address a suggestion if we clearly understand the context of the issue, the problem, and why it matters to you.
We will read your post, but we may not respond
Our team dedicate time each week in the community to read your comments, answer your questions, ask you questions about your feedback, and lead conversations around areas they’re focused on.
That said, we simply can't respond to everything. Remember what we said about a plethora of requests per month in this community, but also coming in through various channels from our sales team, our authorized resellers, technology partners, etc.? There just aren’t enough hours in the day!
Network Optix team members may engage in conversations, ask follow-up questions, or even start threads on topics they’re exploring. If your post or comment doesn’t receive a response, don’t worry. We’ve seen it, and we’ll let you know if and when we have any updates to share.
Posts are not guaranteed a response, or inclusion in any product backlogs or roadmaps. This forum is simply for sharing your challenges and how you use the product, but it is not a case/resolution system.
Vote for suggestions you like
Votes do matter! See a post or comment you like or agree with? Use that up arrow! Feel like making a post that just says "+1"? Please use the upvote button instead. Post a comment to share your detailed use case. Comments are very important for us to understand the benefits of the feature request.
That being said, votes are only one metric that is taken into consideration, but the request still might not be included in a future release for various reasons; like capacity of resources, the impact on the source code, a conflict with our mission and vision of how our software should work, and we might have other priorities due to growth in certain customer segments that require other features, etc.
We don’t share timelines
Occasionally, we’ll share very general ideas of what is or isn’t on a roadmap, or roughly when you might expect to see something roll out. However, we do not share specific dates or versions. Any timelines we share are not guaranteed and are subject to change without notice.
There are situations where we aren't ready to share what we're up to, or it's not reasonable for us to give specifics. While we are as up front as we can be, our roadmap is full of projects, and we generally don’t provide timelines for new features or changes. If we do provide a timeline or a version number, know that it is subject to change, and the feature might be postponed for a future version.
Now we mentioned the roadmap., we made a deliberate choice for not having a public roadmap, since in the past it has the potential to lead to disappointment.
Features might end up in the roadmap, but along the way, might also be postponed due to various reasons, and we don’t want people to wait for certain feature or even makes promises based on a roadmap. With a public roadmap it is inevitable misunderstandings will occur and which lead to constant and exhausting conversations no one benefits of.
We think it is better to not share anything at all than to disappoint someone.
Each new release is a package with plentiful new features and improvement of what we think benefits the majority of our users. And yes, there are very useful feature requests we really would like to deliver, but sometimes we just simply can’t.
We have 4 different tags we can assign to each topic, None, Answered, Completed, and Not Planned.
None - Suggestions that are untagged mean that we have not yet decided on a course of action, typically because we want to hear more feedback from other customers.
Answered - Suggestions that are tagged as Answered are reviewed by our team, and added to the backlog.
Completed - Suggestions that are tagged as Completed, are currently available in our software.
- Not Planned - Suggestions that are tagged as Not Planned were reviewed by our team, and didn’t make it yet to the backlog. That being said, now and then, these Not Planned suggestions are reviewed again by our team and be taken into consideration while we are working on related features.
Post maintenance and archiving
Requests that have been inactive, (have not received a new comment) will be archived. These are retained internally and remain visible to product managers. This helps to keep the community navigable and helps us prioritize the requests that are most important to the largest number of users.
This doesn't mean your idea was bad, or that it will never happen. It just means that it wasn't something that came up for a lot of users. Since we keep records, if the idea pops up again, we’ll aggregate those ideas behind the scenes and know when something keeps coming up.
This also means that if there's an idea you like, be sure to stay active in that conversation!
Thank you for reading this and for understanding how we address suggestions. We value all feedback, and we're happy to have a place to engage in these conversations.
Please follow the Community Code of Conduct
Feedback and constructive criticism are welcome. We’re all professionals, so let’s keep it polite and friendly. Comments that are unhelpful to the conversation may be removed without warning. You're allowed to express frustration or dissatisfaction, just remember there are real people on the other side of the screen. Your boss and your neighbor can see these comments if they search your name. So keep it civil and professional.
You can read our code of conduct HERE.
Post is closed for comments.