Assignment 1.4
Peer Review & Feedback Session
🎥 Video Outline
Why Peer Review Matters
- In professional studios, ideas and documents are always reviewed by others.
- Feedback improves clarity, reveals blind spots, and helps the whole team align.
How to Give Useful Feedback
- Be specific: point out what is clear vs what is confusing.
- Be constructive: suggest improvements, not just criticism.
- Focus on clarity, feasibility, and scope — not art polish.
How to Receive Feedback
- Listen without arguing.
- Ask clarifying questions if you don’t understand a comment.
- Decide what to revise — not all feedback needs to be applied, but you should reflect on it.
Feedback in the GDD Context
- Review each other’s narrative, core loop, and features list.
- Ask: “Could I build this game slice if I only had this document?”
📚 Resources
- Peer Review Checklist — Download Here
- Example peer review forms will be provided in class to guide structured feedback.
🛠️ Workshop Goals
Workshop 1
- Exchange draft GDDs with 1–2 peers.
- Use the checklist to review:
- Narrative clarity (is the premise clear?).
- Core loop feasibility (can this be built?).
- Features list scope (is it realistic?).
- Art/style guide readability.
- Write peer feedback notes (strengths + improvements).
Workshop 2
- Meet with peers to discuss feedback.
- Revise your GDD based on key suggestions.
- Document what feedback you accepted, and why.
- Upload the revised draft to Canvas / portfolio.
If you finish early:
- Review an additional peer’s GDD.
- Expand your own GDD with more visuals (sketches, diagrams).
📑 Deliverables
- Peer Review Notes (feedback you gave to others + what you received).
- Revised Draft GDD updated with changes.
- Reflection Paragraph on what feedback was most useful and how you applied it.
- Upload to Canvas and Portfolio as:
“Peer Review & Revised GDD”