I don't think it would be useful without some structure, otherwise adhoc random questions may spin a lot of wheels when the presentation might function but not meet expectations, or might not function and we have no idea what the expected assumptions and expectations are are; e.g. time, cost, quality level, budget, skill level and design complexity.
It is also best done with interactive audio so that rules out this site.
- Requirements Checklist for Design Phase ( 1,2,3 or as defined)
- Design specs being presented including all layers ( environment, format e.g. HIPO (hierarchical tree, Input, processes, outputs, Validation specs and tolerances)
- Design Review choices: (ad hoc, informal, formal), must haves , nice to have, incomplete, estimate of % complete, resources needed to fulfill objectives
- Conclusions: List of recommendations, rated by risk or difficulty with research\testing required)a
This was just an off-the-cuff response.