Next DLP Reveal Customer Feature Requests

TABLE OF CONTENTS

• How to raise a feature request for Reveal
• Next DLP Feature Request (FR) process descripton

How to raise a feature request for Reveal

Next customers may submit feature requests for the Reveal Platform via a support ticket. 

When raising the feature request ticket, it is important to provide a descriptive feature name in the Subject and include the following information in the Description:

1. Technical description of the feature being requested

2. At least one use case in the format “As an administrator|operator|security analyst I want (describe feature) in order to (describe real world goal)”

3. Business benefits for new feature

4. Additional information e.g. any specific requirements

After the feature request is raised, Support will provide a Feature Request (FR) reference number and the support ticket will be closed. Status updates or further discussion with the Next DLP Product Management team regarding the feature request would be facilitated by your Customer Success Manager (CSM).

Next DLP Feature Request (FR) process descripton

Once submitted all customer feature requests follow the general process outlined below:

1. Logged and Stored in a Centralised Repository: All feature requests are collected and stored in a centralised repository. This ensures that all customer feature requests are registered and accessible by the entire Next team. 

2. Categorization and Prioritization: Feature requests are categorised based on themes or functionality requested. Prioritisation is based on factors such as the number of requests for a particular feature, potential impact on users, alignment with the product roadmap, strategic importance, or market trends.

3. Evaluation: the Product Management team meets with Customer Success and Support on a weekly basis to discuss feature requests. Features are evaluated for feasibility, technical complexity, resource requirements, potential impact on existing features, and alignment with the company's vision and goals.

4. Communication with Customers: your CSM will keep you informed about the status of your feature requests. Next strives to provide transparency about which requests are being considered, prioritised, or implemented, and explain the reasons behind the decisions. Approved/accepted feature requests are incorporated into the feature backlog.

5. Design and Development: Once a feature is prioritised, it moves into the design and development phase. The Product Management team collaborates with UI/UX designers, software developers, and other stakeholders to plan and execute the implementation of the feature.

6. Testing and Quality Assurance: Thorough testing is conducted to ensure that the new feature meets quality standards, functions as expected, and does not introduce any regressions or compatibility issues with existing functionality.

7. Release and Deployment: Some features may be released in Preview mode to customers who requested the feature, prior to release to all customers. Customers who requested the feature will be advised of feature availability and how to use it by the CSM.

8. Feedback Loop: After the feature is released, the Product Management and R&D teams continue to review feedback reported by customers via support tickets or your CSM, to monitor feature performance, gather suggestions for improvements, and/or identify any issues that need to be addressed in future iterations.

Iterate and Improve: Product management and R&D teams use the customer feedback gathered from users to iterate on the feature, make improvements, and add enhancements in subsequent releases. The goal is to continuously evolve the Reveal Platform to better meet the needs and preferences of customers.