Lucid Community conversations are full of feedback about Lucidchart, Lucidspark, and Lucidscale, and we love that! We're always looking for how we can make our products more effective for you, and your experiences and needs are essential for us to understand. Below, find answers to your most important questions about submitting feedback and feature requests.
Why are your feature requests important?
Are your feature requests noticed? Yes! And much more than that.
Lucid highly values your feedback and needs and actively seeks to understand how its products can better support you in your work. Your feature requests are collected and examined by the Community Team, then are shared with our Product Team for review as it considers improvements and further developments to our products. Before thinking it’s not worth putting in your own feature request or that someone else has already beat you to it, think again! Each request matters, helping to voice more support and add additional context.
What happens with your feature requests?
If you’re worrying that your feature requests disappear after submission, never to be looked at, we can assure you that’s not the case!
Your feature requests are used in two ways:
- The requests and additional use case details you submit using the Lucidchart, Lucidspark, and Lucidscale feature request forms are added into a repository for the product team to consider for future developments and improvements. These feature requests also serve as an excellent source of detailed feedback for the Product Team to understand why and how you use a feature - the more detail you can share, the better!
- Separately, our Community Team tracks which posts contain feature requests so that we are able to highlight new and popular requests to the rest of the community using the monthly Community News post and keep the conversation going.
- We can’t make every feature request happen. Some conflict with other requests while others might not make sense for the development of our product. However, we will try our best to implement as many feature requests as possible.
- Creating a new feature might be a long process. There’s a lot of work that goes into making a new feature for our products. So, if it’s been a while and your request still hasn’t been implemented, don’t lose hope! It might just be delayed, but that doesn’t mean it won’t happen.
Where can I see what’s new?
The monthly Community News post in the Announcements and Community Information topic provides regular updates about changes to the product, including relevant resources and opportunities. Here, you’ll also find information about AB tests, bug fixes, and popular community conversations.