D479 Task 2 Guide
Uploaded by
antoniomwaniki001D479 Task 2 Guide
Uploaded by
antoniomwaniki001Common questions
Powered by AIFeedback analysis is crucial as it provides insights into user struggles and successes, allowing for actionable design improvements. Feedback should be summarized by usability task, explaining what users said, where they struggled, succeeded, and categorizing feedback as either actionable or not, based on its nature. This approach ensures informed, iterative design improvements aligned with user needs.
The guide specifies using clear, professional language, avoiding slang or casual phrasing, ensuring clean and readable formatting, working links, and managing file sizes to stay within prescribed limits. These requirements ensure the clarity and professionalism of the submission, contributing to effective communication of ideas and adherence to academic standards.
The process involves summarizing feedback by usability task and categorizing it as actionable or non-actionable. Actionable feedback requires a design change, ensuring clear identification of areas needing improvement. This structured analysis facilitates intentional iterations informed by real user interactions, which directly lead to enhanced usability and design effectiveness.
The guide ensures alignment by requiring that the usability tasks created in Task 1 be objective, action-oriented, and tailored towards real user goals. This helps maintain a focus on practicality and user-centered design in the prototype evaluation process.
The key steps are to open the Prototype and Peer Review Dashboard, select the Usability Prototype Submission Form, paste the interactive prototype URL (updated version from Task 1 feedback), enter five objective usability tasks that are action-oriented and aligned to real user goals, submit the form, open the D479 Task 2 Template, and complete the 'Your Prototype' section by entering your name, ID, the same prototype link, and the exact same five usability tasks as submitted in the dashboard.
Wearing professional attire during the video recordings fosters a level of professionalism and credibility. It reflects the formal nature of the peer review process and aligns the presentation with professional standards, enhancing the overall perception of the submission's quality.
Matching tasks exactly between the dashboard and the template ensures consistency and reliability in the submission process. It mitigates errors or discrepancies that could arise from differing sets of usability tasks and ensures that all evaluations are based on the same parameters, enhancing the assessment's integrity.
External sources must be reviewed and, if used, cited in APA format within the text, with a references section included. Peer feedback is not required to be cited. This approach maintains academic rigor and provides context and support for decisions made during the task completion process.
The specific requirements include logging in to Panopto with the WGU option, recording separate videos for each peer prototype with both camera and screen recording enabled, wearing professional attire, performing all five usability tasks of a peer, verbally explaining what is being done, what works, what is confusing, whether tasks can be completed, and saving the recording with specific viewing permissions set. Voice-only or screen-only recordings do not meet the criteria.
The guide recommends a clear articulation of the design evolution from initial wireframes, through Task 1 guerrilla testing, to Task 2 usability testing, emphasizing necessary changes and how user feedback informed these updates. Focus should be on usability improvements like navigation clarity, layout consistency, and reducing cognitive load, showcasing intentional and informed iteration based on user interactions and feedback.