Customer feedback drives Bynder innovation

  • Updated

Bynder customers make Bynder better. Innovation is one of our core values, and we encourage customers to share their feedback. While making every suggested improvement in our product is impossible, we’re constantly evaluating market trends and learning about the innovative ways our customers use our products. We’re committed to transparency with what we’re working on, why we’ve prioritized those items, and what’s coming next.

The Bynder Roadmap

As a Bynder customer, you can find our Product Roadmap here. Create an account if it's your first time accessing the Community. Otherwise, you can log in with your existing credentials.

The roadmap is a direct response to your feedback and gives you more transparency into our product development cycles so you can better understand what we've released, what we're actively working on, and what we are thinking of building.

How our Product Team Works

The Bynder Product team strives to help you, our customers, reach your objectives. The Product team releases new and/or improved functionality every six weeks. In addition, they are listening carefully, understanding deeply, and regularly collaborating to create and deliver the best possible solutions, working with customers every step of the way.

  • Listen

    • First, we listen to our customers to understand their pain points and needs using the Bynder platform. Based on conversations, surveys, and data, we identify themes.

    • We then prioritize the problems we want to solve by assessing their impact on our customers and their fit with our overall strategy.

  • Ideate

    • Once prioritized, we engage with customers and review past feedback to identify the best solution.

    • Our teams then propose a solution; in some cases, we work with customers to test the proposed solution.

  • Validate

    • When developing and finalizing solutions, we consider our customer base, the rapidly changing martech landscape, and market trends.

    • Our goal is for solutions to be as universally applicable as possible so that every customer can take advantage of innovation across the platform.

  • Launch

    • We then deploy the solution to the Bynder platform after completing all validation, testing, and quality assurance steps.

  • Iterate

    • Does this mean “Job done”? Not quite. After we have released the solution, we carefully monitor performance to ensure we’ve definitively solved the problem we set out to solve.

    • And once again, we engage with customers to hear their feedback, which often leads to new ideas and insights for future development.

Get Involved!

We welcome your feedback! You can get involved by:

  1. Participating in the Bynder Community and joining the discussion

  2. Voting on the Product Roadmap and telling us how important these ideas are to you.

  3. Providing specific product feedback to your Customer Success Manager or Support team.

  4. Joining an upcoming roadmap webinar where Product Managers share recent releases and plans and where they often solicit feedback directly from customers.

  5. Joining product feedback sessions. We’ll publicize these sessions during roadmap webinars, conversations with your CSM, or as a part of beta testing programs.

We can most effectively understand and act on your feedback if it follows a specific structure and includes critical information. The most important things we need from you are a clear description of the problem that you are trying to solve and the impact on your business. It’s natural to identify potential solutions in the product, but our teams can explore other possible solutions if we have a clear understanding of the problem you are trying to solve first.

Please use the structure below when sharing feedback via the Product Roadmap or with your CSM or the Support team. In doing so, our team can understand and act more quickly. Of course, you are always welcome to add more, but at a minimum, please let us know

“As a [user] from [Business Name], I [want to...], [so that...]. This is [a nice to have/relatively important/strongly desired]”:

  • [user] describes the type of user in Bynder, not your job role.

  • [want to] outlines the user’s intent—what are they trying to achieve? Do not describe the UI here.

  • [so that] refers to the bigger picture the customer is trying to address.

Once the team receives your feedback, they will share it with the Product team, and we’ll evaluate for consideration in the roadmap. Every piece of feedback is reviewed and considered.

Was this article helpful?

0 out of 0 found this helpful

We're sorry to hear that!

Find out more in our community

Have more questions? Submit a request