Practice - Section E: Iteration Driven by Formative Feedback
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.
Practice Questions
Test your understanding with targeted questions
What is the primary goal of formative feedback during the design process?
* Answer: To improve the design through early, continuous input before final implementation.
* Hint: It's about learning and improving, not grading.
💡 Hint: It's about learning and improving, not grading.
Name one common method for gathering formative feedback in UI design.
* Answer: Usability testing (or Stakeholder reviews, A/B testing, or informal user interviews).
* Hint: Think about watching users interact with a prototype.
💡 Hint: Think about watching users interact with a prototype.
7 more questions available
Interactive Quizzes
Quick quizzes to reinforce your learning
What type of feedback is collected during the development process to improve the final outcome?
* Type: mcq
* Options: Summative, Formative, Passive
* Correct Answer: Formative
* Explanation: Formative feedback happens during the process, helping shape the final product.
* Hint: It’s like a mid-course correction.
💡 Hint: It’s like a mid-course correction.
True or False: The primary purpose of formative feedback is to assign a grade or final score to the product's usability.
* Type: boolean
* Options: True, False
* Correct Answer: False
* Explanation: Summative feedback handles final assessment; formative feedback focuses on improvement and iteration.
* Hint: Formative is about shaping; summative is about assessing.
💡 Hint: Formative is about shaping; summative is about assessing.
2 more questions available
Challenge Problems
Push your limits with advanced challenges
Imagine you’ve received the following feedback from 4 different users about your app’s onboarding process: “Too fast”, “Too many steps”, “Unclear CTA”, “Visually overwhelming.” How would you iterate on your prototype?
* Solution:
1. Address "Too many steps" & "Too fast": Synthesize by reducing the total number of screens (fewer steps) and increasing the "After Delay" or animation duration (slowing the pace).
2. Address "Unclear CTA": Revise the CTA copy to be action-oriented (e.g., change "Go" to "Start Your Tour") and increase its color contrast for better visibility.
3. Address "Visually overwhelming": Simplify the visuals by reducing the density of images or text per screen, relying more on whitespace and clear typographic hierarchy.
4. Final Step: Retest the revised prototype with the same users to validate the fixes.
* Hint: Focus on clarity and simplicity, and address the time/pacing issues.
💡 Hint: Focus on clarity and simplicity, and address the time/pacing issues.
As a designer on a collaborative team, you receive vague feedback like "I'm not sure this works" from a key stakeholder. How do you turn this into actionable guidance?
* Solution:
1. Ask for Specificity: Ask targeted follow-up questions such as, "Which specific interaction or screen felt unclear?" or "What would you expect to happen instead?"
2. Focus on Goals: Ask, "Does this part of the design help you meet your goal of [stakeholder's goal]?"
3. Encourage Documentation: Guide the stakeholder to leave a comment or pin directly on the design element in question in Figma, forcing them to pinpoint the source of the discomfort.
* Hint: Clarity comes from asking the right questions that force the reviewer to pinpoint the location and describe the expected outcome.
💡 Hint: Clarity comes from asking the right questions that force the reviewer to pinpoint the location and describe the expected outcome.
Get performance evaluation