Written Reflection Requirements
Enroll to start learning
Youβve not yet enrolled in this course. Please enroll for free to listen to audio lessons, classroom podcasts and take practice test.
Interactive Audio Lesson
Listen to a student-teacher conversation explaining the topic in a relatable way.
Purpose of Written Reflections
π Unlock Audio Lesson
Sign up and enroll to listen to this audio lesson
Today we're discussing the written reflection requirements for your capstone project. Can anyone tell me why reflection is important in design?
I think it helps us learn from our mistakes.
Absolutely! Reflection allows you to analyze your decisions and improve over time. Itβs a chance to document your journey. What other elements do you think are important in these reflections?
Maybe it should include feedback we received from others?
Exactly, including user feedback is crucial. It helps articulate how others perceive your design and informs future iterations. Let's remember this with the acronym FLEDβFeedback, Learning, Enhancements, Decisions.
So FLED helps us remember key areas to focus on in our reflections?
Yes! Reflecting on these elements will contribute to more comprehensive insights. Any final thoughts?
I think it will also help us prepare for any design critiques.
Exactly! Summarizing what youβve learned along the way equips you for constructive criticism. Great session!
Components of the Reflection
π Unlock Audio Lesson
Sign up and enroll to listen to this audio lesson
Letβs break down what should be included in your written reflection. Can anyone name one of the components?
We should write about the tools we used!
Yes, tool choices are critical. They impact how effectively you can implement your design. Another important part?
The major design decisions we made?
Exactly! Documenting those decisions provides context for your design direction. Think of the acronym TIDEβTools, Insights, Decisions, Enhancementsβto help remember each category in your reflections.
What was the last part of TIDE?
Enhancements! Reflections should also note how you've improved upon your designs based on feedback. Any other components we should consider?
Lessons learned, right?
Exactly! Articulating lessons learned helps you grow as a designer. Fantastic discussion today, TIDE will really help us keep structured reflections!
Iterative Reflection
π Unlock Audio Lesson
Sign up and enroll to listen to this audio lesson
Now, letβs talk about how you can structure your reflections iteratively. Why do you think this is important?
So we can better track the progress of our designs over time?
Exactly! An iterative reflection captures the evolution of your work. How can we organize this information effectively?
Maybe by including dates or specific stages of our design process?
Perfect! You could also use a table to highlight these iterations. Think of the technique PICEβProgress, Insight, Change, Evaluationβfor structuring your reflections.
So each PICE component focuses on a different aspect of our design growth?
Exactly! It gives a comprehensive look at how your design is evolving. Keep this structure in mind while you write your reflections!
Introduction & Overview
Read summaries of the section's main ideas at different levels of detail.
Quick Overview
Standard
Written reflections require students to articulate their design decisions, tool selections, formative feedback received, and personal lessons learned throughout the prototyping process, thereby providing insights into their design journey and growth.
Detailed
Written Reflection Requirements
This section emphasizes the importance of written reflections in the design process, particularly for the capstone prototype project. A comprehensive reflection should cover key elements: the selection of design tools, significant design decisions made along the way, a detailed iteration log that tracks progress and changes with dates, a summary of user feedback received during evaluations, and a personal account of lessons learned throughout the project. Such reflections are not merely administrative; they serve as vital components for self-assessment and future development in design practices.
Audio Book
Dive deep into the subject with an immersive audiobook experience.
Content Overview
Chapter 1 of 6
π Unlock Audio Chapter
Sign up and enroll to access the full audio experience
Chapter Content
β Content: Tool choices, major design decisions, iteration log with dates, user feedback summary, lessons learned.
Detailed Explanation
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.
Examples & Analogies
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.
Tool Choices
Chapter 2 of 6
π Unlock Audio Chapter
Sign up and enroll to access the full audio experience
Chapter Content
β Content: Tool choices...
Detailed Explanation
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.
Examples & Analogies
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
Chapter 3 of 6
π Unlock Audio Chapter
Sign up and enroll to access the full audio experience
Chapter Content
β Major design decisions...
Detailed Explanation
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.
Examples & Analogies
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
Chapter 4 of 6
π Unlock Audio Chapter
Sign up and enroll to access the full audio experience
Chapter Content
β Iteration log with dates...
Detailed Explanation
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.
Examples & Analogies
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
Chapter 5 of 6
π Unlock Audio Chapter
Sign up and enroll to access the full audio experience
Chapter Content
β User feedback summary...
Detailed Explanation
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.
Examples & Analogies
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
Chapter 6 of 6
π Unlock Audio Chapter
Sign up and enroll to access the full audio experience
Chapter Content
β Lessons learned.
Detailed Explanation
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.
Examples & Analogies
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.
Key Concepts
-
Reflection: A process of analyzing one's own work.
-
Formative Feedback: Valuable input received during the development phase.
-
Iteration Log: A documentation of design evolution.
-
Design Decisions: Choices made impacting the final design.
-
Lessons Learned: Insights from experiences or mistakes.
Examples & Applications
Using an iteration log to document changes made to the design based on user feedback.
Articulating lessons learned through the process such as recognizing the importance of user-centered feedback.
Memory Aids
Interactive tools to help you remember key concepts
Rhymes
Reflect and inspect, thatβs how you grow, learn from design, let your insights glow.
Stories
Imagine a savvy designer named Alex who kept a diary of their design journey, noting every tool used and every piece of feedback received. This diary became a treasure trove of lessons learned that helped Alex shine brighter in every project.
Memory Tools
FLEDβFeedback, Learning, Enhancements, Decisionsβhelps remember to cover key aspects in reflections.
Acronyms
PICE
Progress
Insight
Change
Evaluationβan outline for structured iterative reflection.
Flash Cards
Glossary
- Reflection
A process of introspection and analysis regarding one's work or experiences, in this context focusing on the design process.
- Formative Feedback
Input gathered during the project development phase aimed at informing adjustments and improvements rather than scoring.
- Iteration Log
A record documenting the evolution of a design project through various stages and changes made along the way.
- Design Decisions
Deliberations made throughout the design process impacting elements such as layout, color choice, and typography.
- Lessons Learned
Insights gained through various experiences or mistakes during the design process that inform future practices.
Reference links
Supplementary resources to enhance your learning experience.