Wie verwalten Sie das Benutzerfeedback nach der Bereitstellung einer Lösung?

I had an experience when the client feedback was not as we expected after deploying the product. Luckily, I prepared the questions that helped both sides (client and IT team) to understand the goals and initial requirements from the customer. The questions that I have prepared to ask after the session were: - Does the solution align with your business goals? - How is the performance of the system and are you able to perform your tasks normally? - Is everything clear to the user from the UI point? - Is there function you would to like update?

Managing user feedback post-solution is key. Personalize responses, listen actively, prioritize issues, and iterate for continuous improvement.

There are many different ways of getting the feedback such as workshops, surveys, analytics and etc. However, I personally prefer interview. Why? 1. It creates some sort of sincerity between me and stakeholder. 2. Emotions may give some insight about what a person truly feels. Most of the time we don't get it remotely. 3. It's easier to have a clear view on the same topic. There are some useful tips that I think Business Analyst should consider when selecting interview method: 1. Try to have a face to face meeting, if it's possible. 2. Prepare the questions in advance. 3. Send message or email to thank for setting up time for interview to the stakeholder.

I personally use paper and a pen while having interview. I take notes not on my laptop or any electronic device, but rather I prefer writing my notes down on a piece of paper. Why? It may sound strange, but I believe there is something called "hand memory". When you write something down instead of typing, you tend to remember it better. After I have my notes on the paper, I organize them and analyze the data using some tools. I prefer this method and also advice my students to do the same. Because it gives you better understanding and clearty.

After analyzing the feedback data, I try to divide them into some sections and categories in order to implement the right action. I try to have some tags according the the priority and urgency of the action. For example, it may look like this: Action:Fixing the bug regarding contact form Type: Bug Priority: High Additional comments: It blocks user from sending the request "

In my experience at a health insurance company, managing user feedback after deploying a solution was a crucial part of ensuring our offerings met user needs and expectations. We established a continuous feedback loop through various channels like post-deployment surveys, direct user interviews, and feedback forms integrated into our digital platforms. This allowed users to easily share their thoughts and concerns. Moreover, we categorized feedback into critical, major, and minor issues based on their impact. Critical issues were promptly addressed, major issues were scheduled for the next update, and minor ones were recorded for future improvements.

Managing user feedback after deploying a solution involves collecting and categorizing user input, assigning responsibility for handling it, and documenting feedback. Prioritizing feedback based on impact, planning, and scheduling changes are crucial steps. Implement solutions, communicate progress, and close the feedback loop with users. Analyze feedback trends for long-term improvements, express gratitude to users, and continuously iterate to enhance the product and user experience.

Here are some useful tips that you may want to consider implementing feedback outcomes: 1. Don't give promises to clients before discussing and estimating the efforts to solve issues with the team. There may be technical points that you have overlooked. So it's always good idea to consult with the team first. 2. Take notes. 3. Send email about the outcomes of the meeting to the interviewee to be on the same page. 4. Prepare the questions in advance.