As technology continues to evolve at a rapid pace, the way in which we interact with our devices and apps is constantly changing. For end users, these changes can bring about new and exciting features that make our lives easier and more convenient. However, for vendors and developers, the process of implementing these changes can be a delicate balance between meeting the needs of their users and staying competitive in the market.

From the end user’s perspective, changes to apps and devices are often viewed as a positive thing. New features and updates can bring new functionality and improve the overall user experience. However, it’s important to remember that not all changes are well-received by users. For example, redesigning a popular app that drastically changes the layout and navigation can be confusing and frustrating for users who are used to the old design.

From the vendor’s perspective, changes to apps and devices are a necessary part of staying competitive in the market. In order to keep up with the latest trends and technologies, vendors must continually update and improve their products. However, this can also be a double-edged sword. Introducing too many changes at once can overwhelm users and cause them to lose interest in the product. Additionally, introducing changes that users don’t want or need can lead to negative feedback and a decrease in user engagement.

In order to strike the right balance between meeting the needs of users and staying competitive in the market, vendors must take a holistic approach. This includes understanding the needs and wants of their users, as well as keeping an eye on the competition. By understanding what their users want and what their competitors are doing, vendors can make informed decisions about which changes to implement and when.

It is also a balance between the different needs and preferences of different users. What does the vendor do when some users prefer an approach that another group of users disapproves of? There’s not always an easy solution (such as do implement both options and letting users choose).
For many years we’ve been busy with improving our test management solution, in the first years mostly based on our internal ideas and knowledge (see for example a 2011 post about it), and as we grew, and Testuff got mature, we turned more and more to our community for ideas.

We try to keep our users highly involved, sending feedback, suggestions, and requests for enhancements and preferred changes. The best way to get users involved is to actually listen to what they say… that simple. We’ve learned that our users appreciate an honest dialog, a professional discussion, even if it doesn’t always end up with the implementation of what they have asked for.

A few of the guidelines that we follow:

  • We encourage feedback from a diverse group of users: to sure we gather ideas from a range of users, including those with different backgrounds, perspectives, and needs. This helps ensure that the new features will be useful to a wide range of testing groups.
  • Responsiveness and transparency: Users know that we are listening to their ideas and value their feedback. We are transparent about which ideas we’re considering and why, and keep users updated on the status of their suggestions.
  • We prioritize features that align with our product’s vision: While it’s important to consider all ideas, it’s also important to prioritize features that align with our product’s vision and overall strategy. This helps to ensure that new features are integrated seamlessly and contribute to the overall product goals.
  • Active listening: In order to understand their needs and priorities there need to be a dialog, a discussion.
  • Open-minded: e try to be open to new ideas and be willing to consider all suggestions.
  • Follow-up: It’s essential to follow up with users after they have sent an idea to keep them updated on the status of their suggestions. We never keep someone not knowing what’s their status, even if it is a decision not to go for their suggestion.

We also learned that any feedback, details of a use case, and review of a user’s work process, all help us to better plan and design our next move. It doesn’t have to be exactly what a user asked for, but what comes out of the open discussion and the information we get gives us a way to find the right direction. While doing that, we must always remember not to hurry ourselves to any user and request. It is our responsibility to make sure that whatever we add and/or change is good (or at least doesn’t do bad) for all of our users, with all their different needs and preferences.

Our incremental improvement approach (that has been so for over a decade) helps to stay on the right track, as it gives time to learn from user feedback, and adjust accordingly. After more than 170 monthly releases we do have some experience :-)