A clear and thoughtful prioritization of the feature roadmap is crucial for long-term success and customer satisfaction. Ultimately, we regularly face the challenge of selecting the ideas that bring the most value from a wide range of good suggestions – for you, our users, our company, and our product vision. But how do we go about this concretely?
1. User-Centricity as Top Principle
Our feature decisions are primarily based on your feedback. The feature roadmap, which you can view directly in CrewBrain under “Administration > Roadmap,” plays a very important role in this. Through your votes and super-votes, we receive direct feedback on which topics and areas are most requested by as many customers as possible.
2. Clear Focus on Product Value
Not every exciting feature is automatically a good feature. We ask ourselves with each idea:
Does this feature increase the concrete value of our product? Does it make existing processes easier, faster, or more intuitive?
Only if a feature visibly improves the product quality does it make it onto our roadmap.
3. Structured Prioritization Models
To make our decisions as objective and understandable as possible, we use established prioritization models. We feed them with information from the roadmap, including the number of customers interested in the feature, as well as the effort and complexity of its implementation.
4. Technical Feasibility and Effort
Technical considerations also play a central role. Some features may be theoretically attractive but are only feasible with significant development effort or come with technical dependencies. Therefore, we always seek early input from our development team to incorporate this information into our prioritization models.
5. Strategic Business Goals
Our product development is never isolated – it is part of an overarching strategy. Therefore, we prioritize features based on whether they contribute to reaching new target groups, market differentiation, or achieving long-term goals.
6. Iterative Approach Instead of Rigid Planning
Our roadmap is not a rigid structure, but a living tool. We regularly review whether new insights or changing market conditions require adjustments. This allows us to stay agile while keeping the strategic direction in mind.
Our primary goal is to drive the ongoing development of CrewBrain in line with your needs in the long term. This sometimes involves tough decisions – for example, not developing a highly requested feature because it has too many technical dependencies or because it could divert us from our core product focus. The more feedback we receive from you, especially through votes on individual roadmap topics, the easier it becomes for us to assign real value to these topics for you. And the more likely we are to enable the implementation of larger, more comprehensive topics when a significant portion of you is behind a specific idea.
Learn more about how to use our Feature Roadmap in our Wiki.
This post is also available in de_DE.
