1. Create one case study in notion, following the process outlined in the “story arc workshop.” You will present from this case study in class.
2. You may use a project from any project (any class, or something extracurricular). Keep in mind that it’s probably an effective use of time to use a project that you think will be included in your sophomore review.
3. Apply all learnings / guidelines present in the reading done for the last deliverable.
4. Apply Cat’s general guidelines for a good process blog (this time applied to a design case study):
   • DOCUMENT. Document your design process visually, as it happens (although you may need to stage some images). Include as many (good quality) images of your design process (whiteboards, in-action shots of you accomplishing tasks like ideation, talking to people, etc.) as possible.
   • REFLECT. Each deliverable should have some kind of process commentary / reflection
     • Mandatory: Why did you make the design decisions that you did? How is your deliverable informing your specific thinking about the design brief / context / the next step of the process?
     • Optional: how did it feel?
   • ATTRIBUTE.
     • Include any and all feedback (including the name(s) of those who gave it).
     • Document and cite any inspiration (images and otherwise) and sources of thinking. Don’t copy or plagiarize work (this includes the usage of generative AI).
     • Do not pass off professor / peer feedback as your own thinking. Credit your influences and inspirations, and cite the sources of ALL reference images / articles where applicable.
5. Turn in a PDF export and link to Canvas.

Rubric

You’ll be scored on each of the following criteria on a scale of 1-5:

• front matter. Case study begins with a concisely written and scan-able tagline / summary / specs. A hero image / description of the final object (in use) is shown.
• skeleton. Main titles and phases of the case study follow a understandable arc and contain descriptive and concise titles.
• visuals. A critical mass of visuals demonstrate each phase. A diagram / explanatory image or process image is included whenever appropriate. Lots of process imagery, and images of testing / feedback when it occurs. Visuals are well-formatted and apply good use of 2D design principles (gestalt, grids, etc.)
• scan-able. The piece works at variable speeds. In particular, we can scan the piece because it has highlighted text, bulleted lists, cards, diagrams, and other methods of "pre-digesting" information for us. Meanwhile, there are robust details for us to dive into the how / why of every major design decision.
• documentation. Each step as appropriate deliverables included in appropriate format (visual or otherwise) and are formatted well (sketchbook pictures / scans are edited such that backgrounds are removed, turned to a bright white, etc.).
• reflection / thinking. Major design decisions within each deliverable are properly and thoroughly rationalized.
• attribution. Feedback is thoroughly incorporated, detailed, and cited by feedback giver’s name. No thought processes from others are falsely attributed as your thinking.