11.2. Written Reflection Requirements

● Content: Tool choices, major design decisions, iteration log with dates, user feedback summary, lessons learned.

In this chunk, we're discussing what to include in your written reflection. First, you should detail the 'Tool choices'—the software and applications you decided to use during your design process. Next, 'major design decisions' should cover the key choices that significantly influenced your project. The 'iteration log with dates' tracks when you made changes and why, showcasing your development process. The 'user feedback summary' allows you to present the responses from the individuals who tested your prototype. Lastly, 'lessons learned' focuses on what insights you gained through the project, which can be useful for future work.

Think of your written reflection as a travel journal. Just like a journal captures where you went, what you saw, and what you learned along the way, your reflection captures the tools used, choices made, feedback received, and lessons learned during your design journey.

● Content: Tool choices...

This point emphasizes the importance of documenting the tools you used in your project. It's critical to explain why you chose certain software or applications. For example, if you used Figma for prototyping, note its collaborative features that allow team members to view and comment on the design in real-time. Also, highlight any specific tools (like design assets or plugins) that helped you achieve your design goals.

Imagine preparing for a big cooking competition. You’d want to detail not just the dishes you made but also the kitchen tools you chose, like a particular knife because it helps you chop vegetables more efficiently. Similarly, in your reflection, articulate how your chosen design tools improved your workflow.

● Major design decisions...

In this section, you should discuss significant choices regarding the visuals and functions of your design. Explain your rationale behind these decisions. For example, why did you choose a particular color scheme or typography? What goals did you prioritize, and how did they guide your design? This elaboration not only reflects your thought process but also justifies your design choices.

Consider writing a book. Each major plot point is a decision that shapes the storyline. You’d explain why you wrote your protagonist in a certain way or chose a specific setting. Just like that, in your reflection, articulate your design decisions as pivotal shifts in your project’s narrative.

● Iteration log with dates...

Creating an iteration log involves logging all changes made to your project along with the dates of those changes. This helps you track your design evolution over time. It’s also a vital practice for demonstrating how user feedback or usability tests informed your design adjustments. Each entry should explain what was changed and why, providing insight into your iterative design process.

Think of an artist revising their painting. As they step back and assess their work, they might make notes about what colors to change or details to add, accompanied by the date of each modification. This process informs their final piece and showcases their growth. Your iteration log works similarly, reflecting your progress and responsiveness to feedback.

● User feedback summary...

Summarizing user feedback involves collecting and categorizing the insights you received from those who tested your prototype. This summary should address common themes, specific suggestions, and notable critiques. Understanding this feedback allows you to show how it influenced your design improvements and to highlight the voices of your testers in your creative process.

Picture conducting a survey after a movie screening. You’d gather audience reactions and summarize their thoughts on aspects like character development and pacing. Similar to that, your feedback summary provides a compact glimpse into how users interacted with your design and informs future enhancements.

● Lessons learned.

This final part of the written reflection requires you to articulate any insights gained throughout the design process. Consider skills improved, challenges confronted, and strategies that proved effective or ineffective. This is an opportunity for self-reflection that can help you grow as a designer by recognizing the strengths and weaknesses you've exhibited.

Imagine an athlete reflecting on their performance after a competition. They’d think about their training regimen, the mistakes made during the event, and what worked well. Just like them, use your lessons learned to evaluate your journey and prepare for future challenges, ensuring continuous improvement.

--