Hours 5-6: Reviewing and Refining Wireframes and Prototypes
Hour 5: Techniques for Reviewing and Refining Wireframes and Prototypes
5.1 Reviewing Wireframes and Prototypes
Introduction to the review process: What it is, why it's important, and who should be involved.
Methods for conducting a review: Individual inspection, group walkthroughs, heuristic evaluation, etc.
Key elements to review: Consistency of layout and design elements, clarity of the information structure, intuitiveness of the navigation, alignment with user needs and project objectives, etc.
5.2 Refining Wireframes and Prototypes
Responding to feedback: How to interpret and prioritize feedback, and how to decide what changes to make.
Iterating on the design: Tips for refining the layout, information structure, navigation, and visual design based on feedback.
Documenting changes: The importance of keeping a record of changes made, reasons for the changes, and feedback received.
Hour 6: Hands-on Exercise: Reviewing and Refining the Sample Web Application Wireframes and Prototype
6.1 Reviewing the Wireframes and Prototype
Conducting a thorough review of the wireframes and prototype you've created for the sample web application. This could be done individually or as a group.
Noting down any issues, questions, or suggestions that come up during the review.
6.2 Refining the Wireframes and Prototype
Prioritizing the issues and suggestions based on their potential impact on the user experience and the feasibility of implementing the changes.
Making necessary changes to the wireframes and prototype based on your review and prioritization. This could involve adjusting the layout, redesigning certain elements, revising the navigation, etc.
6.3 Documenting and Presenting Your Changes
Keeping a record of what changes were made, why they were made, and any feedback or insights that led to these decisions.
Presenting the revised wireframes and prototype to your team members, stakeholders, or instructors for another round of review and feedback. Be prepared to explain your changes and provide rationale for your design decisions.
Want to print your doc? This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (