WEBVTT

00:00:04.520 --> 00:00:06.480
To create great user experiences.

00:00:06.480 --> 00:00:09.840
UX design teams use a five phase process:

00:00:09.920 --> 00:00:13.120
Empathize, define, ideate,

00:00:13.200 --> 00:00:16.000
prototype and test.

00:00:17.280 --> 00:00:19.480
In the empathize phase, teams explore

00:00:19.480 --> 00:00:22.360
the problem they're trying to solve
with the product.

00:00:22.360 --> 00:00:25.920
User researchers conduct interviews
with people affected by the problem

00:00:25.920 --> 00:00:28.360
and review
existing knowledge of the issue.

00:00:28.360 --> 00:00:32.320
The stage is about knowing
what needs to be solved and why.

00:00:34.200 --> 00:00:37.440
At the defined stage, user researchers
turn their knowledge

00:00:37.440 --> 00:00:41.360
into a research plan
and conduct more targeted tests.

00:00:41.440 --> 00:00:43.920
They'll learn more about their users
and what they're currently doing

00:00:43.920 --> 00:00:45.600
to solve the problem.

00:00:45.600 --> 00:00:48.520
Then they'll put their findings
into deliverables.

00:00:48.520 --> 00:00:52.840
Tools for the UX designers to reference
when they start designing solutions.

00:00:52.920 --> 00:00:58.800
These include: user Journey Maps, to show
how users try and solve the problem and present.

00:00:58.800 --> 00:01:02.280
Personas, which are details of typical users.

00:01:02.360 --> 00:01:06.880
Affinity Diagrams of what those users
think, feel, see and do.

00:01:06.920 --> 00:01:11.760
And "How might we" statements that list
the problem teams are trying to solve with the product.

00:01:12.360 --> 00:01:17.160
In the ideate phase, teams ensure everyone has a shared
understanding of the problem.

00:01:17.240 --> 00:01:19.800
Someone will
then lead a brainstorming session

00:01:19.800 --> 00:01:23.400
where the team will consider solutions
for the first time.

00:01:23.480 --> 00:01:26.080
The team will come up
with as many ideas as possible,

00:01:26.080 --> 00:01:29.040
even if they're silly sounding
or impractical.

00:01:29.040 --> 00:01:32.560
Afterwards, they will evaluate the options
and choose the most viable

00:01:32.560 --> 00:01:35.560
and effective solutions from those ideas.

00:01:35.600 --> 00:01:39.320
In the prototyping phase,
the UX designers turn those design ideas

00:01:39.320 --> 00:01:41.400
into testable prototypes.

00:01:41.400 --> 00:01:46.800
These prototypes could be low fidelity,
digital prototypes or even paper prototypes.

00:01:46.800 --> 00:01:50.880
The UX designers will do their best
to make sure the product is intuitive to use

00:01:50.880 --> 00:01:54.480
and make multiple versions
of those design ideas.

00:01:55.440 --> 00:01:57.600
In the test phase, researchers

00:01:57.600 --> 00:02:00.760
get participants to test the prototype
and get feedback.

00:02:00.760 --> 00:02:04.440
From that they deliver usability test reports to the designers.

00:02:04.440 --> 00:02:07.640
Who then make new prototypes based on that feedback.

00:02:07.640 --> 00:02:11.720
products will get increasingly polished
and refined with cycles of testing

00:02:11.720 --> 00:02:13.800
until a final design is settled on.

00:02:13.800 --> 00:02:16.600
Then the design will be developed
and shipped.

00:02:16.600 --> 00:02:20.240
You think it's
all over here, but not quite.

00:02:20.320 --> 00:02:23.240
Product development is cyclical
and non-linear.

00:02:23.240 --> 00:02:26.800
The product can still be revamped
based on real user feedback,

00:02:26.880 --> 00:02:31.080
and in that revamp you may repeat some
or all of the design phases.

00:02:31.160 --> 00:02:36.320
New information could even set development
right back to the planning stage once again.