I've recently begun interest in a framework for developing solutions to problems called Design Thinking. Essentially you follow approx 5 steps in non-linear order to design a solution for all the people involved in your product or process.
The first step is Empathize (and this will the the step that's relevant for this post), but I'm having difficulty understanding how to actually do this step. If someone claims to have a problem, how do you empathize with it even if you disagree or are not sure that it is a problem worth solving? If someone has a positive experience, how do you know if that positive experience is worth implementing in your design solution?
If many students say something like, "I wish I had all the time in the world to do my homework", how do you interpret that data? Supposing that you got this feedback from a survey about the school experience. We don't know for sure whether we should eliminate all due dates on homework even if many students claim to want it.
My solution to this problem is instead of taking people's feedback at face value, I break down people's feedback to create a palette of definitions that serve as a mental model for creating a solution. Taking the student survey example, we can make a list of words that have occurred frequently after surveying:
- homework
- time
- student
No longer are we necessarily believing that students should be able to delay turning in homework indefinitely, but we do know that students care about these listed topics a lot and that our new schooling system should eliminate the problem of time, homework, and students, or if that's not possible, prioritize those points.
Do you have any suggestions on how to process survey feedback when looking for a new design for the school/education system? Note that I haven't even started doing any surveying and I'm ignoring that step for now.
Submitted June 29, 2020 at 06:07PM by SJ_the_changer https://ift.tt/3eL18CF
No hay comentarios:
Publicar un comentario