1 of 25

Evaluasi UX dalam Design Life Cycle

PERTEMUAN 2 – EVALUASI UI/UX

Team Teaching:

Retno Indah Rokhmawati, S.Pd., M.Pd.

Riswan Septriayadi Sianturi, S.Si.., MM., M.Sc., Ph.D.

2 of 25

Review Materi

3 of 25

4 of 25

What is evaluation?

  • Evaluation is a process that critically examines a system.
  • It involves collecting and analyzing information about a system’s activities, characteristics, and outcomes.
  • Its purpose is to make judgments about a system, to improve its effectiveness, and/or to inform the stakeholders involved.

  • Patton, M.Q. (1987). Qualitative Research Evaluation Methods. Thousand Oaks, CA: Sage Publishers.

5 of 25

When?

  • Ideally, evaluation should occur throughout the design life cycle, with the results of the evaluation feeding back into modifications to the design.
  • Clearly, it is not usually possible to perform extensive experimental testing continuously throughout the design, but analytic and informal techniques can and should be used.
  • We will consider evaluation techniques under two broad headings: expert analysis and user participation.

Alan Dix, Janet E. Finlay, Gregory D. Abowd, and Russell Beale. 2003. �Human-Computer Interaction (3rd Edition). Prentice-Hall, Inc., Upper Saddle River, NJ, USA.

6 of 25

When?

  • Evaluation throughout the design life cycle has the advantage that problems can be ironed out before considerable effort and resources have been expended on the implementation itself: it is much easier to change a design in the early stages of development than in the later stages.�

Alan Dix, Janet E. Finlay, Gregory D. Abowd, and Russell Beale. 2003. �Human-Computer Interaction (3rd Edition). Prentice-Hall, Inc., Upper Saddle River, NJ, USA.

7 of 25

Why?

  1. Improve system design and implementation.
  2. It is important to periodically assess and adapt your activities to ensure they are as effective as they can be.
  3. Evaluation can help you identify areas for improvement and ultimately help you realize your goals more efficiently.

8 of 25

Why?

  1. Demonstrate system impact.
  2. Evaluation enables you to demonstrate your system’s success or progress.
  3. The information you collect allows you to better communicate your system's impact to others, which is critical for public relations, staff morale, and attracting and retaining support from current and potential funders.

9 of 25

What type of evaluation?

There are many different dimensions to consider when choosing the best assessment approach:

  • Goal: Summative (on the final product) or formative (during the process)
  • Approach: Objective or subjective
  • Data: Quantitative or qualitative
  • Moments: Momentary, episodic, or overall UX
  • Setup: Lab or field

10 of 25

When?

  • Do user research at whatever stage you’re in right now. The earlier the research, the more impact the findings will have on your product, and by definition, the earliest you can do something on your current project (absent a time machine) is today.
  • Do user research at all the stages. As we show below, there’s something useful to learn in every single stage of any reasonable project plan, and each research step will increase the value of your product by more than the cost of the research.

11 of 25

When?

  • Do most user research early in the project (when it’ll have the most impact), but conserve some budget for a smaller amount of supplementary research later in the project. This advice applies in the common case that you can’t get budget for all the research steps that would be useful.

12 of 25

Design Life Cycle (Nielsen)

Discover

  • The discovery stage is when you try to illuminate what you don’t know and better understand what people need.
  • An important goal at this stage is to validate and discard assumptions, and then bring the data and insights to the team.

13 of 25

Design Life Cycle

Explore

  • Exploration methods are for understanding the problem space and design scope and addressing user needs appropriately.

Test

  • Testing and validation methods are for checking designs during development and beyond, to make sure systems work well for the people who use them.

14 of 25

Design Life Cycle

Listen

  • Listen throughout the research and design cycle to help understand existing problems and to look for new issues. Analyze gathered data and monitor incoming information for patterns and trends.

15 of 25

16 of 25

17 of 25

Top UX Research Methods

Discover

• Field study�• Diary study�• User interview�• Stakeholder interview�• Requirements & constraints gathering

Explore

• Competitive analysis• Design review• Persona building• Task analysis• Journey mapping• Prototype feedback & testing (clickable or paper prototypes)• Write user stories• Card sorting

Test

• Qualitative usability testing (in-person or remote)• Benchmark testing• Accessibility evaluation

Listen

• Survey�• Analytics review�• Search-log analysis�• Usability-bug review�• Frequently-asked-questions (FAQ) review

18 of 25

19 of 25

Summative vs. �Formative

20 of 25

Summative vs. Formative

Evaluations fall into one of two broad categories:

  • Formative evaluations are conducted during system development and implementation and are useful if you want direction on how to best achieve your goals or improve your program.
  • Summative evaluations should be completed once your system are well established and will tell you to what extent the system is achieving its goals.

21 of 25

22 of 25

TYPE OF EVALUATION

PURPOSE

Formative

1. Needs Assessment

Determines who needs the system, how great the need is, and what can be done to best meet the need, what audiences are not currently served by systems and provide insight into what characteristics new systems should have to meet these audiences’ needs.��How to conduct need assessment: https://coast.noaa.gov/needsassessment/#/

2. Process or Implementation Evaluation

Examines the process of implementing the system and determines whether the system is operating as planned. Can be done continuously or as a one-time assessment. Results are used to improve the system. A process evaluation may focus on the number and type of participants reached and/or determining how satisfied these individuals are with the system.

23 of 25

TYPE OF EVALUATION

PURPOSE

Summative

1. Outcome Evaluation

Investigates to what extent the system is achieving its outcomes. These outcomes are the short-term and medium-term changes in system participants that result directly from the system. For example, outcome evaluations may examine improvements in participants’ knowledge, skills, attitudes, intentions, or behaviors.

2. Impact Evaluation

Determines any broader, longer-term changes that have occurred as a result of the system. These impacts are the net effects, typically on the entire school, community, organization, society, or environment.

24 of 25

Phases of Product Development

  1. STRATEGIZE: In the beginning phase of the product development, you typically consider new ideas and opportunities for the future. Research methods in this phase can vary greatly.
  2. EXECUTE: Eventually, you will reach a "go/no-go" decision point, when you transition into a period when you are continually improving the design direction that you have chosen. Research in this phase is mainly formative and helps you reduce the risk of execution.

25 of 25

Phases of Product Development

  1. ASSESS: At some point, the product or service will be available for use by enough users so that you can begin measuring how well you are doing.  This is typically summative in nature, and might be done against the product’s own historical data or against its competitors