picture, erase the board, and keep going. Address recommendations and assign severity ratings. After you've made it through the interface and collected issues, it's time to discuss recommendations and severity ratings as a group. What will it take to solve each of the issues? Which issues are the most important to address? Use asterisks or numbers to denote how severe an issue is and write the recommendations directly below each issue. You may also wish to denote which issues are quick fixes. Transcribe issues and send the list to all of the participants. Identify more issues if necessary. You can now dismiss your participants. Make sure to take a picture of the whiteboard. Transcribe all of the issues, their severity ratings, and recommendations. If necessary, you may want to spend more time identifying any issues that were missed in the meeting or elaborating on recommendations. Send the list of issues to all of the participants and ask them if they have further input. If you are not in close contact, follow up with the team after a week or two to see if they need any help addressing the issues. Our Experience We've used the participatory expert review method several times and it appears to be very effective. In one review, a developer began addressing some of the quick issues on a laptop while we were still in the meeting (not at all recommended, but a promising sign that the method fosters engagement and responsiveness). So far, clients seem more