►
From YouTube: intro to product design
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
My
name
is
michael
lee
and
I'm
a
senior
product
designer
here
at
good
lab
and
over
the
couple
of
years
I've
been
here,
I've
been
able
to
work
on
navigation
settings,
the
editing
experience,
and
today
I
had
the
pleasure
of
walking
through
this
course
about
the
intro
of
product
designs.
Where
we're
going
to
highlight
these
three
points,
what
is
product
design?
What
does
a
product
designer
do
and
what
skills
are
essential
to
be
a
good
product
designer.
A
A
A
A
Are
these
issues
the
root
cause
of
the
problem,
or
do
we
need
to
do
more
research
to
dig
deeper
to
find
the
answer
and
at
the
same
time
we
want
to
know
how
big
is
this
problem?
Is
this
problem
affecting
a
small
subset
of
our
users
or
a
large
subset,
and
that
will
determine
how
we
prioritize
the
work
and
where
we
focus
our
energies
on
once
we
part
of
validating
the
problem
is
also
to
define
the
problem.
A
Better
and
here
we
will
be
looking
towards
using
our
personas,
which
is
a
map
of
our
ideal
user
that
would
be
in
these
different
situations
and
understanding
the
high
level
path
or
the
user
journeys
that
they
may
go
through
to
complete
their
tasks
inside
the
user
journey.
There
might
be
distinct
steps
in
their
tasks
or
jobs
that
they
need
to
do
to
achieve
their
goals
and
what
we
are
looking
to
do.
A
There
is
analyze
and
look
at
each
of
those
individual
tasks
or
jobs,
to
help
define
them
out
to
validate
them,
to
make
sure
that
their
re
real
experiences
that
our
users
have.
A
The
next
step
after
we
done
validating
and
understanding
problems
with
ux
researchers
and
product
managers
is
time
to
look
at
how
we
might
define
the
solution
to
the
problem
and
in
these
scenarios
these
are
some
of
the
questions
that
may
come
up.
What's
the
right
component
or
pattern
to
use
to
solve
this
problem.
A
A
And
here
we're
looking
at
responsive
designs
like
how
might
this
look
on
the
large
screen
versus
a
small
screen,
such
as
a
mobile
phone,
whether
the
information
hierarchy
matches
the
visual
hierarchy?
So
are
we
using
large
text
for
headings
and
titles,
and
and
does
that
match
what
people
see
on
the
screen
in
the
order
that
they
see
it?
A
And
all
of
this
is
looking
at
creativity
and
constraints,
and
this
is
why
I
love
doing
this
job,
because
it
is
giving
you
a
lot
of
information
and
it's
up
to
you
to
distill
it
into
something:
that's
going
to
be
usable
for
users
and
that
when
we're
talking
about
usability,
we're
also
talking
about
accessibility.
So
this
means
looking
at
the
interactions
and
color
usage,
to
make
sure
that
it's
accessible
to
holes
so
that
anyone
can
use
it
in
any
context,
whether
they're
using
a
keyboard,
mouse
or
touch
device.
Our
product
should
be
usable
for
everyone.
A
So
once
we
have
our
design,
we
validate
our
problem.
The
next
thing
we
do
is
to
check
if
these
solutions
that
we've
come
up
with
achieves
the
goal
of
the.
If
our
solution
achieves
the
goal
by
getting
users
to
check
the
flows
themselves
by
going
through
prototypes
prototypes,
are
a
series
of
clickable
images
representing
the
flow
that
we
want
users
to
test,
or
it
could
even
be
a
code
build
that
represents
this
new
flow.
A
A
It
doesn't
mean
that
we're
done
this
is
our
learn
and
improve
phase.
So
what
we're
looking
here
is
to
check
into
our
product
analytics
to
ensure
that
users
are
using
it
at
scale
and
understanding
if
the
goals
that
we
set
up
to
say
that
you
know
people
clicked
these
certain
events
on
these
certain
buttons
in
these
orders,
or
they
made
it
to
a
certain
page,
help
with
us
measuring
the
solution
effectiveness
over
time.
A
To
me,
these
are
the
essential
skills
that
would
make
a
really
good
product
designer
you're
curious.
Your
challenge,
assumptions
made
by
users
the
business
yourself
and
you
can
validate
them
through
solution,
validation
or
problem,
validations
and
you're,
not
afraid
to
ask
questions
like
why,
and
I
think
that
really
helps
dig
in
deeper
to
find
root,
causes
and
able
to
unlock
new
insights.
A
You
also
have
should
have
good
communication,
so
this
looks
at
how
you
can
use
storytelling
to
give
an
engaging
presentation,
how
you
might
frame
questions
to
users
to
ask
things
in
a
different
way,
to
entice
more
dialogue
and
questions
and
answers
from
user
interviews
and
articulating
your
design
rationales
of
why
we're
going
with
a
certain
direction
versus
another
solution
as
a
designer
you
need
to
work
on
your
craft,
and
this
looks
at
understanding
visual
hierarchy
layout
patterns,
how
you
can
prototype
more
realistic
experiences
so
that
you
can
do
better
solution,
validations
and
understanding
which
interactions
are
the
right
ones
to
use
and
at
which
fidelity
in
the
different
phase
of
the
whole
product
development,
workflow
and
putting
it
all
together
is
the
attention
to
detail.
A
So
this
is
not
really
asking
hey,
you
need
to
know
how
to
code,
but
this
looks
at
do
you
know
how
all
the
pieces
of
the
code
fit
together?
Do
you
know
which
parts
are
talking
to
which
parts
of
the
system-
and
this
comes
down
to
a
deep
understanding
of
your
part
of
the
product,
because
that's
the
only
way
you're
going
to
deliver
a
better
experience
by
understanding
how
users
get
in
and
out
of
your
flows
and
as
well
as
all
the
edge
cases
in
between.
A
That's
it
for
this
course,
but
if
you're
looking
to
learn
more
and
you
can
check
out
the
product,
design,
rules
and
responsibility
in
the
link
here,
that
will
tell
you
about
the
different
levels
that
we
have
within
the
product
design
team.
If
you
want
to
know
what
we're
doing
from
a
ux
team
as
a
whole,
you
can
check
out
our
the
ux
showcase,
and
this
has
different
designers
talking
about
the
things
that
are
working
through
different
processes
and
different
ways
of
working
across
our
global
design
team.