All right, day five. So you've got your test plan results and now you need to figure out what you learned, what it means, and what you're going to do next. And so you'll spend the morning finishing up your testing and then I think you'll find you'll have plenty of time in the afternoon to make those final set of conclusions and drive to your next steps. So morning time, you're running your test plan, we're really just looking at this part here. I would repeat basically what you did on day four and post those top learnings, stick a vote on them to drive discussion, and then assign peers and review your test plan notes, okay. You'll probably have fewer notes on these, and yes, you have the recordings, but make sure that you're cleaning up those transcripts. You're making notes on the insights, and it's not, okay, Alex, review the notes you made again. It's Stan review Alex's notes. Alex, review Stan's notes. That's important because the whole point of this is that you accrue this asset. And other people are able to go in as you find other things that are and are not important in the future and look at the results you've got and what happened. It took you a lot of time to get this, so you might as well make sure it's usable and readable. You'll have some time to do updates on that, you have a break. And then whatever revisions to your mock ups, your software, your test plan for next time, you want to go ahead and make those. And then you want to review and prepare next steps. What are you going to do now? Go build software, think about architecture, rinse and repeat some of the other stuff. This is a time when you, in principle, have driven through a relatively specific view of what's going to be valuable to the user. And you may be quite ready to build software if you know what approach you're going to take. So here you've learned how to take this sort of nebulous thing of usability and put it in the right place in your process, so you know when it's time to really focus on that. You have a systematic way to think through it and you have a test regime that is sort of phase appropriate, highly approachable, I think you'll find. And something that you can do regularly with your team to make sure that you figure out what's going to be usable and valuable to the your end user before you go and you release software.