Your feedback is essential to the continued evolution of the Incident IQ platform. The Idea Exchange is where your unique challenges turn into shared solutions. By sharing your ideas and use cases, you help us focus our development resources on the features that will make the biggest impact on your daily workflows.
Don't just post—participate! Voting on peers' suggestions and sharing your specific use cases are the most effective ways to demonstrate community interest and ensure our team understands the community's needs.
Please note that all ideas are thoroughly reviewed; however, submission does not guarantee implementation.
Submission Best Practices
1. Search First
Check whether your idea has already been submitted. If it is, add your vote and a comment with your specific use case to keep the momentum on one thread.
- Why: This prevents duplicate entries and concentrates votes and use cases on a single, existing thread. If an idea already exists, please up-vote it rather than creating a new one.
2. Provide Detailed Descriptions
The more context, the better. Explain the "why" behind your request so others can rally behind it. Include relevant use cases or concrete examples to help illustrate the value.
- Tip: A screenshot is worth a million words and helps our team and other users visualize your enhancement request.
3. One Topic, One Post
Keep your submissions focused. Single-idea submissions are easier for others to digest and for our team to track and implement.
- Why: When ideas are grouped together, it can be challenging to identify which specific features are in demand. This increases the likelihood of confusion regarding the requests being made. Additionally, if multiple similar ideas are not developed simultaneously, it allows our team to focus on and complete individual ideas more effectively.
Our Review Process
Every idea starts with a "New" status. We evaluate each submission to understand its request and often reach out to you for more details. Once assessed, we update the status so you can track your idea's journey.
While community engagement—such as vote counts, comments, and the request's age—provides valuable insight and helps us gauge interest, it is one of many factors we consider. Our product team conducts a thorough assessment of each request against key criteria to ensure alignment with our platform’s long-term goals and stability, including:
- Strategic Alignment
- Technical Feasibility & Resources
- Customer Experience & Friction Reduction
- Platform Stability & Maintenance
Track the Journey: Status Definitions
Did the status of your idea recently change? Learn more about our Ideation Statuses below!
- New - Recently submitted and pending initial review.
- Open - Verified as a unique suggestion and now open for community discussion and voting.
- Under Review - Currently being assessed by the Product Team for potential development.
- Candidate - Validated and identified as a candidate for future development.
- Committed - Approved and scheduled for a future release.
- In Development - Currently being actively built by our team.
- Completed (Live) - Fully implemented and now available for use.
- Duplicate - A duplicate of an existing idea; will be merged with the original submission.
- Not in Vision - Assessed and determined to be outside our current product vision.
- Needs Information - Further details are required from the requester before assessment can proceed.
- Already Exists - The suggested feature is already available in the current product version.
