Scribd
Upload
72 views

Chapter 9 Refining Prototypes PDF

This chapter discusses refining prototypes based on user feedback. It explains that after user testing, the results must be analyzed for patterns and insights to inform next steps, such as fixing usability issues or returning to ideation. Prototypes should be iterated and refined until the product is ready for launch. Early iterations focus on understanding the vision and identifying oversights, while later iterations improve functionality and the user interface. Refinement methods include re-testing, demonstrations to capture feedback, and observing users to identify problems. The prototype is refined until the purpose is satisfied or problems are found.

Uploaded by

Angeline Lagmay Visaya
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
72 views

Chapter 9 Refining Prototypes PDF

This chapter discusses refining prototypes based on user feedback. It explains that after user testing, the results must be analyzed for patterns and insights to inform next steps, such as fixing usability issues or returning to ideation. Prototypes should be iterated and refined until the product is ready for launch. Early iterations focus on understanding the vision and identifying oversights, while later iterations improve functionality and the user interface. Refinement methods include re-testing, demonstrations to capture feedback, and observing users to identify problems. The prototype is refined until the purpose is satisfied or problems are found.

Uploaded by

Angeline Lagmay Visaya
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Chapter 9

Refining Prototypes

Introduction
You’ve conducted several user tests and have documented your findings. What
happens now?

After a round of user tests, you’ll need to spend some time analyzing the results.
You’ll look for patterns in what you’ve observed and the feedback you received. Your
tests will either validate that something works well, or highlight issues that need to be
fixed. Either way, the insights you gather from user testing will inform your next steps. Do
you need to reiterate on the current design in order to fix a usability issue? Did your initial
concept completely fail in front of your users, sending you back to the ideation phase?
Perhaps your test users confirmed that your information architecture is extremely user
friendly, meaning you’re ready to start refining the design.

Design Thinking is all about iterating and reiterating until your product is ready for
launch—but it doesn’t stop there! Even once your product is on the market, you’ll continue
to run tests and add new features or make improvements.

Prototyping and testing are absolutely key to creating user-friendly products, so


remember to test early and often!

Learning Outcomes/Objectives

After the completion of this chapter, the student must be able to enhance the prototype
produced based on user feedback.

Learning Content/Topic

Keep the purpose of the prototype in mind and refine the prototype to the point
that the purpose is satisfied. For example, if the prototype is to be retained and
used to produce the actual system, refinement will continue until the final system
is produced. However, if the purpose of the prototype is to resolve a technical
issue, the prototype is refined to the point where a solution, or insurmountable
problem, is found.

In some situations, the purpose may change. For example, if major problems are
uncovered in the content or design of the prototype, a prototype that was to be
assimilated may become a throw away prototype, with no further refinement.
Focus of Early Iterations

Each iteration of a prototype allows the customer to observe, critique, and


experience the prototype. Encourage the customer to offer suggestions for
refinement.

Early iterations of prototype should concentrate on the following questions.

• Does the customer accept the vision of the system? Are we building the
right product? Does it look the way you expected?
• Are there any significant oversights? For example, did we miss a screen?
• Is the customer comfortable with using the prototype? Is the customer able
to offer more than cosmetic suggestions, such as new ideas?

Focus of Later Iterations

Later iterations of a prototype should concentrate on:

• identifying missing or incorrect functionality,


• improving the human interface,
• observing the end-user to evaluate if additional refinement is needed.

Improve the User Interface

When reviewing a prototype with the customer, consider:


• reviewing the system structure to see if it can be improved,
• reviewing functions that are subtle and better understood by users than
analysts,
• reviewing windows, menu bars, and reports to improve their content and
ease of use.

How to Refine the Prototype

Methods of Refinement
Use a number of methods to refine the prototype. For example:
• test the prototype,
• conduct a demonstration,
• observe participants using the prototype.

Test the Prototype

To identify missing or incorrect functionality, test, redesign, and test the prototype
again. For functional requirements, the prototype “works” if it can perform each
simulated business transaction. If a business function does not work it should be
removed from the prototype or worked on for the next iteration of the prototype.

Conduct a Demonstration

Provide the customer with an overview of the prototype system and demonstrate
the prototype. When demonstrating a prototype to customers, capture the
following information:
• date of demonstration,
• names of attendees,
• functions demonstrated,
• test scenarios prepared and reviewed,
• appropriateness of security levels,
• archival needs,
• backup/recovery needs.

Customers often request changes to the prototype during a demonstration that


result in changes to functionality or new data elements being
identified. Requests to change test scenarios may require additions or changes
to functionality. Such changes may affect the scope of a project.
Observe Participants

Once the customer is familiar with the prototype, observe the customer working
with the prototype, prompting the customer only when the customer is having
difficulty. Encourage the customer to think aloud during the observation,
expressing his or her thoughts on such factors as ease of use, navigation, and
functionality. However, note that talking out loud may distract the customer from
his or her usual problem-solving process. Talking out loud will also slow down
the process so that meaningful time estimates cannot be obtained. Interview the
customer following the observation to obtain more feedback.
Participant Observation can uncover learning problems the customer may not
report in an interview. It works most effectively when simulating real tasks and
involving customers who will be using the final system.
Consider videotaping the customer working with the prototype. A videotape is
effective when trying to persuade application engineers and management there
is a need for redesign.

Teaching and Learning Activities

Discussion
Research
Group Activities

Flexible Teaching Learning Modality (FTLM) adapted

Video Conferencing/Google classroom

Assessment Task

References:
https://www.toolbox.com/tech/enterprise-software/blogs/refining-a-prototype-
030807/#:~:text=Keep%20the%20purpose%20of%20the,the%20final%20system%20is
%20produced.

You might also like