Feature Requests

At Kraken, we prioritise customer satisfaction and feedback, clients are encouraged to share their suggestions for improvements to existing functionalities and ideas for new functionalities via their Power Users and regular forums. 

Regular Forums

During the scheduled Kraken-Client meetings, the Delivery Manager will collect information about the feature requests: 

• The basic idea/problem to be solved - who will use it and to achieve what on the product?
• The value of this / what the impact is of not having it
• What a successful solution would demonstrate (must have and nice to have requirements)
• The best client contact point for driving this priority

What happens after submission? 

Each feature request is added to an internal directory where the Product team complete discovery - carefully evaluate their feasibility, impact, and alignment with the product roadmap. A decision on proceeding is then taken and actioned by the Delivery Manager:

• Further information required: additional details are needed to better understand the request.
• Viable development and a Kraken priority: if deemed feasible and aligned with our goals, the request is added to the relevant backlog for Product Team planning.
• Viable development but not an immediate Kraken priority: the request is feasible for development but is not currently among our top priorities. If this item is a high priority for you, this may trigger a commercial discussion.
• Feature request is not aligned with Kraken roadmap / not technically feasible: if the request does not align with our roadmap or is technically unfeasible, it will not be pursued.

Kraken’s product and development teams carefully assess each request's feasibility and prioritise them based on the roadmap and available resources.