►
From YouTube: UX Showcase - UX onboarding & UX buddy experience
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
Okay,
hey
everyone,
I'm
gina
doyle
and
I'm
the
product
designer
for
verify,
testing
and
runner.
I
just
joined
the
ux
team
about
a
month
ago
on
july
12th,
so
I'm
going
to
talk
about
my
ux
onboarding
and
ux
buddy
experience.
A
So
here's
an
image
of
kind
of
how
I've
been
spending
my
first
month
of
my
onboarding
time
in
the
top
left
you'll
see
the
handbook
a
lot
of
it
has
been
reading
the
handbook.
As
you
all
know,
the
onboarding
issue
contains
a
whole
bunch
of
links.
So
that's
the
majority
of
my
time
right
now.
I
did
realize
that
at
some
points
I
was
reading
through
and
not
really
taking
in
what
I
was
reading,
and
I
think
that
I
learned
I
need
to
add
more
breaks
into
that.
A
So
if
anybody
else
is
starting
or
has
to
read
a
lot,
I
would
recommend
doing
that
and
then
I
also
realized
that,
as
I
started
taking
on
product
issues
in
uxkrs,
I
ended
up
having
to
go
back
and
refreshing.
My
memory
kind
of
on
the
topics
that
I
had
read,
which
I
think
is
not
a
bad
thing,
but
I
did
realize
that
I
missed
a
lot
in
the
beginning.
A
I
was
kind
of
able
to
resonate
with
more
than
just
reading
it
in
the
handbook,
and
I
think
that's
mostly
because
it
gave
so
much
context
about
the
problem
at
hand
and
like
how
to
solve
it,
and
it
was
easier
for
me
to
learn
with
the
visual
too
and
then
another
big
chunk
has
been
issues
which,
I
think
is
all
of
our
lives.
Right
now
involves
get
lab
issues.
I
think
it's
awesome
that
we
use
our
own
product.
A
That
has
been
really
cool
to
see,
and
a
lot
of
the
conversation
happens
in
that
that
issue
as
well.
So
it's
easy
to
catch
up
on
the
history
of
what
happened,
especially
for
me,
who
was
kind
of
exploring
the
issues
in
my
product
areas
and
then
could
easily
get
up
to
speed
through
the
discussion
that
was
there
and
issue
the
links
that
were
added
into
the
issues
and
then,
finally,
my
other
portion
of
onboarding
has
been
one-on-ones
and
coffee,
chats,
I'm
really
lucky
to
have
my
manager
hayanna
and
my
onboarding
buddy
vitica.
A
I'm
glad
that
I
was
also
being
given
the
time
to
be
able
to
meet
a
lot
of
you
on
the
team,
and
I
still
have
a
lot
more
of
you
to
meet,
and
then
I
was
also
able
to
meet
a
lot
of
people
in
my
product
teams,
which
was
nice,
and
I
also
realized.
I
took
advantage
of
the
coffee
chats
things
I
think
in
the
first
couple
weeks,
because
I
set
up
a
whole
bunch
of
them
and
then
realized
that
it
was
a
bit
overwhelming
because
I
set
up
so
many
so
going
forward.
A
The
next
thing
I
wanted
to
go
through
was
my
product
designer
onboarding
issue,
which
I
linked.
It's
in
the
angela.
It's
also
in
this
screen,
and
I
wanted
to
go
through
some
of
the
larger
categories
of
kind
of
like
how
I
reflected
on
it
in
the
I'm
going
to
go
through
this
kind
of
quickly.
A
A
A
One
other
thing
that
I
reflected
on
myself
is
that
I
put
a
lot
of
pressure
on
myself
to
complete
all
those
tasks
and
the
issues,
and
I
think
when
I
see
the
checkbox,
I
just
want
to
check
them
all
off,
and
I
talk
to
everybody
about
it,
and
everyone
makes
me
feel
very
the
opposite
way
like.
I
should
not
be
pressured.
A
So
that
is
something
that
I
just
realized
about
myself
that
I
reflected
on
and,
lastly,
recording
videos
is
a
huge
part
of
the
design
workflow.
I
think
that's
been
awesome.
I
think
it's
an
easier
way
to
kind
of
describe
how
your
problem
or
your
project
went
instead
of
just
writing
it
on
the
screen.
A
Some
of
the
big
surprises
was
that
we
all
have
to
use
gdk
or
get
pod
and
it's
necessary
for
the
design
workflow.
I
think
that's
also
cool,
because
it
brings
us
closer
to
the
development,
workflow
and
kind
of
forces
us
to
learn
more
about
git
lab
as
a
product,
and
then
some
of
the
big
questions
I
had
is:
why
was
gdk
failing
to
install
or
start?
I
finally
did
get
it
installed
and
it's
working
properly
now,
but
it
was
a
struggle
and
how
do
I
apply?
A
The
design
workflow
cycle
to
my
everyday
tasks
was
another
thing
I
was
struggling
with
and
I
think
that's
going
to
come
with
time,
but
I'm
getting
more
used
to
it
now
is
just
trying
to
figure
out
like
how
do
I
now
pick
up
issues
and
what's
the
best
way
to
go
about
that,
so
some
other
things
is
what
went
well.
A
lot
of
that
was
around
learning
more
about
the
product.
My
product
area,
specifically
to
with
videos
that
were
product
demos
on
youtube,
using
loom
to
record
videos,
was
really
easy.
A
I
liked
that
a
lot,
because
I
could
chop
out
my
mistakes
and
then
using
the
web
ide
to
create
simple.
Mrs,
has
been
great.
I
actually
really
prefer
using
the
web
id
over
like
my
terminal
and
then
getting
help
from
vitica
in
meetings
or
asynchronously
she's,
always
willing
to
hop
on
a
call
which
has
been
great,
because
we
have
very
distinct
time
zones
and
then
always
receiving
detailed
and
organized
plans
from
hayanna.
Who
has
helped
me
feel
better
about
the
state
that
I'm
at
things
that
didn't
go
well.
A
Gdk
was
a
struggle
like
I
said,
and
then
the
project
and
website
using
gitlab
pages
was
somewhat
difficult
for
me,
and
I
realized
that
I
couldn't.
I
was
trying
to
follow
the
documentation
and
I
ended
up
having
to
watch
like
a
demo
video
to
complete
it
so
yeah,
something
that
just
took
a
little
longer
than
expected
and
then
something
that
could
be
better,
possibly
would
be
adding
a
timeline
view
of
what
should
be
completed
over
time.
A
I
think
the
general
onboarding
issue
broke
it
down
by
days
and
it
kind
of
gave
me
a
sense
of
what
I
would
complete
over
time
and
this
one.
It
was
just
like
everything,
so
I
was
thinking
of
maybe
trying
to
improve
that
by
submitting
like
creating
an
issue
around
it
and
discussing
how
we
could
propose
a
solution
for
that,
and
then
I
just
wanted
to
quickly
go
through
how
I've
been
staying
organized
throughout
the
onboarding
experience.
A
I've
been
using
a
markdown
file
to
track
my
weekly
priorities
and
tasks,
which
I
really
like,
and
I
stole
that
from
hayanna
as
well
and
that's
been
helping
me,
keep
the
smaller
things
in
track
and
then
the
larger
things
I'll
have
milestone
issues
with
the
table
to
track
my
issues
for
that
milestone
and
then
any
ux
kr
work
that
overlaps
within
that
time
and
finally,
for
meetings.
A
I
will
usually
hop
on
about
45
minutes
before
and
just
asynchronously
like
update,
whatever
questions
that
are
in
that
agenda
and
then
I'll
also
create
action
items
for
myself,
which
I
like
doing
so.
I
can
take
on
whatever
items
that
came
out
of
that
discussion
and
finally,
I'm
going
to
zoom
through
this,
the
ux
buddy
experience
has
been
great
and
I
just
wanted
to
share
some
of
those
things
that
have
been
going
well.
So
far
so
vita
and
I
meet
weekly
for
one-on-ones.
A
It's
really
great
to
be
able
to
work
with
her
again
because
we
worked
together
previously.
So
that
was
comfortable
like
coming
in
having
someone
to
know
and
then,
like
I
said
before,
we
communicate
asynchronously
through
issues
in
slack
or
we
just
hop
on
a
call
like
if
we
have
time-
and
the
other
thing
that
she's
been
providing
me
is
links
to
previous
work.
A
That's
been
done
that
I
can
reference
to
complete
whatever
it
is
that
I
have
to
complete,
which
has
been
really
useful
and
she
has
been
providing
me
a
lot
of
leadership
and
mentorship,
especially
reflecting
on
her
own
onboarding
experience
and
what
can
be
better
for
mine,
and
then
I've
been
using
her
support
for
the
ux
scorecard
that
I've
been
going
through
now.
That
relates
to
our
york's
krs
and
she's,
been
really
great
in
collaborating
through
that.