Scribd
Upload
47 views4 pages

Prototype Refinement Strategies

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
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
47 views4 pages

Prototype Refinement Strategies

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
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

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:
[Link]
030807/#:~:text=Keep%20the%20purpose%20of%20the,the%20final%20system%20is
%20produced.

Common questions

Powered by AI

Participant observation during prototype testing can significantly impact design decisions by providing direct feedback on how end-users interact with the system. This can reveal unexpected usability issues or missing functionalities that need attention. Observations can guide iterations and improvements on the user interface and overall system design. Furthermore, videotaped sessions can be persuasive tools for advocating redesigns to application engineers and management .

Observing participants using a prototype is significant because it helps to uncover learning problems that may not surface in interviews, allows for the evaluation of ease of use, navigation, and functionality, and provides insights for further refinement. Talking aloud during this observation can provide additional feedback, although it might slow down the process and affect time estimates .

Keeping the purpose of a prototype in mind during refinement is important because it ensures that resources are efficiently utilized to meet specific goals, whether they are resolving technical issues or preparing for final system production. It helps in aligning the refinement process with the intended outcome, avoiding unnecessary efforts in scenarios where a prototype doesn't achieve its primary objectives and must be reassessed or discarded .

Video recordings during prototype testing enhance the refinement process by providing a visual record of user interactions, highlighting usability issues that may not have been captured through written observations alone. These recordings can serve as compelling evidence for necessary redesigns and are especially useful in demonstrating the need for changes to stakeholders who may not be present during live testing .

Early iterations of a prototype focus on validating the overall system vision, ensuring the product is aligned with customer expectations, and identifying any major oversights, such as missing features. In contrast, later iterations concentrate on refining specific elements like the user interface, rectifying missing or erroneous functionalities, and evaluating end-user interactions for additional refinements to enhance usability and effectiveness .

Customer feedback is pivotal in prototype refinement as it provides insights into user needs and areas requiring improvement. It can lead to changes in functionality or scope adjustments if new data elements or test scenarios are identified during demonstrations. This feedback loop ensures that the final product is user-focused and aligns with defined requirements, potentially impacting timelines and project resources depending on the extent of required changes .

The focus when reviewing a prototype's system structure for improvement should be on potential enhancements in system architecture that improve user experience, ease of use, and robust functionality. This includes assessing the overall design, functionalities that might be subtle, and user elements like windows and menu bars to ensure they are user-friendly and align with customer expectations .

Methods to refine a prototype after user testing include conducting demonstrations, testing the prototype for missing or incorrect functionality, and observing participants' usage. These methods are important because they offer diverse insights into how the prototype performs in real-world scenarios, help gather comprehensive feedback for further improvements, and ensure the system meets business requirements and user expectations before the final rollout .

Validating the functionality of a prototype in early iterations is crucial because it ensures that the system being built aligns with customer expectations and addresses any significant oversights, such as missing screens, before further development. This early validation helps in confirming that the right product is being built and facilitates customer buy-in by meeting their vision and needs .

Encouraging customers to express their ideas aloud during prototype testing can introduce challenges such as slowing down the user's natural problem-solving process and potentially distracting them from typical usage patterns. It can also make it difficult to obtain meaningful time estimates as the verbalization process takes additional time. Despite these challenges, it can provide valuable insights into user experience and areas for improvement .

You might also like