The objective of the Lo-Fi Prototype & Test stage was to quickly translate my ideas into tangible designs and evaluate how intuitive the core features were before moving into higher-fidelity work. Instead of focusing on visual detail, I focused on functionality, specifically how users would complete key tasks like adding events, rescheduling events, and planning social schedules. This stage allowed me to test whether the structure of my design aligned with user expectations and identify usability issues early.<\/p>\n\n\n\n
To support this process, I used ChatGPT as a tool to help guide how I translated my user flow into paper prototypes. Since I had already mapped out the system interactions, I wanted to ensure my prototypes clearly reflected those flows and supported each task step-by-step.<\/p>\n\n\n\n
Prompt:<\/strong> AI Output:<\/strong> This response helped me approach prototyping in a more structured way. I focused on creating clear, step-by-step screens for each task and made sure each interaction had a visible action, such as buttons for adding or editing events. This was especially helpful when designing flows for rescheduling and social planning, which involved multiple steps.<\/p>\n\n\n\n The biggest benefit of using AI in this stage was that it helped me translate abstract flows into concrete designs more efficiently. It provided a clear starting point and helped me think about how users would move between screens. It also reinforced the importance of clarity in actions, which directly impacted how I designed my prototypes. However, there were challenges. AI suggestions were general and did not account for the specific nuances of my design. For example, while it emphasized clarity, I still overlooked adding a clear reschedule button, which became a key issue during testing. <\/p>\n\n\n\n Reflecting on this stage, the division of labor was clear. I created all of the paper prototypes, conducted the cognitive walkthroughs, and analyzed the results independently. AI supported me by helping structure how I approached prototyping, but it did not make design decisions or identify usability issues. Those insights came directly from testing with users.<\/p>\n\n\n\n Overall, AI played a supportive role in the Prototype Lo-Fi & Test stage. It helped guide my process and improve efficiency, but the most valuable insights came from real user interaction.<\/p>\n","protected":false},"excerpt":{"rendered":" The objective of the Lo-Fi Prototype & Test stage was to quickly translate my ideas into tangible designs and evaluate how intuitive the core features were before moving into higher-fidelity work. Instead of focusing on visual detail, I focused on functionality, specifically how users would complete key tasks like adding events, rescheduling events, and planning […]<\/p>\n","protected":false},"author":13,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[],"class_list":["post-324","post","type-post","status-publish","format-standard","hentry","category-blog"],"_links":{"self":[{"href":"https:\/\/sova.ourcloud.ou.edu\/tarynhall\/wp-json\/wp\/v2\/posts\/324","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sova.ourcloud.ou.edu\/tarynhall\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sova.ourcloud.ou.edu\/tarynhall\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sova.ourcloud.ou.edu\/tarynhall\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/sova.ourcloud.ou.edu\/tarynhall\/wp-json\/wp\/v2\/comments?post=324"}],"version-history":[{"count":3,"href":"https:\/\/sova.ourcloud.ou.edu\/tarynhall\/wp-json\/wp\/v2\/posts\/324\/revisions"}],"predecessor-version":[{"id":332,"href":"https:\/\/sova.ourcloud.ou.edu\/tarynhall\/wp-json\/wp\/v2\/posts\/324\/revisions\/332"}],"wp:attachment":[{"href":"https:\/\/sova.ourcloud.ou.edu\/tarynhall\/wp-json\/wp\/v2\/media?parent=324"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sova.ourcloud.ou.edu\/tarynhall\/wp-json\/wp\/v2\/categories?post=324"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sova.ourcloud.ou.edu\/tarynhall\/wp-json\/wp\/v2\/tags?post=324"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\u201cI have a user flow diagram for a scheduling app that includes adding tasks, rescheduling tasks, and planning social events. How can I translate this user flow into paper prototypes that are clear and easy to test?\u201d<\/p>\n\n\n\n
\u201cStart by breaking each task into key screens based on your user flow. Create simple sketches for each step, focusing on inputs, actions, and system responses. Make sure each screen clearly shows what the user can do next, and include visible buttons or actions for important features like editing or rescheduling. Keep layouts simple so users can focus on functionality rather than visuals.\u201d<\/p>\n\n\n\n