7.2. Reflective Prompts

1. In your first test, which assumption was most surprising?

This prompt encourages you to think critically about the assumptions you made before conducting your user test. Assumptions are ideas you believe to be true, grounded in your prior experiences or expectations about how users will interact with your design. Reflecting on what surprised you can help you identify gaps in your understanding of user behavior, leading to better designs in the future.

Imagine you're constructing a bridge and assume that cars would always follow the speed limit. During test runs, you discover that drivers often speed, causing unexpected stress on the structure. This revelation could lead you to modify your design to include better traffic control measures.

2. How did real users’ problem-solving differ from your expectations?

This prompt asks you to analyze the actual behavior of users compared to what you anticipated. Users often approach tasks with their unique experiences and thought processes, which may differ from your intended use cases. Understanding these differences can illuminate unexpected usability issues and can inform future design iterations.

Think of it like planning a picnic: you expect everyone to sit on the blanket and eat sandwiches, but when you arrive, some friends decide they want to explore instead, changing your plans entirely. This teaches you to consider alternative activities for future picnics.

3. Describe how quantitative data (times, error rates) and qualitative feedback (comments) guided your design decisions.

This prompt emphasizes the importance of both quantitative and qualitative data in user testing. Quantitative data, like task completion times, provides measurable results that show how efficiently users can interact with your design. In contrast, qualitative feedback, such as user comments, offers insights into users' feelings and thoughts during the interaction. Both types of data together help you make informed design decisions.

It’s akin to cooking: you weigh out ingredients to ensure the recipe is followed correctly (quantitative) but also taste the dish to check if it needs more salt or spices (qualitative). Both steps are crucial for ensuring a successful meal.

4. Why is it important to test low-, mid-, and high-fidelity prototypes through the cycle?

This prompt highlights that each prototype fidelity stage serves different purposes in the design process. Low-fidelity prototypes (like sketches) help explore ideas quickly and cheaply without detailed design work. Mid-fidelity prototypes (digital wireframes) allow for more interaction and help refine user interfaces. Finally, high-fidelity prototypes look and function like the finished product, providing a near-complete testing experience. Testing each level assures that problems are addressed early and leads to a more user-centered design.

Consider a film production: you might first do a table read (low fidelity), then practice scenes with basic props (mid fidelity), and finally shoot a full production with all effects, lighting, and sound (high fidelity). Each stage helps refine the story and ensures a better final product.

5. How can documenting your iterations support future designers and stakeholders?

This prompt underscores the value of keeping a record of your design iterations, including what changes were made, why they were necessary, and the results of each modification. This documentation not only helps you track your own design process but also provides valuable insights for future designers and stakeholders who may continue or build upon your work, ensuring continuity and informed decision-making.

Think of this as maintaining a 'recipe book' for a family dish. Writers add notes if something didn’t taste right or if a new spice improved the meal. Future cooks can look back at these notes to avoid past mistakes and replicate successes.

--