Skip to main content
How We Prioritise Feature Requests

Balancing Feedback with Strategic Focus

Jim Evans avatar
Written by Jim Evans
Updated over 2 months ago

At Full Fabric, customer feedback is a cornerstone of continuous improvement and innovation. Our product is built with our users' needs in mind, and we are committed to listening to your feedback and incorporating it into our development process. To ensure we develop the most impactful features and enhancements, we have a structured approach to prioritise feature requests, balancing feedback with our strategic goals.

The Importance of Feedback

To capture this feedback efficiently, we have created a feedback portal. Users can submit their ideas, suggestions, and concerns directly to our product team. The portal allows us to organise, track, and assess the feedback we receive while also providing a space where you can see what others have suggested and vote on your most wanted features.

Please refer to submitting feature requests for more information on how to submit feature requests and improvements.

Giving Feedback

To capture this feedback efficiently, we have created a feedback portal. Users can submit their ideas, suggestions, and concerns directly to our product team. The portal allows us to organise, track, and assess the feedback we receive while also providing a space where you can see what others have suggested and vote on your most wanted features.

Working with your Customer Success Manager

In addition to submitting requests directly through the feedback portal, users can also collaborate with their Customer Success Manager (CSM) to discuss potential feature enhancements. Your CSM serves as your advocate within Full Fabric, ensuring that your needs are communicated clearly to our product team. This method can be particularly helpful when you need to provide additional context or discuss complex needs in more detail.

However, it’s important to note that requests communicated through your CSM should eventually be submitted to the feedback portal, either by you or your CSM. Once a request is in the portal, you’ll be able to follow its progress, vote on it, and see updates alongside other users.

Going the Extra Mile with Development Sprints

For clients with specific needs or feature requests that require a more immediate or tailored approach, we offer Development Sprints - a paid, time-boxed, fixed-scope project designed to deliver the capabilities that are most important to you predictably and cost-effectively. This option allows you to prioritise the development of features that are critical to your operations, with clear timelines and deliverables agreed upon upfront. Our team works closely with you to define the project scope, ensuring that the solution aligns with your business requirements and seamlessly integrates with the Full Fabric platform.

If you’re interested in exploring a Development Sprint, please reach out to your Customer Success Manager for more details.

Balancing Feedback with Strategic Focus

While feedback is crucial, it is equally important to recognise that we cannot develop every suggestion that comes our way. We aim to create a product that satisfies immediate user requests and aligns with our long-term vision and strategic goals. To strike this balance, we rely on a prioritisation framework that considers multiple factors:

Customer Impact: We assess the potential impact a feature will have on our users. Features that solve widespread issues, enhance user experience, or significantly improve the value of our product are given higher priority. We listen closely to feedback that is backed by a large segment of our user base, as it often indicates a critical need.

Alignment with Strategic Goals: We evaluate whether a requested feature aligns with our broader product vision and strategic roadmap. Our goal is to ensure that each new feature contributes to our mission of delivering innovative, high-quality solutions that differentiate us in the market. This sometimes means that we may prioritise features that may not have been highly requested but are essential to achieving our strategic milestones.

Technical Feasibility: We also consider the technical complexity and resources required to develop each feature. Some requests may be straightforward, while others could involve significant changes to our architecture. By weighing technical feasibility, we ensure that we focus on delivering high-quality solutions within reasonable timelines.

User Votes and Trends: Users can vote on suggested features through our feedback portal. This helps us identify trending requests and prioritise features that resonate with a large portion of our community. While votes are an important part of our decision-making process, they are one of several factors we consider.

Feature Requests vs. Bugs: Understanding the Difference

Before diving into our prioritisation process, it’s important to clarify the difference between a feature request or improvement and a bug:

  • Feature Requests/Improvements: These are suggestions from users that propose new functionality or enhancements to existing features. A feature request could be a new tool, an integration with another software, or an adjustment to an existing functionality that would improve usability. These ideas are focused on expanding the product's capabilities or refining the user experience.

  • Bugs: A bug refers to a defect or error in the software that prevents existing functionality from working as intended. Bugs need to be fixed to ensure the product operates correctly and reliably. Our team prioritises bugs based on their severity, impact on the user experience, and the number of users affected. Fixing bugs is typically treated with a higher level of urgency, as they are critical to maintaining the product’s stability and usability.

Understanding this distinction helps clarify why certain issues might be addressed more quickly than others. While we strive to continuously improve the product through feature requests and enhancements, our priority is always to ensure the core product functions smoothly and reliably.

Our Prioritisation Process

We review and prioritise feature requests monthly to ensure that we are staying aligned with the latest feedback and market trends. This regular cadence allows us to stay agile and responsive, adapting our focus as new trends or needs emerge.

However, it’s important to understand that not all feature requests will appear on the public roadmap immediately—or at all. Some features may require extensive research, development, or alignment with other strategic initiatives, which can extend the time before they are visible on the roadmap. Others might not fit our current product direction, even though they are valuable ideas. In such cases, we may revisit the request later as the product evolves or as new priorities emerge.

Transparency Through Our Public Roadmap

To promote transparency and keep our users informed, we maintain a public roadmap that provides visibility into what we are working on, what is in the pipeline, and what has been released. The roadmap serves as a bridge between our users and our product team, providing clarity on how we are incorporating feedback into our development process.

The roadmap includes features that have been selected based on the criteria above, giving you a sense of our priorities and progress. It’s our way of saying: "We hear you, and here’s how we are acting on your input."

Our Commitment to Building the Best Product

At Full Fabric, we strive to make decisions that will benefit our users and our product in the long term. While we may not be able to develop every feature request, rest assured that your feedback is always considered thoughtfully and respectfully. We are committed to delivering a product that reflects the needs of our users while staying true to our vision of innovation and growth.

Thank you for being an active participant in our journey. Your feedback helps us get better every day, and we look forward to continuing to build a product that supports your success.

Did this answer your question?