End-users are giving unclear feedback on database changes. How will you decipher their true needs?

Temos que começar fazendo perguntas abertas para que eles possam se expressar melhor. Em vez de perguntar "Você gostou da mudança?", tente "O que você achou mais difícil de usar agora?" Observar como eles interagem com o sistema. Às vezes, ver na prática o que está acontecendo pode revelar problemas que eles não conseguem explicar. Considerar fazer reuniões ou workshops para discutir as mudanças e coletar feedback de forma mais estruturada. Isso não só ajuda a esclarecer as necessidades, mas também mostra que você valoriza a opinião deles.

1) Realizar entrevistas detalladas. 2) Análisis de casos de uso. 3) Workshops y sesiones de trabajo. 4) Prototipos y retroalimentación. 5) Análisis de datos existentes. 6) Comunicación continua. 7) Documentación y seguimiento.

After listening, the next step is to clarify your users’ needs. This involves repeating their concerns in your own words and asking for confirmation to ensure you have understood correctly. If a user mentions that the interface is “confusing,” ask them to describe an ideal layout or specify which elements are causing confusion. This approach helps bridge the gap between what users say and what they actually need from the database.

One aspect I find beneficial is the ability to receive user feedback; my go-to approach involves active listening and understanding the users, which is crucial for troubleshooting. It's essential to identify the root cause through open-ended questions, considering the various user roles and needs, to grasp the diverse perspectives and requirements of your user base. Adequate communication and thorough analysis are key to brainstorming solutions that meet user needs. Additionally, it is highly encouraged to document each step engaged in the successful resolution of the problem for future reference. Surveys enable users to contribute to more structured database changes.

An example of this is empathizing with what is currently hardest in the end users job. Every interface is built to do something for a user. By empathizing with the end user you set yourself up to be better able to fill in the gaps of the user needs and make the interface a lot more user friendly.

An example of this is empathizing with what is currently hardest in the end users job. Every interface is built to do something for a user. By empathizing with the end user you set yourself up to be better able to fill in the gaps of the user needs and make the interface a lot more user friendly.

An example of this is empathizing with what is currently hardest in the end users job. Every interface is built to do something for a user. By empathizing with the end user you set yourself up to be better able to fill in the gaps of the user needs and make the interface a lot more user friendly.

Empathizing with user is a skill and requires patient and ability to 'listen' - user generally verbalize their issues they way they understand it, not how the solution is design to function. The best approach to understand an issue and resolve adequately should involve user going through all the step he perform and in 99.9% of the cases - seing and experiencing what the user report as an issue is the best way to sympathize with the issue. User often uses conflicting wording and terms that are not relating necessarily to a specific problem.

I second this, usually people think that they would remember everything but its not likely the case! Notepad or google doc is your best friend