GROCS Design Review
GROCS Design Review
This document describes a standard design feedback presentation format for GROCS participants.
When and why
We envision GROCS teams giving at least 2 presentations for their peers – first to help define the scope or
specific focus of the project; and again at some pivotal point before the project’s completion.
These presentations are meant to:
• Inform peers, staff and the public of project details, particularly the interesting questions being
addressed by the project
• Give the project team feedback (and help)
• Help to establish connections between individuals who can contribute to a particular project or learn
• Help to establish a context within which this interaction can occur (without emotional strain)
The guidelines that follow are specifically intended to allow the design team to present the project and solicit
feedback without having to defend or explain their (likely complicated and careful) decisions "on their feet"
in front of the group.
Be concise and to the point. The time guidelines below are only suggestions, you can divide up the time in other
ratios if it is more suitable for your presentation.
Overview of the project
Describe the history, purpose/ problem, audience, timeline, team composition, and any other
relevant background information.
Demonstrate/present relevant aspects of the project
Show your work
Present a problem/issue/question/decision for feedback
Briefly describe issues on which the team like the audience to comment.
Round robin presentation of feedback, comments, suggestions
Presenters become mostly passive and listen to comments and suggestions from the audience,
commenting in turn around the room. At the end of the presentation the audience will turn in their
comments (on forms provided) to the design team.
The project team collects the Design Review Worksheets. The audience comments may be made
public, and the team may wish to publish responses to comments.