Loading the lesson
Loading the lesson
Search AllRounder.ai
Search the courses, subjects, tracks, games and features, or jump straight to a page.
Search the courses, subjects, tracks, games and features, or jump straight to a page.
Learn it your way
A short class with Sarah and her students. The other ways are under More.
Sign up free to listen. Transcripts are free to read.
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!
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!
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!
Reflect and inspect, that’s how you grow, learn from design, let your insights glow.
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.
FLED—Feedback, Learning, Enhancements, Decisions—helps remember to cover key aspects in reflections.
PICE: Progress, Insight, Change, Evaluation—an outline for structured iterative reflection.
Term
Reflection
Click to flip
Term
Iteration Log
Click to flip
Term
Formative Feedback
Click to flip
Term
Design Decisions
Click to flip
Term
Lessons Learned
Click to flip
A process of introspection and analysis regarding one's work or experiences, in this context focusing on the design process.
Input gathered during the project development phase aimed at informing adjustments and improvements rather than scoring.
A record documenting the evolution of a design project through various stages and changes made along the way.
Deliberations made throughout the design process impacting elements such as layout, color choice, and typography.
Insights gained through various experiences or mistakes during the design process that inform future practices.
This section outlines the expectations for the written reflection accompanying the capstone prototype project.
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.
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.