Ask anyone in the tech world and they’ll tell you that user testing is the key to good software development. In fact, that’s not quite true, because the key is actually good user testing. Users don’t always give you exactly the information you need. Or they may not give you all the information you need. For these reasons, you need to be able to do an excellent job of debriefing a user test with the users.
Debriefing basically means talking about an experience. Debriefing helps us understand a user’s thoughts and feelings during their experience with the software. And in software development, that means we can make the necessary changes to improve that experience.
Debriefing a user test effectively might require you to do several things. For one, it’s a good idea to start by setting the focus for the debrief. And later, you might have to bring the user back to that focus area. To get a general sense of the experience, you might ask for overall impressions. And to get more detail, you might ask the user to talk about the process of using the software. It’s also a good idea to acknowledge important issues when they come up.
In today’s dialog, we’ll hear a software developer named Jill debriefing a user test with Carla, an office worker. Jill’s company, OptiTech, has been developing new software for a logistics company where Carla works.
1. What does Jill say she wants to focus on in the debrief?
2. How does Jill respond to Carla’s suggestion about being able to update a driver’s status?
3. How does Jill respond when Carla mentions that the routes are changing color too soon?